Skip to Content

Hi everyone, in this blog I’m going to talk about some of the basic configurations of Customer Code Check (or Customer Code Migration) when doing a S/4HANA System Conversion.

Foreword

The following picture shows the procedure and landscape involved in the task.

/wp-content/uploads/2016/08/01_1016833.jpg

Basically, you’ll need an AS ABAP NetWeaver 7.5 system as shown in the above picture (the evaluation system doesn’t have to be a S/4HANA system, any AS ABAP NW 7.5 system will be ok), at first we thought the new Solution Manager 7.2 will do so, but unfortunately Solution Manager 7.2 was build on NetWeaver 7.4.

References

Custom Code Migration Worklist –  Application Development on AS ABAP – SAP Library

Using the Custom Code Migration Worklist –  Application Development on AS ABAP – SAP Library

2241080 – Custom code check content for SAP S/4HANA on-premise edition

https://launchpad.support.sap.com/#/notes/2241080

How we did it


1. On ERP Source System


1.1 Implement SAP Note 2185390, follow the the Note to perform manual-activities.

/wp-content/uploads/2016/08/02_1016841.jpg


1.2 Run report SYCM_DOWNLOAD_REPOSITORY_INFO


Run report SYCM_DOWNLOAD_REPOSITORY_INFO with SE38 (we’ll talk about the error “the where-used index is not up-to-date” later on), you may want to run it as a background job if you have a lot of customer developed programs.


Customer Namesapce = /0CUST/

/wp-content/uploads/2016/08/04_1016842.jpg


1.3 Download the Customer Repository ZIP file


Wait until the job gets finished, then you should be able to download the ZIP file to your local computer.



2. On the Evaluation System (NW 7.5 System)


2.1 Upload the Customer Repository ZIP file


Upload the Customer Repository zip file into the evaluate system by execute program SYCM_UPLOAD_REPOSITORY_INFO with SE38, give it a extraction name.


/wp-content/uploads/2016/08/020_1016864.jpg


2.2 Import the SMB


Download the latest patch of Simplification Database Content from SAP launchpad support one app by doing a quick search CCMSIDB.


Import the downloaded simplification database zip file into evaluate system through report SYCM_UPLOAD_SIMPLIFIC_INFO with SE38.


/wp-content/uploads/2016/08/05_1016865.jpg

2.3 Analyze the Impact of the Simplification


Launch the Custom Code Migration Worklist by using transaction SYCM, fill the SAP System ID and Extraction Name and click on execute.


/wp-content/uploads/2016/08/021_1016866.jpg

The results will give you a glance of the customer objects affected by the simplifications

/wp-content/uploads/2016/08/022_1016882.jpg


You can find more information like SAP Object Name, Application Component, most importantly the Simplification Category and relevant SAP Note

/wp-content/uploads/2016/08/023_1016883.jpg

As mentioned in the SAP document, the follow paragraph gives an overview of the Simplification Category


Simplification Category: Represents the category of the simplification item

The following categories are provided:

  • Usage of functionality not supported anymore: Usages of this SAP object must be removed from the custom code.
  • Usage of functionality not recommended anymore: SAP recommends to remove usages of this SAP object from the custom code.
  • Syntactically incompatible change: Custom code needs to be adapted as described in the related SAP Note.
  • Semantically incompatible change : Custom code needs to be adapted to the new semantics as described in the related SAP Note.
  • Change with performance impact: Usages of this SAP object might have impact on your custom code.

3. Error “the where-used index is not up-to-date” in the ERP Source System

/wp-content/uploads/2016/08/e01_1016884.jpg

To solve this problem, we can perform the following activities in the ERP system:

1. Run report SAPRSEUJ with SE38

2. Wait until the job EU_INIT gets finished, then run the following reports with SE38 as background job:

     SAPRSEUB

     SAPRSEUC

For more information about how to solve this problem, please check the following SAP Notes:

     2234970 – Job EU_INIT

     18023 – Jobs EU_INIT, EU_REORG, EU_PUT

That’s all, I hope this will help you and I’m willing to receive your feedback!

Regards,

Michael

