Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table
Value Mapping, ID Mapping and Fixed Values in SAP Cloud Integration

Course quiz

Value Mapping, ID Mapping and Fixed Values in SAP Cloud Integration

Keep this: job aid

Code translation cheat sheet

  • Pick the home: S/4HANA master data → lookup; per partner → Partner Directory; shared or business-changed → Value Mapping; few fixed values in one mapping → FixValues; never hard-code.
  • Agency = who issues the code; identifier = which list. Fix the naming convention before the first table.
  • Create: package edit → Artifacts → Add → Value Mapping; add bi-directional mapping, then values; Save as version; Deploy.
  • Ambiguous reverse lookups: set the Default Values tab.
  • Mapping: Value Mapping function (Conversions) with exact agency/identifier strings; decide key, default or exception for not found.
  • Groovy: ITApiFactory.getService(ValueMappingApi.class, null).getMappedValue(srcAgency, srcId, value, tgtAgency, tgtId).
  • Import: Integration Directory (PO 7.5 SP22+, service plan) or CSV (comma, Agency|Identifier, UTF-8).
  • Configure per tenant; configured artifacts can't be edited, only re-configured.
  • ID Mapping step: source ID + context → stable GUID in a header; default expiry 30 days; context starts with a letter.
  • Test every entry both ways, an unknown and an empty value; assert translated values; compare deployed content across tenants.