Further Recommendations for Custom Developments

The tab Custom Developments shows details about the impact of the planned maintenance activity to your custom developments. Additionally to the documentation in the application, in this topic you get further recommendations for your custom developments according to the impact categories.

There are further comprehensive recommendations for the following impact categories.

Custom Code using deleted SAP ABAP objects

Recommendation: Adjustment required

In case of deleted SAP DDIC objects that you refer to in your programs, you should create respective objects in your custom namespace. In case of SAP programs, functions or methods you should look for other SAP programs replacing the deleted programs and that are released for customer usage. Alternatively, you create the required functions in your custom namespace. For this purpose, you should not copy (clone) the deleted SAP object into your namespace. This can lead to follow-up issues as described in the categories below adressing cloned programs.

Clones with changed SAP references and originals

This impact category displays clones if the following conditions are true:

the clone includes or calls SAP repository objects that are changed in the new SAP software version
the original SAP objects from which you created the clone is changed in the new SAP software version or the clone includes further cloned SAP objects for which the original SAP object changes after the upgrade

Recommendation: Adjustment required

You should carefully inspect and test clones in this impact category in a upgrade test system. You could use the tool Clone Finder in your development system to perform this analysis. You can access the Clone Finder by calling transaction CC_APPS.

Custom code using changed obsolete SAP functions

Recommendation: Adjustment required

SAP does not guarantee correct functioning of obsolete functions in upgraded software versions. You should replace these functions by suitable released successors.

Note Note

The Scope and Effort Analyzer cannot detect functions that will become obsolete with the new release. Therefore, you should use the Reference Analysis that you can start in transaction CC_APPS to look for further obsolete functions in a upgrade test system.

End of the note.

Custom code using changed unreleased SAP functions

Recommendation: Adjustment required

SAP does not guarantee correct functioning of unreleased functions in upgraded software versions. You should replace these functions by suitable released SAP functions. At least, you have to carefully inspect and test the changed SAP functions.

Custom code with syntax errors after upgrade

Recommendation: Adjustment required

Perform an extended syntax check for all of your custom developments in a upgraded test system to determine the impacted custom code and to create a work list for your developers. You can use the ABAP Test Cockpit or the Code Inspector to perform this syntax check as a mass job.

Custom code using changed SAP references

Recommendation: Adjustment required

Usually, most custom code impacted by an enhancement package or support package upgrade reside in this category. Generally, most of the delivered SAP changes are not critical and do not require development rework. However, the Scope and Effort Analyzer is not able to perform a detailed impact analysis on code level because the respective new source code is not available at the point in time of the analysis.

Perform a detailed impact analysis of your custom developments as soon as an upgraded test system is available to determine critical changes and to create a work list for your developers. You can use the tool Custom Development Management Cockpit in Solution Manager to perform this analysis.

Additionally, you perform regression tests for all business processes using custom code with changed references. Refer to the test scope optimization section of this scope and effort analysis for more information.

Custom code using obsolete SAP functions

Recommendation: Adjustment required

You should replace obsolete functions by suitable released SAP functions in the course of this planned maintenance project. This measure will help avoiding future conflicts.

Clones with changed SAP original

Recommendation: Adjustment required

If no other parts of the cloned program change, the clone will most likely function as before. Therefore, no immediate development action is required. However, you should perform regression test of the business processes using these clones to check if the respective clones still work as designed and required. Refer to the test scope optimization section of this scope and effort analysis for more information.