Opens a case 90 days before a purchasing contract expires, shows consumption against target value, and carries the renew, renegotiate or lapse decision through legal and the category lead.
Objects are read in place through the released REST resources, and bulk history through BI Cloud Connector extracts. The rows stay in Oracle.
| Object | Read from | Fields the app uses | Freshness |
|---|---|---|---|
| Purchasing contract | Procurement REST: purchaseAgreements · Enterprise Contracts REST: contracts | EndDate (valid to) · AgreementNumber (number) · Supplier (vendor) · AgreementAmount (target value) | live through the API |
| Purchase order line | Procurement REST: purchaseOrders · lines · schedules | OrderNumber (number) · LineNumber (line) · Supplier (vendor) · Item (material) | live through the API |
| Supplier master | Procurement REST: suppliers · supplierSites | SupplierNumber (id) · Supplier (name) · Country (country) · Status (block) | live through the API |
| Supplier invoice | Payables REST: invoices | InvoiceNumber (number) · Supplier (vendor) · InvoiceAmount (amount) · PurchaseOrderNumber (lines) (po) | live through the API |
In plain words: A purchasing contract whose validity ends within the next 90 days.
The criterion runs in Oracle Fusion through the data handler, so only the matching rows return. The editor shows the rows it selects, and their count, as it is written.
# start criterion in Oracle Fusion fields EndDate <= today + 90 and EndDate >= today # the same criterion in canonical fields {contract.valid_to} <= today + 90 and {contract.valid_to} >= today
Writes use the same released REST resources (POST and PATCH) with the integration user's data-security profile. Each call returns the document identifier or an error message, and the app records both beside the decision.
| Object | What changes | Interface |
|---|---|---|
| Purchasing contract | validity and target value extended, or a new contract created with the agreed prices; a lapse recorded with the reason | PATCH purchaseAgreements · POST contracts |
| Purchase order line | open order lines dated beyond expiry moved to the new contract or closed | PATCH purchaseOrders (change order) · POST purchaseOrders |
Each write stores the identifier Oracle Fusion returns beside the decision, the person and the time, so the log answers who changed what, and the reconciliation shows it arrived.
Oracle roles and data-security policies are mapped to Lima access policies once. A buyer scoped to a business unit in Oracle sees the same rows in the app.
On Oracle E-Business Suite the same objects live in the tables named beside each row and are read in place through JDBC with a read-only user; writes go through the open interface tables and public APIs, run by a concurrent program.
| Object | On Oracle Fusion | On Oracle E-Business Suite |
|---|---|---|
| Purchasing contract | Procurement REST: purchaseAgreements · Enterprise Contracts REST: contracts | PO_HEADERS_ALL (blanket) · OKC_K_HEADERS_ALL |
| Purchase order line | Procurement REST: purchaseOrders · lines · schedules | PO_HEADERS_ALL · PO_LINES_ALL · PO_LINE_LOCATIONS_ALL (write: PO_CHANGE_API1_S) |
| Supplier master | Procurement REST: suppliers · supplierSites | AP_SUPPLIERS · AP_SUPPLIER_SITES_ALL (write: AP_SUPPLIERS_INT) |
| Supplier invoice | Payables REST: invoices | AP_INVOICES_ALL · AP_HOLDS_ALL (write: AP_INVOICES_INTERFACE) |
The screens read through handlers that leave the rows in Oracle Fusion. History the app needs at scale is landed in the lake by the Backbone, which is the exception by design.
The prerequisites above: an integration identity with read rights on the objects listed and write rights on the interfaces named, connectivity, and the scopes agreed with the process owner.
Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, listed above.
Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.
