• loga201@reddot-nextgenlabs.com
  • Behringstraße 7, Berlin -12437, Germany
about-img

Preferred Architecture

The above approach is completely automated and preferred by most customers who use MDG to centrally maintain all their master data however this requires a certain level of custom implementations. Note: MDG is optional so employee business partners can be generated directly in the target systems.

about-img

Employee to BP Process

The above model follows VMODE = 2 approaches and is recommended by SAP. A central person is a unique object within S/4 HANA for every employee. HCM system should transfer both the employee master data and central person data to the connected systems. Once the idoc is processed, there will be central person-to-person relationships exist in the HRP1001 table. One employee may have more than one contract because of the country transfer or concurrent assignment, in such cases, there will be more than one pernr for the same central person. Daily job or the initial synchronization report generates one employee BP with role BUP003 and the employment BP for each contract with role BUP010. SAP provides the standard report to check the complete relationships with the central person. The relationship between the BP and the vendor/customer is stored in the tables CVI_CUST_LINK, and CVI_VEND_LINK. Generation of the employment BP’s is completely optional. Business users(info type 0105, subtype -0001) are connected to BP, and the relationship can be found in table USR21.