Domain catalogue Supply chain on SAP S/4HANA

Product compliance attributes on SAP S/4HANA

Country of origin, substance declarations, certifications and restrictions per golden item, with evidence and validity, ready for customs, customers and regulators.

SOURCES, READ IN PLACESAP S/4HANAERPASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN PRODUCT COMPLIANCE ATTRIBUTESProduct compliance attributesone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
The objects the domain reads in place on SAP S/4HANA, the assembly steps, and who reads the result. Writes go through released BAPIs and IDocs.
3
objects read in place from SAP S/4HANA
catalogue
4
attribute groups assembled
catalogue
3 days
to production-grade
estimate
1
write path, acknowledged and logged
catalogue
0
rows copied to start
product
What the domain reads

The SAP S/4HANA objects behind the golden record

Tables are read in place through the SAP connector, using released read interfaces and change capture where the basis team allows it. The rows stay in SAP.

ObjectRead fromFields the domain usesFreshness
ClassificationAUSP · KSSK · CABNOBJEK · ATINN · ATWRTlive; change capture where enabled
Dangerous goods and substancesEHS tables (ESTRH · ESTVH)SUBID · RECNlive; change capture where enabled
Sales restrictionsTVLST · VBAK checksLSTELlive; change capture where enabled
The keys

How product compliance attributes records match, in this system's fields

item + attribute + supplierdeclaration id

The first object above carries the strong keys; the standardised attributes come from the same rows. Attributes carry their evidence and validity; a lapsed certificate changes a rule result, and the item's status, on the day it lapses.

What is written back

Through the interfaces SAP S/4HANA supports

Writes go through released BAPIs and IDocs. Each call returns a document number or an error message, and Lima records both beside the change.

InterfaceUsed forResult
BAPI_OBJCL_CHANGE (classification) · EHS APIsgolden values approved for write-back: origin; substances; certificationsthe id or error SAP S/4HANA returns, stored beside the change

Write-back is off per object until a test write succeeds, and approval rules can require a person per object. Reconciliation compares the source row with the golden value on a schedule.

Access and prerequisites

What is in place before the first build

SAP roles are mapped to Lima access policies once. A steward who sees purchasing organisation 1000 in SAP sees the same rows here.

Register the objects3 objects from the connector catalogue; each shows its rows at once.
Also on SAP ECC

The same domain on SAP ECC

ObjectOn SAP S/4HANAOn SAP ECC
ClassificationAUSP · KSSK · CABNsame tables
Dangerous goods and substancesEHS tables (ESTRH · ESTVH)same objects
Sales restrictionsTVLST · VBAK checkssame objects
Nearby

This domain on other systems, and other domains on SAP S/4HANA

Product compliance attributes on

Other domains on SAP S/4HANA

Terms on this page

Country of originWhere an item was produced or last substantially transformed.
DeclarationA supplier's or maker's statement about substances or conformity, with a version.
Read in placeThe rows stay in SAP S/4HANA; Lima sends the filter and the columns and SAP S/4HANA returns the matching rows.
Questions

Does this domain copy data out of SAP S/4HANA?

The golden record reads the objects above in place. History the pivot needs at scale is landed in your lake by the Backbone, under the same keys, security and audit.

What does the SAP S/4HANA team need to do?

Grant the read access and the write interfaces listed above and agree the refresh method. Nothing is installed in SAP S/4HANA.

Can we start with reads only?

Yes. Write-back stays off per object until a test write succeeds; the golden view, the API and the pivots work from day one on reads.

See your first domain built on your data

Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.