Scribd
Upload
3 views1 page

Custom Code Analysis

The document discusses the challenges of managing custom SAP code, which constitutes 28% of business process transactions and often includes duplicates, clones, and unused elements. Key questions addressed include the cost, complexity, quality, and security of custom code. LiveCompare is presented as a solution to identify and manage problematic custom code effectively.

Uploaded by

Anthony Vilchis Medel
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
3 views1 page

Custom Code Analysis

The document discusses the challenges of managing custom SAP code, which constitutes 28% of business process transactions and often includes duplicates, clones, and unused elements. Key questions addressed include the cost, complexity, quality, and security of custom code. LiveCompare is presented as a solution to identify and manage problematic custom code effectively.

Uploaded by

Anthony Vilchis Medel
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Better Manage SAP Custom

Custom Our benchmark studies reveal that 28% of the transactions


Code
Code
used to support business process are custom. Systems
contain duplicates and clones of standard SAP programs,

Challenges
as well as a huge amount of unused custom code. Custom
code often grows in complexity making it hard to change,
hard to test and hard to support.

 How much does our custom code cost?


Answer 

What custom code will break?
What custom code can be retired?
Key 

How complex is our custom code?
What is the quality of our custom code?
Questions  How secure is our custom code?

Manage LiveCompare identifies custom code that will break; all the
duplicates that can be eliminated; all the clones that can return to
Custom standard; all the unused objects to be retired; all the complex
custom code to be refactored; all the unsecure custom code; all the
Code slow code and all the out-of-date code.

[Link]

You might also like