in this video I would like to show you how is possible to create a WebService in ECC 6.0 and identify the correct WSDL.
I apologize for the audio but my mic is out of order; but I’m confident that video is very simple to understand.
In this period I’m involved in many upgrade projects and one of the biggest effort is to adjust ABAP copied from SAPstandard ones that I call CLONEs.
In my experience pure custom ABAPs require few adaptations (obsolete statements, obsolete function modules and so on),modifications are also well managed by modification assistant but rearranging clones is a nightmare! They usually contain a lot of INCLUDEs and call a lot of Function Modules that change so much during the upgrade.
The first step to solve a problem is to know where it is. In this case it means to have a working list of CLONEs.
Sergio Ferrari, colleague of mine and SAP mentor, suggested to me to have a look to the function module ‘RS_COMPARE_WORDS_SIMILAR’;it is very powerful and during a night I developed the report that follows.
We extended it with a lot of other logic andit’s now part of the Techedge X-RAY toolbox that we use to analyze SAP ERP system before upgrades and EhP.
The Simple ABAP Clone Hunter (lite), that I’mgoing to share with the community, tries to match each custom ABAP object witha standard one comparing the report name.
The scope of this report is not to identify univocallya standard one but is to give a rated list of possible matches.
Continue reading Simple ABAP Clone Hunter
in this post I would like to resume all the steps required in order to add the crossdomain.xml on the root of SAP WAS.
First of all create a crossdomain.xml, I used this content:
<!DOCTYPE cross-domain-policy SYSTEM “http://www.adobe.com/xml/dtds/cross-domain-policy.dtd”>
<allow-access-from domain=”*” secure=”false” to-ports=”*”/>
<allow-http-request-headers-from domain=”*” headers=”*”/>
If you need more information about crossdomain.xml please refers to Adobe Cross-domain policy file specification
Continue reading Add crossdomain.xml on the root of SAP Web application server
This class give you a collection of static method in order to access to the Frontend Services such as:
- File functions
- Directory functions
- Write to / read from clipboard
- Upload / download files
- Execute programs / open documents
- Query functions, such as Windows directory, Windows version, and so on
- Standard dialogs (open, save, directory selection)
Continue reading SAP obsolete functions (2) – CL_GUI_FRONTEND_SERVICES
When you upgrade your SAP system some functions became obsolete. (List of Obsolete Function Modules in ECC 6.0)
In this first part I would like to analyze one of the most used function module in SAP: POPUP_TO_CONFIRM
This is its signature with all the possible parameters:
CALL FUNCTION ‘POPUP_TO_CONFIRM’
* TITLEBAR = ‘ ‘
* DIAGNOSE_OBJECT = ‘ ‘
* TEXT_BUTTON_1 = ‘Ja'(001)
* ICON_BUTTON_1 = ‘ ‘
* TEXT_BUTTON_2 = ‘Nein'(002)
* ICON_BUTTON_2 = ‘ ‘
* DEFAULT_BUTTON = ‘1’
* DISPLAY_CANCEL_BUTTON = ‘X’
* USERDEFINED_F1_HELP = ‘ ‘
* START_COLUMN = 25
* START_ROW = 6
* POPUP_TYPE =
* IV_QUICKINFO_BUTTON_1 = ‘ ‘
* IV_QUICKINFO_BUTTON_2 = ‘ ‘
* ANSWER =
* PARAMETER =
* TEXT_NOT_FOUND = 1
* OTHERS = 2
POPUP_TO_CONFIRM in ECC600 have to be used instead of the obsolete function module:
Even if most of these function modules are obsolete also in SAP 4.7, I would like to analyze it because are largely used. Below for each obsolete function module I give the new coding (default use) through POPUP_TO_CONFIRM.
Continue reading SAP obsolete functions (1) – POPUP_TO_CONFIRM