Modification and Enhancement Adjustment Planning

This section deals with modifications, which are changes to objects of the SAP standard.

There are two types of modifications: changes to the translation of an object text, and changes to the object itself.

In addition, the Enhancement Framework allows enhancements, such as source code plug-ins, implementations of the new kernel-based BAdI, and class enhancements. We recommend using the Enhancement Framework to enhance or adapt SAP development objects.

Changes to the Translation of an Object Text

The changes are made in the translation environment (transaction SE63) or in the ABAP Workbench. An SSCR key is not required.

Modifications and Enhancements of SAP Objects

You possibly need an SSCR key to perform the modification adjustment. Get the key before you start the update. For more information, see SAP Support Portal at https://support.sap.com/sscr Information published on SAP site .

Release upgrade only: All modified standard SAP objects are displayed for adjustment in transaction SPDD or SPAU. Objects that SAP no longer delivers are deleted. If you want to keep these objects, you have to accept the modifications in transaction SPDD or SPAU.

Enhancement package installation and SPS update: All modified standard SAP objects that are contained in a software package that is to be applied to your system are displayed for adjustment in transaction SPDD or SPAU. If you want to keep these objects, you have to accept the modifications in transaction SPDD or SPAU.

All enhancements that you have to adjust are shown in transaction SPAU_ENH. In contrast to modifications of source code units, you only have to adjust enhancements if the underlying SAP development objects were deleted or changed in an incompatible way.

Make sure that you perform the adjustments in transaction SPAU_ENH after the adjustments in transaction SPDD or SPAU and not the other way around.

The modification adjustment of ABAP Dictionary objects occurs during production operation. This is possible since the complete version management is available in the shadow system. The remaining Repository objects are still adjusted at the end of the update.

Caution

Potential ABAP Dictionary objects and data loss because of passive deletion of objects

Be aware of the following issue: You want to perform a system upgrade or a conversion to a product based on SAP NetWeaver 7.50 or higher, and you have created new SAP objects (for example a structure or data element) as part of a manual correction instruction of an SAP Note, either manually or by executing a report attached to an SAP Note. However, the target support package of the upgrade does not include these corrections.

The reason is that the Software Update Manager does not rescue the objects during the SUM run because they are registered in the system as modified SAP objects. Therefore, they do not exist in the target release anymore, but are deleted passively. The objects will show up as deleted objects in SPDD or SPAU. If ABAP Dictionary objects are not manually re-created during SPDD, data loss can occur. For example, this can happen if a structure is used as a table append. You possibly encounter such a situation, for example, if you have implemented larger legal changes, such as Goods and Services Tax in India.

As a solution, see SAP Note 2513585 Information published on SAP site for more information and for information about preventing the potential object loss, especially if you were requested to execute a report to create ABAP Dictionary objects. Contact SAP Support for assistance in identifying the objects to be saved.

Modification Adjustment in the First System (Development System)

You have to test the modification and enhancement adjustment in a development system that has the same SAP system release and that has been modified in the same way as the production system. If the development system contains more modifications or enhancements, or has a different Support Package level, contact an experienced SAP consultant for help. The following explanation assumes that the levels of modification are identical.

The list of objects that has to be adjusted in your SAP system is determined in the ADJUSTCHK phase. This phase is executed in the Configuration roadmap step and runs between the import of the substitution set and the end of the production period.

The list is part of the log file UMODPROT.<SID> that is located in the subdirectory <SUM directory>/abap/log.
The ABAP Dictionary objects (tables, data elements, domains, and so on) are adjusted during production operation. However, if you choose scenario strategy Single System, they are adjusted during downtime before the ABAP Dictionary is activated on the original system.

The adjusted objects are collected in a repair that is released to a transport request. You have to release the tasks of the SPDD transport request. Do not release this transport request. Instead, flag it using the menu option Modification Adjustment Assign Transport.

Note

Only adjust the objects. However, do not activate them using transaction SE11 (ABAP Dictionary Maintenance).
Modified or enhanced repository objects (reports, screens, and so on) are adjusted towards the end of the update. At this stage, the import of SAP objects has already been completed. However, the old modified version is still available in the version database. As with ABAP Dictionary objects, all changes are released to a transport request that is flagged and then exported and registered by the Software Update Manager.

If you need to adjust enhancements, release these adjustments to the flagged transport request that already contains the adjusted modified objects. Adjust all modifications before you adjust the enhancements.

Towards the end of the update, the Software Update Manager exports the request to the transport directory /usr/sap/trans and registers it for transport in the umodauto.lst file.

Note

Make sure that the user <SID>adm has write permissions for the file <DIR_TRANS>/bin/umodauto.lst.

Modification Adjustment in Subsequent Systems

For the quality assurance and production system, we recommend that instead of adjusting modifications and enhancements manually, you automatically transfer the transport requests exported from the first system: one for the ABAP Dictionary objects adjusted using transaction SPDD and one for the Repository objects adjusted using transactions SPAU and SPAU_ENH.

The ADJUSTPRP phase in the Configuration roadmap step prepares the requests that you entered in phase SUMASK_SPDD_SPAU from the development system to be transferred. The phase checks whether all the modifications identified in the system are handled by transport requests. If this is the case, you do not need to perform a modification adjustment.

For a detailed description of the modification adjustment function, see the SAP Help Portal for your target SAP NetWeaver release at http://help.sap.com and see Start of the navigation path Application Help Next navigation step SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP Application Development on AS ABAP Customer-Specific ABAP Development Changing the SAP Standard (BC) Modifying the Standard Modification Assistant Upgrade Procedure / Support Packages (link at the bottom of Modification Assistant page) End of the navigation path .