3066001 - Query on Cost Center Key Mapping: Replicating Cost Centers from SAP ERP to Employee Central Using Boomi AtomSphere as the Middleware

You wish to understand the behavior of fields REMOTE_OBJECT_ID and REMOTE_EXTERNAL_OBJECT_ID during Cost Center Key Mapping, specifically in the replication package Replicating Cost Centers from SAP ERP to Employee Central Using Boomi AtomSphere as the Middleware

• An initial upload has been done in the system without any leading zeros for the cost centers
• You wish to understand whether, during mapping, the missing leading zeros will be added in the fields REMOTE_OBJECT_ID and REMOTE_EXTERNAL_OBJECT_ID in the resulting IDoc

Clarification of standard behavior

The mapping of the Boomi Cost Center Replication process follows a process whereby both fields from the IDoc (REMOTE_OBJECT_ID and REMOTE_EXTERNAL_OBJECT_ID) get mapped 1:1 to the EC fields externalCode and costcenterExternalObjectID without any modifications (please note, the default behavior on the ERP side is that the two mentioned fields in the IDoc message should always contain leading zeros)

Cf. the explanation from our Implementation Guide also:

7.1.2 Cost Center Key Mapping
Whenever there are multiple SAP ERP systems you need to make sure that the cost center IDs delivered to Employee Central are unique across your system landscape. The default ID delivered by SAP ERP is a concatenation of controlling area key (4 characters) and cost center key (not more than 10 characters). The controlling area key is required to make the ID unique (because different cost centers can have the same key if they belong to different controlling areas)

Replicating Cost Centers from SAP ERP to Employee Central Using Boomi AtomSphere as the Middleware

Boomi, Cost Center, mapping, Replicating Cost Centers from SAP ERP to Employee Central Using Boomi AtomSphere as the Middleware , KBA , LOD-SF-INT-BOM , Standard SF to 3rd Party Boomi Content , LOD-SF-INT-BPI , Dell & Boomi Infrastructure , LOD-SF-INT , Integrations , How To