- SAP Managed Tags:
Hi
the successor of UPL is SCMON
these functions are used to identify which abap artifacts have to be adapted for S/4HANA, Unicode, Hana and do the housekeeping
comparison of the different Transactions:
ST03N: see the usage of reports and transactions
UPL (Usage & Procedure Logging): see the usage of all ABAP Objects including details like functions/classes/methods/… (Obsolete, started from CC_APPS or Solution Manager )
newest Transaction:
SCMON or /SDF/SCMON (Depending on Product / Release)
see the usage of all ABAP Objects including details like functions/classes/Methods/… including which function calls this object, which helps you to find the reason for the usage
because this generates way more data than upl, it is not so easy to analyze the results of SCMON
to support the analysis, a new Transaction /NSUSG is provided, which aggregates the information so it can be used for custom code Management (Code Inspector or ATC)
if the transaction is not available in your System, install the following support stack or maintain note
https://launchpad.support.sap.com/#/notes/2643357
Installation of Transaction SUSG
https://launchpad.support.sap.com/#/notes/2701371
Recommendations for aggregating usage data using transaction SUSG
to implement the notes, transport based corrections need to be active (TCI, see SAP Note 2187425)
how to use the /NSUSG Transaction:
Activate the Aggregation:
Create a Snapshot:
Download the Snapshot:
an xml file is created:
xml can be opened for example with excel:
save excel as text or use clipboard as a input-list to filter used objects in ATC/Codeinspector
related links:
https://blogs.sap.com/2018/10/01/s4hana-1809-custom-code-migration-with-new-fiori/
https://blogs.sap.com/2017/04/06/abap-call-monitor-scmon-analyze-usage-of-your-code/
the successor of UPL is SCMON
these functions are used to identify which abap artifacts have to be adapted for S/4HANA, Unicode, Hana and do the housekeeping
comparison of the different Transactions:
ST03N: see the usage of reports and transactions
UPL (Usage & Procedure Logging): see the usage of all ABAP Objects including details like functions/classes/methods/… (Obsolete, started from CC_APPS or Solution Manager )
newest Transaction:
SCMON or /SDF/SCMON (Depending on Product / Release)
see the usage of all ABAP Objects including details like functions/classes/Methods/… including which function calls this object, which helps you to find the reason for the usage
because this generates way more data than upl, it is not so easy to analyze the results of SCMON
to support the analysis, a new Transaction /NSUSG is provided, which aggregates the information so it can be used for custom code Management (Code Inspector or ATC)
if the transaction is not available in your System, install the following support stack or maintain note
| SAP_BASIS 731 | SAPKB73124 | ||
| SAP_BASIS 740 | SAPKB74021 | ||
| SAP_BASIS 750 | SAPK-75014INSAPBASIS | ||
| SAP_BASIS 751 | SAPK-75108INSAPBASIS | ||
| SAP_BASIS 752 | SAPK-75204INSAPBASIS | ||
| SAP_BASIS 700 | SAPKB70037 | ||
| SAP_BASIS 701 | SAPKB70122 | ||
| SAP_BASIS 702 | SAPKB70222 |
https://launchpad.support.sap.com/#/notes/2643357
Installation of Transaction SUSG
https://launchpad.support.sap.com/#/notes/2701371
Recommendations for aggregating usage data using transaction SUSG
to implement the notes, transport based corrections need to be active (TCI, see SAP Note 2187425)
how to use the /NSUSG Transaction:
Activate the Aggregation:
Create a Snapshot:
Download the Snapshot:
an xml file is created:
xml can be opened for example with excel:
save excel as text or use clipboard as a input-list to filter used objects in ATC/Codeinspector
related links:
https://blogs.sap.com/2018/10/01/s4hana-1809-custom-code-migration-with-new-fiori/
https://blogs.sap.com/2017/04/06/abap-call-monitor-scmon-analyze-usage-of-your-code/
1 Comment
