Symptom
The standard BADI data replication programs have changed in S/4 after recent upgrade from ECC 6.0 to S/4HANA On-Premise system. All the C4C configurations are not available and have all being deleted. There is no MDT config data available post S/4 upgrade, no config data available for FOP nor Object Hierarchy.
Environment
- SAP Cloud for Customer
- SAP S/4HANA
- ECC 6.0
Cause
After the upgrade from ECC 6.0 to S/4HANA system, the customizing configurations have to be manually upgraded in S/4 system. This happens because the tables are different in ECC and S/4. ECC developments come under Add-On CODERINT, whereas S4H developments come under IS-UT. As an example:
- S4H Packages: ISU_C4C_INT, ISU_C4C_PROXY
- ECC Package: COD_BYD_ERP_UTILITIES
Resolution
Since the underlying tables for these configurations differ between the ECC and S4 systems, they need to be maintained again. The objects in the ECC system and in the S/4HANA system belong to different packages and often have different application components and names. Therefore, the configurations in the ECC cannot be directly transferred to the S/4HANA tables and must be manually completed.
Keywords
Cloud for Customer; C4C; ECC; S/4 HANA; Utilities; upgrade; BADI; ISU_C4C_INT; ISU_C4C_PROXY; COD_BYD_ERP_UTILITIES; MDT. , KBA , LOD-CRM-IND-UTL , Utilities , How To