Scores every supplier each month from receipts, quality notifications and invoices, and opens a corrective action with the supplier when the score falls below the threshold.
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 |
|---|---|---|---|
| Supplier master | Procurement REST: suppliers · supplierSites | SupplierNumber (id) · Supplier (name) · Country (country) · Status (block) | live through the API |
| Purchase order line | Procurement REST: purchaseOrders · lines · schedules | Ordered (value) · RequestedDeliveryDate (delivery date) · OrderNumber (number) · LineNumber (line) | live through the API |
| Goods receipt | Receiving REST: receivingReceiptTransactions | TransactionDate (date) · ReceiptNumber (document) · DocumentNumber (po) · ItemNumber (material) | live through the API |
| Quality notification | Quality Management REST: qualityIssues · qualityActions | IssueNumber (number) · IssueType (type) · Item (material) · Supplier (vendor) | live through the API |
| Supplier invoice | Payables REST: invoices | InvoiceAmount (amount) · InvoiceNumber (number) · Supplier (vendor) · PurchaseOrderNumber (lines) (po) | live through the API |
In plain words: On the first working day of each month, a supplier with at least 5 receipts in the last 3 months whose score from on-time delivery, quality and price is below 70.
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 score(TransactionDate against RequestedDeliveryDate, IssueNumber per 100 receipts, InvoiceAmount against Ordered) < 70 over the last 3 months # the same criterion in canonical fields score({gr.date} against {po.delivery_date}, {qn.number} per 100 receipts, {invoice.amount} against {po.value}) < 70 over the last 3 months
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 |
|---|---|---|
| Quality notification | a corrective action notification created with the supplier's actions as tasks with owners and due dates | POST qualityIssues · POST qualityActions |
| Supplier master | purchasing block set when the category lead places the supplier on hold | POST suppliers · PATCH supplierSites |
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 |
|---|---|---|
| Supplier master | Procurement REST: suppliers · supplierSites | AP_SUPPLIERS · AP_SUPPLIER_SITES_ALL (write: AP_SUPPLIERS_INT) |
| Purchase order line | Procurement REST: purchaseOrders · lines · schedules | PO_HEADERS_ALL · PO_LINES_ALL · PO_LINE_LOCATIONS_ALL (write: PO_CHANGE_API1_S) |
| Goods receipt | Receiving REST: receivingReceiptTransactions | RCV_SHIPMENT_HEADERS · RCV_TRANSACTIONS (write: RCV_TRANSACTIONS_INTERFACE) |
| Quality notification | Quality Management REST: qualityIssues · qualityActions | QA_RESULTS (collection plans) |
| 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.
