Custom Code decommission - Transaction usage

[KumarAakash]

Hello All - we are performing the analysis of transaction that are not used in Production and are candidate for decommission, the challenge we are facing the user base confirm on transaction is used bt the cockpit is showing no usage , how and what to use to get right amount of information  

[david_song · Accepted solution]

Function Custom Code Decommission gets transaction usage data from ST03N on managed systems. So please logon production can run transaction ST03N to confirm whether the transaction usage can be recorded. If a transaction execution can not be recorded by ST03N, then it is out of the scope and Custom Code Decommission will also not be able to show its usage.

[KumarAakash · Accepted solution]

thanks David - we did check in ST03N and GRC system also , there is no usage picked by the system but user did confirm they are using the custom transaction .

[david_song · Accepted solution]

ST03N will only count an object as used when it is actually executed. When Transactions are loaded into memory but not executed yet, they will not be counted by ST03N. Please check more detailed explanation in below KBA:3113122 - Custom Code PROG is missing Last Usage information "Resolution In the case of a report that means: 1) Starting the report (e.g. press F8 in SE80) causes - that the selection screen (dynpro) is generated - the selection screen (dynpro) is shown - the ABAP report is loaded into memory (triggering SBLM) - but no single line of ABAP code was called/executed to this point. (Unless you have defined a load-of-program event in the report) 2) Executing the report (e.g. press F8 when your selection screen is visible for inputs) triggers the execution of the start-of-selection part in the report, which is an actual call of ABAP code and therefore triggers SCMON log-writing. The assumption is that a user started the transaction/report but did not actually execute it. Therefore no ABAP code was actually called/executed and therefore it would be correct that SCMON did not write a record."

[KumarAakash · Accepted solution]

Hi David - we did check ST03N , bt there was no usage reported over there so it seems program was never called till selection screen tooo.. but we are checking with Business to get confirmation if transaction is called as Batch Job but not as dialog user .. can you provide some insight if the program is called via different program will SCMON and SAP Decommission Cockpit will be able to capture is as used or not being used ?

[david_song · Accepted solution]

Only transactions/programs that are recorded by ST03N/SCMON will be analyzed by Decommitioning Cockpit.

[KumarAakash · Accepted solution]

Thanks for response , now the biggest question that are being asked during decommission of custom code discussion is, the app suggest most of the custom code based on usage as "ready for decommission " , so if program is not called via se38/SA38/Custom transaction that there is chance customer will end up decommissioning custom object which could be leverage in other program hence causing problem. The challenge grows even bigger when the discussion is for object not equal to program or transaction , Class, FM , other Dev type is creation lot of confusion and hence there should be a guideline on how and what should be done to decommission custom code ... can you sugges the best way

[david_song · Accepted solution]

When the usage date for an object can not be recorded in ST03N & SCMON, then the object will be listed as "ready for decommission" in Decommitioning Cockpit project. This is how Decommitioning Cockpit function works technically, and sometimes may also be seen as limitation of the function.

[KumarAakash · Accepted solution]

Thanks @david_song - this information is really helpful of the way Custom decommission cockpit has been designed... so all custom details without usage will hve false positive feedback as decommission and is there a way we can provide right information to client of usage to make the decision on the decommission.. or this is only and last resort we have to add some assumption and factor there could be usage but not identified due to technical limitation of the tool and process .

[david_song · Accepted solution]

Hi Kumar, in general I would say the Decommissioning Cockpit function has been working fine for decades in helping many customers indentifing unused objects. I haven't seen 'false positive' entries during support. It is possible that certain customer may have unique custom codes that may not be recorded due to limitation, but that should be very rare case. In order to discuss further on the transaction usage not recorded symptom, you can raise a support ticket under component SV-SMG-CCM for detailed checking.