Countries and regions, currencies, units, Incoterms, payment terms, tax codes, languages, industry codes: the small lists that every system needs and every system spells differently.
Units, dimensions, global and item conversions, cycle consistency.
Read the page →Codes, decimals, rate types and the rate series every system converts with.
Read the page →ISO countries and regions, Incoterms, payment terms, languages and their crosswalks.
Read the page →Factory, fiscal and planning calendars as dimensions every plan and report agrees on.
Read the page →Tax codes, commodity codes and product classification are reference-heavy domains with their own pages.
| Rule | Level | Example |
|---|---|---|
| ISO code matches the standard | column | a country code has two letters and exists in ISO 3166-1 |
| Validity is consistent | column | valid-to is after valid-from |
| A retired code names its replacement | row | payment term N45 retired → N45-2026 |
| Every code has a default-language name | row | an Incoterm with an English name |
| Bound fields hold only active codes as of the row's date | business | an order dated after the retirement uses the replacement |
| Each local code maps to exactly one golden code | business | CTRY 049 in the legacy system maps to DE |
It is the same platform: a list is a small domain with the same versions, rules, security and audit trail.
Lima raises the customising request with the values and records the transport id beside the change; the SAP basis team keeps control of transports.
Yes: ISO, UN/CEFACT and industry lists are loaded as versions with their publication dates, and your own lists sit beside them.
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.
