Skip to Content

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.

 

CC1.jpg

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

CC Blog 1.jpg

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

CC Blog 2.jpg

 

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)

CC Blog 3.jpg

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

CC Blog 4.jpg

Import results into analysis system

CC Blog 5.jpg

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

CC Blog 6.jpg

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)

CC Blog 7.jpg

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

CC Blog 8.jpg

CC Blog 82.jpg

CC Blog 9.jpg

 

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!

CC Blog 10.jpg

 

Remark:

 

 

 

 

 

To report this post you need to login first.

27 Comments

You must be Logged on to comment or reply to a post.

    1. Anil Vempati

      SAP Provided a 7.5 Instance in the Cloud Application Library. CAL. This instance can be activated on AWS for a small charge to Amazon. That will give you a 7.5 System for getting the Custom code Work list. Hope this helps.

      (0) 
  1. Mingkang Huang

    Nice post.

    I have a question. What’s the name of the report to display CCMW?

     

    =============================================

    4. Custom Code Migration Worklist

    Execute report ?? to display the Custom Code Migration Worklist

    (0) 
  2. Joern Strade

    Thanks for sharing!

    That looks nice.

    I have one question though: Does the “Custom Code Migration Worklist” also contains all custome code developments that need adjustments because auf new DB features (like removal of database hints or other incorrect DB-selects)?

    If not, do you know if there is another (similiar) tool providing this information?

     

    Thanks!

    (0) 
  3. Denis Tislenko

    Cannot get access to the notes 2241080, 2185390. Get the following message in browser:

    This site can’t be reached

    css.wdf.sap.corp’s server DNS address could not be found.

     

    DNS_PROBE_FINISHED_NXDOMAIN

     

    Please advise how to find them. Also Home | SAP Support Portal does not help here

    (0) 
  4. Ruben Hartogs

    Thank you Frank!
    Great post, as always!
    Indeed though: links to SAP Notes on the css.wdf.sap.corp site can only be reached by SAP employees, not by people outside the company.
    The links you provided on the launchpad site will work for everyone.
    Best regards,
    Ruben

    (0) 
  5. Karl Bergström

    Hello,

    We are using a temporary cloudsystem (cal.sap.com) for doing this. But we are not able to connect the cloud system to the onprem Solution Manager system (of security reasons). Is there any workaround for matching UPL data with the Custom Code Worklist, without connecting via RFC?

    Brgds
    Karl

    (0) 
    1. Markus Goebel

      Hello Karl,

      at the moment there is no file export functionality for UPL data. So you can get this only via RFC. In case RFC connection to the cloud instance is not possible for you, you need to do the custom code check from a local NW instance.

      As you apparently still use the SYCM transaction for custom code checks, please note that in NW 7.51 the SAP S/4HANA specific code checks have been fully integrated into SAP Code Inspector and checks have been improved compared to the SYCM tool.

      Therefore it’s highly recommended to use a NW 7.51 system as analysis system and do the custom code checks via code inspector instead of SYCM. For details please see the NW 7.51 documentation.

      http://help.sap.com/saphelp_nw751abap/helpdata/en/3f/2f0b6f8d8045c480293803b57939b4/content.htm

      Best Regards,
      Markus

      (0) 
  6. Karl Bergstrom

    Hello,

     

    we are running the SAPRSEUB program in our test environment and it has been running for 22 days. Do you have any idea for how long “significant runtime” could mean?

    (0) 
    1. Frank Wagner Post author

      Hi Karl,

      it is not completely unusual. I know from other cases where 1-2 days for the regenartion of the indexes happened. The development is aware of the longruning SAPRSEUB program.

      Kidn Regards,
      Frank

      (0) 
      1. Frank Wagner Post author

         

        Hi,

        sorry – I thought 22 hours. Not days. Markus will reply with the component where you should create a ticket for the issue.

        Kind Regards,

        Frank

        (0) 
    2. Markus Goebel

      Hello Karl,

      the runtime should not be more than max. 1-2 days. 22 days is definitely much too long. Can you please open a support message on component BC-DWB-UTL-BRR regarding this excessive SAPRSEUB runtime.

      Best Regards,

      Markus

      (0) 
  7. Manikandan Rajasekar

    Hi Frank,

    Greetings , I have two questions related to SAP S/4HANA Custom code migration.

    1. If a customer has performed a modification in SAP standard object ( not ‘z’ program) then will custom code migration will capture it ?
    2. If custom did not follow the z or Y naming convention – what will happen ?

    How to proceed in such scenarios ?

    Thanks in advance!

    Regards, Mani

    (0) 
    1. Frank Wagner Post author

       

      Hello Mani,

      the S/4HANA Custom Code Check does have the focus to analyse the custom code which does not comply to S/4HANA. The results are independent how you done your modification. The custom code check is comparing your existing custom code with the chanegs in scope and data model which you have in S/4HANA.

      If you did modify a SAP Object which is not changed in S/4HANA the custom code check will not dedect this. Nevertheless you have to adapt this in SPDD phase of the Software Update Mananger (SUM). In this sense you have the same work you would have if you would execute an upgrade within SAP ERP.

      Like said the focus of the S4 custom code check is to provide infromation and adaption task related to the SAP entities whcih will be different in S/4HANA. The standard custom code task which will occur in an SAP ERP upgrade need to be considered aswell. For that the standard tooling /ATC checks, code instector) remain relevant.

      Kind Regards,
      Frank

       

       

      (1) 
    1. Markus Goebel

      Hi Stefka,

      yes, transaction SYCM is deprecated as of NW 7.51. The SAP S/4HANA specific custom code check functionality is now fully integrated into the standard code check tools ABAP Test Cockpit (ATC) / Code Inspector.

      The recommended way to do custom code checks (SAP S/4HANA specific custom code checks as well as any other type of custom code check) is to have a central ATC system on NW 7.51 from where you can then remotely scan any other system in your landscape.

      Doesn’t matter if the to be scanned target system is on ERP 6.0x, SAP S/4HANA 1511 or SAP S/4HANA 1610.

      Please see the following series of blog posts for more details:

      https://blogs.sap.com/2017/02/15/sap-s4hana-system-conversion-challenge-for-your-custom-code/
      https://blogs.sap.com/2017/02/15/sap-s4hana-system-conversion-custom-code-adaptation-process/
      https://blogs.sap.com/2016/12/12/remote-code-analysis-in-atc-one-central-check-system-for-multiple-systems-on-various-releases/
      https://blogs.sap.com/2016/12/13/remote-code-analysis-in-atc-technical-setup-step-by-step/
      https://blogs.sap.com/2016/12/13/remote-code-analysis-in-atc-working-with-baseline-to-suppress-findings-in-old-legacy-code/
      https://blogs.sap.com/2016/12/22/remote-code-analysis-in-abap-test-cockpit-atc-faq/
      https://blogs.sap.com/2017/02/27/remote-code-analysis-in-atc-for-developers/
      https://blogs.sap.com/2017/02/27/remote-code-analysis-in-atc-working-with-exemptions/

       

      We will soon also update this blogpost to reflect this information(currently we cannot yet change this blogpost as it’s in archive/read only mode.)

      Best Regards,

      Markus

      (2) 
  8. Cheriyan Sam

    Dear Frank,

    Is it still available on a NW 750 system, is there any way we can get this functionality on a NW 740 system?

     

    Regards,

    Sam

     

    (0) 
  9. Frank Wagner Post author

    Hi Sam,

     

    I´m no longer working in the System Conversion / S-List topic. But as far as I know there was no “downport” of this functionality into 7.40 stack. The Sycm is available from 7.50 onwards.

    Kind Regards,

    Frank

     

    (0) 

Leave a Reply