Purchase and sales agreements as master data: parties, items, prices, validity and limits, linked to the orders released against them.
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.
| Object | Read from | Fields the domain uses | Freshness |
|---|---|---|---|
| Purchase agreements | PO_HEADERS_ALL (DOCUMENT_TYPE = BLANKET / CONTRACT) (REST: purchaseAgreements) | PO_HEADER_ID · AGREEMENT_NUMBER · AMOUNT_LIMIT · START_DATE · END_DATE | live through REST; extracts refreshed on schedule |
| Releases | PO_HEADERS_ALL (referencing agreement) · PO_LINES_ALL | AGREEMENT_HEADER_ID · AMOUNT | live through REST; extracts refreshed on schedule |
| Enterprise contracts | OKC_K_HEADERS_ALL_B (REST: contracts) | CONTRACT_NUMBER · STS_CODE | live through REST; extracts refreshed on schedule |
The first object above carries the strong keys; the standardised attributes come from the same rows. Release orders are transactions in the bed, so remaining value is a live measure on the agreement record.
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.
| Interface | Used for | Result |
|---|---|---|
REST purchaseAgreements · contracts | golden values approved for write-back: agreement; items; limits | the 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.
Fusion roles and data-security policies are mapped to Lima access policies once; a person sees the same organisations here as in Fusion.
| Object | On Oracle Fusion Cloud | On Oracle E-Business Suite |
|---|---|---|
| Purchase agreements | PO_HEADERS_ALL (DOCUMENT_TYPE = BLANKET / CONTRACT) (REST: purchaseAgreements) | PO_HEADERS_ALL blanket agreements; OKC in EBS |
| Releases | PO_HEADERS_ALL (referencing agreement) · PO_LINES_ALL | same objects |
| Enterprise contracts | OKC_K_HEADERS_ALL_B (REST: contracts) | same objects |
Contracts and agreements on
Other domains on 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.
Grant the read access and the write interfaces listed above and agree the refresh method. Nothing is installed in Oracle Fusion Cloud.
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.
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.
