SAP Knowledge Base Article - Preview

3728665 - /SHCM/BUPA_SYNC_S does not take customer-specific name or additional data changes into account during HR → Business Partner synchronization

Symptom

When an employee is replicated (e.g. from SAP SuccessFactors Employee Central or SAP HCM) the automatic HR-BP synchronization delivers the expected values—for example a customer-specific full name format or an additional comment/description (such as an internal tag).

However, if the same employee has to be (re-)processed with the report /SHCM/BUPA_SYNC_S (or by the BP delta sync job that calls the same framework), the Business Partner (BP) is created/updated but the customer-specific adjustments are lost or overwritten by the standard mapping. Typical effects are:

• The BP full name is created with the SAP standard logic instead of the customer-defined format.
• Custom fields or comments (for example a descriptive tag in BP roles, addresses or identification data) are missing after the report is executed.


Read more...

Environment

• SAP S/4HANA on-premise edition
• SAP S/4HANA private cloud edition

Product

SAP S/4HANA 2021

Keywords

/SHCM/BUPA_SYNC_S, HR-BP synchronization, Business Partner, employee BP, BADI_FITV_VENDOR_SYNC, /SHCM/B_EE_BP_SYNC, MODIFY_COMPLETE_DATA, MODIFY_ALL, custom mapping, full name, description field, comment, TESORERIA, employee replication, EC to S/4, BP overwrite, PA infotype exit , KBA , CA-HR-S4-OP-BP , HCM Business Partner Integration , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.