Blog for SAP technical guru's: SAP basis, SAP security and authorization, SAP ABAP, SAP Focused Run
All ABAP documentation is online available in your ABAP system. Start transaction ABAPDOCU:
The most used function is the traditional ABAP keyword documentation.
But the ABAPDOCU is constantly updated and also contains great background information on:
SAP IGS is a built in graphics server for ABAP.
To determine the version of IGS running start transaction SIGS (or run program GRAPHICS_IGS_ADMIN):
Press execute:
The RFC itself can be tested in SM59 with connection IGS_RFC_DEST.
Background OSS note: 995471 – IGS administration via ABAP.
To test the graphics start program BW_IGS_CHART_TEST. Output should be:
SQVI is a tool to quickly build ad-hoc queries.
Start transaction SQVI:
Enter a QuikView name and press create. Now choose the type (in this case we will make a table join):
First add the table:
And add the second table:
The join between the tables is in this simple cases created automatically. In more complex cases you have to define the join conditions yourself.
Press the back button to go back.
Now enter the output fields:
And the selection fields:
Save the SQVI query.
Now you can start to Execute the query:
Enter the input criteria and press execute to get the wanted results:
Bug fix OSS notes for SQVI:
SAP has a nice framework to handle interface errors: AIF (application integration framework).
The framework is quite old already but was not very popular. Not to the fact that it is not good (it is in fact quite good), but it is because it is a licensed product and too expensive for the value it brings.
The framework is now split into 2 parts:
For reference you can read the formal help file from SAP on activating AIF content.
Extract the content using SE38 report /AIF/CONTENT_EXTRACT.
Then start transaction /AIF/CUST to maintain the customizing for errors. The input is given on this SAP help page.
And define the error handling levels:
Transaction /AIF/ERR can be used for the error handling monitoring:
SAP generates a lot of change documents for a lot of objects. Unfortunately for classification (for example for materials), this is not enabled by default.
The procedure to activate change documents for classification is described in OSS note 1705101 – How to Activate Classification Change Documents.
First you need to run program RCCLUKA2 as described in OSS note 942691 – Information about using RCCLUKA2. Depending on the amount of records this program runs minutes to several hours.
Program RCCLUKA2 convert the key of the classification. Any custom code reading KSSK and AUSP directly might need to be updated!
Once the program is done, you can use transaction O1CL to activate the change documents:
In the material master classification screen the menu option Environment/Change Documents is now enabled and will show the changes to classification done:
