Domain catalogue Parties on Oracle Fusion Cloud

Business contact on Oracle Fusion Cloud

One record per person at a customer, supplier or partner, linked to the organisation they work for and the roles they hold.

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 BUSINESS CONTACTBusiness contactone 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.
2
objects read in place from Oracle Fusion Cloud
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 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
ContactHZ_PARTIES (PERSON) · HZ_RELATIONSHIPS (REST: contacts)PARTY_ID · PERSON_FIRST_NAME · EMAIL_ADDRESS · JOB_TITLElive through REST; extracts refreshed on schedule
Contact pointsHZ_CONTACT_POINTSPHONE_NUMBER · EMAIL_ADDRESSlive through REST; extracts refreshed on schedule
The keys

How business contact records match, in this system's fields

e-mail addressphone (standardised)name and employer (fuzzy)portal user id

The first object above carries the strong keys; the standardised attributes come from the same rows. A shared mailbox address is a weak key; the rules treat info@ and orders@ as organisation attributes, so two people stay apart on it.

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 crmRestApi/resources/latest/contacts · findDuplicatesgolden values approved for write-back: identity; employer and role; consent and preferencesthe 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 objects2 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
ContactHZ_PARTIES (PERSON) · HZ_RELATIONSHIPS (REST: contacts)HZ_PARTIES person parties
Contact pointsHZ_CONTACT_POINTSsame objects
Nearby

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

Business contact on

Other domains on Oracle Fusion Cloud

Terms on this page

Partner functionSAP's name for the role a person or organisation plays on a document.
ConsentThe recorded permission to contact a person on a channel, with its date and source.
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.