Transaction SYCM recommends unrequired custom code adaptations

[digantogos]

We recently migrated to S/4 HANA 1605. SYCM recommends around 885 custom object adaptations. After exploring an object for adaptation it was found that the custom object references vbtyp element which is passed on to a BAPI. Both the BAPI structure and custom code VBTYP reference is of ™ Character Length 1. The note says vbtyp is now of 4 characters but standard table is still maintaining character 1 for the field even after SPDD activity.

Please advise on the activity to follow.

[Sandra_Rossi]

Which BAPI? Which parameter?

[digantogos]

Can someone explain purpose of tcode SYCM generated custom object list when compared with simplification database zip file? I am getting a lot many custom objects that shows need to adjust. But approach to do such adjustment is not indicated. An example can surely help uncover this mystery.

[schneidermic0]

Hi Diganto,

Transaction SYCM refers for each finding to an SAP Note. This SAP Note should describe how to solve the findings.

In the example related to data element VBTYP, SYCM should refer to SAP Note 2198647 - S/4 HANA: Data Model Changes in SD. Attached to this note you find a cookbook for the field length extension of VBTYP. As described there, data element VBTYP was not extended, but new data elements were introduced (e.g. VBTYPL) with a length of 4 characters.

I hope this helps.

Michael

P.S.: It is recommended to use ATC for custom code analysis (instead of using custom code migration worklist in transaction SYCM), if possible. Please refer to the following blogs:

• SCN-Blog „SAP S/4HANA System Conversion – Challenge for your custom code” by Olga Dolinskaja
  https://blogs.sap.com/2017/02/15/sap-s4hana-system-conversion-challenge-for-your-custom-code/
• SCN-Blog “SAP S/4HANA System Conversion – Custom code adaptation process” by Olga Dolinskaja
  https://blogs.sap.com/2017/02/15/sap-s4hana-system-conversion-custom-code-adaptation-process/