/
Objects’ keys mapping

Objects’ keys mapping

Owned by proaxia
Mar 21, 2025
2 min read

SAP backend system uses ‘normal’ objects’ identifiers. FSM uses GUIDs. These must match.

image-20250321-121257.png

 

Both Connector and FSM have their own mapping tables - /PACG/ECM_EOBREF and IdentifierMap (FSM IdentifierMap is internal table with no public access).

image-20250321-121319.png

 

Mapping is done a bit differently for objects sent to FSM and received from FSM.

  • For new object sent to FSM (new to FSM) the corresponding FSM Guid is returned as part of confirmation

  • For new objects received from FSM the logic is a bit more complex and depends on the objects.

  • Objects that are updated in FSM are transferred to the Connector containing both SAPKEY and FSM GUID

image-20250321-121340.png

 

These can be also found in corresponding IDOC:

image-20250321-121353.png

 

When an object is created in FSM, there is simply no SAPKEY. After object’s creation, SAPKEY must be delivered to FSM. For most of the objects, it is included in the GENERIC message

image-20250321-121408.png

 

But for some (due to historical reasons) addition message is sent – the OBJCONF

image-20250321-121422.png

 

Which is nothing but mapping between SAPKEY and FSM GUID

image-20250321-121437.png

Related content

If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed /wiki/spaces/PFCC/pages/1561427969. Learn about support possibilities here.