- SAP offers Custom Code Management Tools which allows for SAP custom code manufacturing.
- We cover the Solution Manager, CCLM, RDPD, TEA, CDMC, BPCA and the SAP Clone Finder.
Introduction to Custom Code Management Tools
SAP Custom Code Management Tools are items that can be leveraged by coders. In this article, your will learn about the major code management tools for SAP.
The Types of SAP Custom Code Management Tools
In the book Managing Custom Code in SAP, the following tools are mentioned:
“Solution Manager: Custom code can be managed in Solution Manager.
CCLM: Custom code can be measured in terms of magnitude. There is something called Custom Code Lifecycle Management (CCLM) applications.
RDPD: There is a Reverse Business Process Documentation tool (RDPD) that is used as a process to map custom code to the business process.
TEA: There is a Transport Execution Analysis report, this allows one to obtain an overview of the current management practices for your custom code landscape.
CDMC: The Custom Development Management Cockpit (CDMC) is used to determine the impact of an SAP upgrade on the custom code library.
BPCA: The Business Process Change Analyzer (BPCA) is used to determine the impact on your custom code library of an upcoming change, including the automatic generation of optimized test plan.
SAP Clone Finder: Is used to identify code that you have cloned from SAP standard and comes with impressive comparison capabilities to help revert back to the standard when possible. The code inspector provides a quantitative measure of quality of your custom code against predetermined metrics and patterns.”
Solution Manager is very well known, however, it is becoming actually less frequently used to manage either development or configuration details, as is covered in the article End of the Line for SAP Solution Manager.
But a number of the items listed below, are actually within the Solution Manager application. SAP provides misleading information on how customers generally respond to Solution Manager.
The statements made in this video simply don’t occur on projects. Solution Manager has very significant overhead and while it can be advantageous to document configuration and development in Solution Manager, (Solution Manager allows to store the link so that you can go right out to the SAP transaction and configuration). But generally, people don’t like using Solution Manager. And Solution Manager’s use on projects continues its long decline.
Google Trends shows what we have seen on projects. Solution Manager is just less and less relevant. SAP put major capital behind making Solution Manager as the thing through which everything on a project was to flow, and it failed.
CCLM is intended to reduce custom code. This is explained in the following video.
The problem with this is that SAP is always trying to reduce custom code, even when the custom code is important for the business processes. This is covered in the article How SAP Used and Abused the Term Legacy.
CCLM is actually within Solution Manager.
The CCLM provides insight to the various categories of development objects.
- “Custom Code Usage App
- Custom Code Severity App
- Custom Code Quantity App
- Custom Code Quality App
- Custom Code Criticality App” – SAP
“The analysis results referring to the SAP standard business process reference model can be converted into a Solution Manager project and can be adapted to the customer specific business processes. Customer specific adaptation of a process structure means including customer’s transactions and programs, defining additional customer specific process steps or individualization of SAP standard process steps. To prioritize which business processes need an adaptation, SoDocA provides detailed information about the usage and frequency of used business processes. This includes also a deep insight into customer specific development and their usage penetration in the productive environment. SAP provides analysis content with more than 14.000 inspections to jump-start the initial documentation of any productive SAP environment. The overall number of SAP inspections will be increased over the coming years to support the whole SAP Business Suite including the different industry solutions. Apart from SAPs provided inspections, the customer has the full flexibility to define their own specific inspections to individualize the discovery process.”
SAP Clone Finder
This is designed to find any code that has been cloned in the past. It will rank how close the SAP object is to the object that was cloned.
More quotations from the book Managing SAP Custom Code are as follows:
“All SAP systems have custom code. Over time, the amount of custom code increases as new features are added and business processes mature and evolve. Custom code may be added to your system in large chunks, delivered as part of a project, or evolve organically over time as part of “business as usual.”
As a general rule, software developers spend much more time reading code than writing code. Most of the time, a developer will need to read and understand existing legacy code before a new feature can be added. This leads to the obvious conclusion that easy to read code can be considered good code because it makes the job of the developer easier.”
92% of SAP ECC implementations are moderately or extensively customized. As part of S/4HANA messaging, SAP has been proposing that customization will decrease significantly in the future, but there is little reason to think this will be the case. Most SAP projects were sold under the idea that they could be implemented with very little custom code, but that is the standard position to hold when trying to sell SAP.