To report this post you need to login first.

10 Comments

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

      1. Madhu B

        Hello Michael,

        Thanks for the blog, SAP Note 2185390 seems to be applicable for NW 700 and above.

        Read few blogs and SAP supports S/4 HANA migration from 4.6c also. How to perform custom code analysis for SAP R/3 4.6C , any specific note for this. Appreciate your help on this.

        Thanks

        Madhu

        (0) 
        1. Michael Hu Post author

          Hi Madhu,

          You’re right, SAP supports system conversion from 4.6c to S/4HANA, but you do have to perform an system upgrade to upgrade your source system to ERP 6.0 first, I think you’ll be able to perform the customer code analysis once your system finished the upgrade process.

          Unfortunately, I can’t find the documents or notes for R/3 4.6c, and we don’t have the test environment here, but I can give you some information about the system upgrade to ERP 6.0.

          For upgrade to ERP 6.0, you can check the SAP documents on system upgrade with software update manager, for example NW 7.0, you can check the following link, looking for the Upgrade Master Guide as sell as Upgrade and Update Guides (lots notes in these documents)

          SAP NetWeaver 7.0 – SAP Help Portal Page

          Regards,

          Michael

          (0) 
          1. Madhu B

            Hello Michael,

            Thank you for the reponding back and the inputs. I have already gone through the few blogs and notes wherein it says that 4.6c has to be upgraded to EHP7 as S/4 HANA supports  Unicode. What i am really looking right now is custom code analysis for 4.6c before i go for upgrade then unicode conversion and making it ready for S/4 HANA migration.

            Regards

            Madhu

            (0) 
            1. Michael Hu Post author

              Hi Madhu,

              You’re right S/4HANA only supports unicode, as note 2269871 mentioned, SUM support S/4 system conversion start releases from SAP ERP 6.0 including enhancement packages up to 7, means from EHP 0 to EHP 7 are well supported.

              I think the system upgrade and unicode conversion could be done just in one step with the new SUM software update manager, the actual S/4 system conversion also use this tool, you do need a license to generate and download the system conversion files for S/4.

              Michael

              (0) 
        2. Frank Wagner

          Hello Madhu,

          Michael Hu describes it correctly a move from R/3 4.6c is possible in a two-step approach. You first have to upgrade your systenm to SAP ERP 6.0 and in a second step you can do a system conversion to SAP S/4HANA. See aswell:

          SAP S/4HANA, on-premise edition – Transition Paths

          Accordingly our content related to the S/4 System Conversion is focused on SAP ERP 6.0, because that is the start release for a system conversion to S/4HANA 1511.

          Kind Regards,

          Frank

          (0) 
          1. Madhu B

            Hello Frank,

            Thank for the reply, what i am looking at is custom code analysis for 4.6c system before i go for upgrade and unicode conversion. Do i need to spend additional license cost here for upgrade , unicode conversion to ECC 6.0 EHP7 and again license cost for S/4 HANA 1511.

            Regards

            Madhu

            (0) 
            1. Frank Wagner

              Hi Madhu,

              do not know about the license cost – what I can say is that S/4HANA is a different product than SAP ERP and you need a separate S/4HANA license.

              The logic to extract custom code from source system is available for systems based on SAP Basis 700 (see the note 2185390 – https://launchpad.support.sap.com/#/notes/0002185390)


              At the end the custom code part is just one corner stone of a project to go from 4.6c to S/4HANA. As far as I know the starndard maintenance window for 4.6c ended in 2010. In the meantime (even in SAP ERP6.0) a lot of new business processes are established which are supported by the SAP software. I would recommend to start to identify the   custom code usage (based on experience just ~50% of existing custom code is used at all) and the opportunities to go back to standard (S/4HANA).    

              Kind Reagrds,

              Frank

              (0) 
  1. Jonathan Ma

    I am getting where-used index not up to date error even though SAPRSEUB, SAPRSEUC and SAPRSEUJ, EU_INIT are all run successfully. Any idea? What exactly SYCM_DOWNLOAD_REPOSITORY_INFO checks to see if index is up to date or not?

    (0) 

Leave a Reply