Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
Wagnerfr
Active Participant
42,253

Custom Code Migration Worklist


 

With the Custom Code Migration Worklist (technically part of SAP NetWeaver 7.5) a customer can check if his SAP Business Suite custom code complies with the scope and data structure of SAP S/4HANA, on-premise edition. The following figure describes basically the supporting custom code management approach related to SAP S/4HANA.

 



Figure 1: Custom Code Migration Worklist at a Glance

 

 

In the context of Custom Code Migration Worklist a central component is a data store called “Simplification Database". This database contains information about which SAP objects changed between the classical Business Suite and SAP S/4HANA. For each changed object, a SAP note is referenced describing what has been changed, why it has been changed and how custom code needs to be adapted.

The relevant and release-dependent Simplification Database can be downloaded as a ZIP file from the SAP Service Marketplace and imported in a SAP NetWeaver 7.5 system.

  • See SAP Note 2241080

  • The ZIP file can be imported into SAP NetWeaver 7.5 system using program SYCM_UPLOAD_SIMPLIFIC_INFO.


 

In addition to the information about changed SAP objects, the custom code needs to be scanned for references to these SAP objects. The customer can run the Custom Code Analyzer to extract these references. The resulting file can be imported in the SAP NetWeaver 7.5 system.

  • See SAP Note 2185390

  • The Custom Code Analysis Result file can be imported into SAP NetWeaver 7.5 system using programSYCM_UPLOAD_REPOSITORY_INFO


 

With executing the Custom Code Migration Worklist the information about the current custom code base is checked against the content of the Simplification Database. This custom code information includes modifications and enhancements to SAP code as well as customer-owned main objects, respective where-used list information and possibly available usage information (UPL). The Custom Code Migration Worklist is provided in an ALV-like list (including XLS download opportunities). Besides the pure listing of customers code entities which do not comply with the SAP S/4HANA data structure and scope additional information (based on SAP notes) and recommendations will be included in the resulting list. Customers can navigate from the worklist to a corresponding SAP Note. The dedicated SAP Notes then will give the explanation about the technical change and how the related custom code needs to be adapted. Based on the results, the individual custom code analysis results and the provided adaption recommendations, the customer can plan and adapt his custom code to comply with the SAP S/4HANA data structures and scope.

 

Custom Code Migration Worklist - The Steps


 

1. Simplification List Content (CCMSIDB)

a. Download component CCMSIDB from SMP

See SAP Note: 2241080




b. Upload zip-file into analysis system using report SYCM_UPLOAD_SIMPLIFIC_INFO




 

2. Create Custom Code Metadata Export (on Dev/QA-System)

If where-used index is not up-to-date à execute report SAPRSEUB (Note: this might have a significant runtime)


Implement SAP Note 2185390
Includes report to create metadata zip-file (to be scheduled as batch job)
Also includes the download feature for the collected content



Import results into analysis system



3. Get usage data of productively used custom code


Usage and Procedure Logging (UPL) needs to be activated in Production System and available in Solution Manager.
Note: RFC-connection betweenanalysis system and SolMan needs to be set-up



4. Custom Code Migration Worklist


Execute report to display the Custom Code Migration Worklist


Contained are objects in use that are affected by simplification items:
- Syntactically (e.g. material number field length extension)
- Semantically
- Use of no more existing functionality
- Use of new functionality
is mandatory

Not in scope
: SAP HANA code optimization (e.g. for performance)


SAP-Notes will be referenced to explain the necessary resolution tasks


Code adaptation may happen before (using transports) or after System Conversion (e.g. for initial dev system conversion)



To reduce and prioritize the work list use the UPL data collected in Solution Manager






 


NOTE: Prepare your ABAP code for SAP HANA in general


In general existing ABAP code runs on SAP HANA as before (exception: DB specific code, aforementioned incompatibilities due to simplification).

However: Database migration to SAP HANA is a good opportunity for tuning!



 

Remark:

 

 

 

 

 

27 Comments