New Change Analysis (ABAP) Tool with ST-A/PI Release 01S*
this is my first blog on SCN and I hope you will enjoy it.
I am going to present a new Tool – Change Analysis (ABAP) – to identify what Changes have been made in an SAP ABAP System.
Changes can be moved or made in totally different ways and affect different areas in an ABAP System.
With ST-A/PI Release 01S* SAP introduces a new toolset – Backoffice Tools – in ST13 which includes the Change Analysis (ABAP). With the new tool you can identify different kind of changes implemented in a SAP System – NetWeaver based, ABAP – during a given timeframe:
– Starttime & -date of Active Hosts
– OS/DB/SAP Parameter Changes
– Transport Requests – Imported from other System
– Transport Requests – Created in current System
– Change time & -date of Specific Program/Function Group/Class
The tool can be accessed directly in the ABAP System via transaction ST13 –> BACKOFFICE_TOOLS –> Change Analysis (ABAP)
We have also created a Knowledge Based Article 2223746 – Backoffice Tools – Change Analysis (ABAP) in ST13 (http://service.sap.com/sap/support/notes/2223746). All information on how to use the tool is documented in this KBA. Besides, we published an article as a short “How To Guide” on the SCN under the following link: http://scn.sap.com/docs/DOC-69342
Important Note/Constraint for the execution of the Change Analysis (ABAP) tool: Depending on the selected timeframe the required execution time of the tool can increase significantly. Please choose proper selection criteria to restrict the result set to a minimum – normally < 7 days should be sufficient. In maximum you can select a timeframe of 30 days only.
Remark: in some customer systems you might face an ABAP Runtime Dump
CONVT_CODEPAGE – CX_SY_CONVERSION_CODEPAGE.
One option to resolve this issue is to manually apply SAP Note 1813468 – Web Dynpro: Conversion for non-printable chars (NON-UNICODE).
A fix for this Dump was released within ST-A/PI Release 01S* SP2.
Feel free to try it out and let me know your feedback.