The degree to which customization can be achieved varies from simple parameters, such as adding a specific custom field in your sales order, to ones that require complex modification, such as creating a custom transaction by executing several different standard transactions in the background.
There is really no limit to the possibilities with SAP customization and development. However, this does not mean that customization is risk-free. If you don’t check your customizations carefully, they might cause an unwanted side effect for other transactions.
Therefore, before deciding to customize your SAP system, you need to have a thorough understanding of what might be affected by the actions you take
Having completed thousands of successful SAP ERP customization projects with over 2000 enterprise customers. For example, based on customer data gathered over 13 years, here is our list of the Top SAP ERP Customizations
This popular type of customization applies to every change in transactions, reports or a remote function call (RFC).
Another popular type of customization applies to every change in configuration tables, both via SAP Project Reference Object (SPRO) and via direct maintenance (SM30), that impacts a standard executable object.
This type of customization applies to table maintenance. That is, every change in values in custom tables used for configuration that are called by custom code.
This type of customization applies to every change in user exits that was done via transaction SMOD and impacts standard executable object.
Next, layout objects customization applies to every change in layout objects (SAP script, SmartForm) including changes of printing programs.
Code objects customization applies to every change in code units as functions, methods, includes etc., that impacts an executable object.
DDIC objects customization applies to every change in custom data dictionary object definition (table, structure, data element etc.) used/called by custom code.
Finally, note objects customization applies to every note implementation (where the note is part of EHP/SPS) that impacts standard executable object.