Domain catalogue Reference data on Oracle Fusion Cloud

Countries, regions and code lists on Oracle Fusion Cloud

The code lists every system needs, kept once: countries and regions, Incoterms, payment terms, languages, and the crosswalk to each system's local codes.

SOURCES, READ IN PLACEOracle Fusion CloudERPASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN COUNTRIES, REGIONS AND CODE LISTSCountries, regions and code listsone 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 Oracle Fusion Cloud, the assembly steps, and who reads the result. Writes go through Fusion REST resources and import management.
3
objects read in place from Oracle Fusion Cloud
catalogue
4
attribute groups assembled
catalogue
1 days
to production-grade
estimate
1
write path, acknowledged and logged
catalogue
0
rows copied to start
product
What the domain reads

The Oracle Fusion Cloud objects behind the golden record

Objects are read through Oracle Fusion's REST resources and, for volume, through BI Cloud Connector extracts landed in your lake; the rows stay in Oracle.

ObjectRead fromFields the domain usesFreshness
Territories and geographiesFND_TERRITORIES · HZ_GEOGRAPHIES (REST: geographies)TERRITORY_CODE · GEOGRAPHY_NAME · GEOGRAPHY_TYPElive through REST; extracts refreshed on schedule
LookupsFND_LOOKUP_VALUES (REST: standardLookups)LOOKUP_TYPE · LOOKUP_CODE · MEANINGlive through REST; extracts refreshed on schedule
Payment termsRA_TERMS · AP_TERMS (REST: paymentTerms)NAME · DUE_DAYSlive through REST; extracts refreshed on schedule
The keys

How countries, regions and code lists records match, in this system's fields

list + codestandard code (ISO)

The first object above carries the strong keys; the standardised attributes come from the same rows. A code list is a small master-data domain with the same history, rules and security as the big ones.

What is written back

Through the interfaces Oracle Fusion Cloud supports

Writes go through Fusion REST resources or import management. Each call returns the record id or an error, and Lima records both beside the change.

InterfaceUsed forResult
REST standardLookups · paymentTerms · geographies importgolden values approved for write-back: code list; codes; crosswalksthe id or error Oracle Fusion Cloud 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

Fusion roles and data-security policies are mapped to Lima access policies once; a person sees the same organisations here as in Fusion.

Register the objects3 objects from the connector catalogue; each shows its rows at once.
Also on Oracle E-Business Suite

The same domain on Oracle E-Business Suite

ObjectOn Oracle Fusion CloudOn Oracle E-Business Suite
Territories and geographiesFND_TERRITORIES · HZ_GEOGRAPHIES (REST: geographies)FND_LOOKUP_VALUES / FND_TERRITORIES
LookupsFND_LOOKUP_VALUES (REST: standardLookups)same objects
Payment termsRA_TERMS · AP_TERMS (REST: paymentTerms)same objects
Nearby

This domain on other systems, and other domains on Oracle Fusion Cloud

Countries, regions and code lists on

Other domains on Oracle Fusion Cloud

Terms on this page

Code listA finite set of allowed values with names and validity.
CrosswalkThe mapping from a golden code to each system's local code.
Read in placeThe rows stay in Oracle Fusion Cloud; Lima sends the filter and the columns and Oracle Fusion Cloud returns the matching rows.
Questions

Does this domain copy data out of Oracle Fusion Cloud?

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 Oracle Fusion Cloud team need to do?

Grant the read access and the write interfaces listed above and agree the refresh method. Nothing is installed in Oracle Fusion Cloud.

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.