7/4/2023 0 Comments Iemployee iclockThis BAdI implementation identifies employee vendors (LFB1-PERNR has an entry) and enables the synchronization of those vendors to BPs of category “Person” while executing the CVI synchronization report MDS_LOAD_COCKPIT. To accomplish this, implement SAP Note 2539457 (CVI & employee vendors in incorrect BP category) and ensure that BAdI implementation HCM_CVI_MAP_BP_CATEGORY (BAdI CVI_MAP_TITLE) is active. I will explain both in this blog.įirst of all, if employee vendors exist in the SAP ERP system, the employee vendors will have to be converted to BPs of category “Person” during CVI synchronization. There are two parts to this, one is to synchronize the employee vendors to BP in the SAP ERP System before system conversion and the second one is to synchronize the employee records to BP in S/4HANA after system conversion. If an existing SAP ERP customer who is using SAP ERP HCM is planning to convert their ERP system to S/4HANA, they are required to synchronize their employee data as well to Business Partner once they are in S/4HANA. You may refer to my blog BP and CVI in SAP S/4HANA System Conversion for a step by step guide for CVI Implementation and Synchronization. ![]() Implementing Customer Vendor Integration (CVI) and synchronizing customer and vendor data with Business Partner (BP) in the SAP ERP system is a prerequisite for system conversion to S/4HANA. This is one of the major changes in S/4HANA, and therefore, it requires considerable effort to prepare the SAP ERP system for conversion to S/4HANA. In SAP S/4HANA, Business Partner (BP) is the leading object, and customer and vendor master data will be assigned as roles to Business Partner. If HCM is running inside of S/4HANA on-premise, then the integration is automatically provided as part of the Compatibility Mode. The integration between SAP ERP HCM and S/4HANA on-premise will be available via ALE if HCM is running on a separate instance. Those customers can run their HCM in either a separate instance or a single instance with S/4HANA. ![]() However, some SAP ERP customers who are converting to SAP S/4HANA on-premise may not be able to move their existing SAP ERP HCM to SAP SuccessFactors in the near future and would like to continue to use SAP ERP HCM until they are ready to move to SAP SuccessFactors. SAP SuccessFactors, the next generation HCM suite in the public cloud, is the go-forward HCM solution for both cloud and on-premise editions of SAP S/4HANA. Updated on – Relevant to SAP S/4HANA 2020 and higher
0 Comments
Leave a Reply. |