Turns a quality notification against a supplier into an 8D case the supplier works on a portal screen, with blocked stock, return delivery and closure recorded in the ERP.
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 |
|---|---|---|---|
| Quality notification | Quality Management REST: qualityIssues · qualityActions | IssueType (type) · Supplier (vendor) · IssueNumber (number) · Item (material) | live through the API |
| Supplier master | Procurement REST: suppliers · supplierSites | SupplierNumber (id) · Supplier (name) · Country (country) · Status (block) | live through the API |
| Inspection lot | Quality Management REST: inspectionResults · inspectionPlans | InspectionNumber (lot) · Item (material) · InspectionType (origin) · Result (result) | live through the API |
| Goods receipt | Receiving REST: receivingReceiptTransactions | ReceiptNumber (document) · DocumentNumber (po) · ItemNumber (material) · Quantity (qty) | live through the API |
| Stock position | Inventory REST: inventoryOnhandBalances · inventoryItemLots | ItemNumber (material) · OrganizationCode (plant) · Subinventory (sloc) · OnhandQuantity (on hand) | live through the API |
| Purchase order line | Procurement REST: purchaseOrders · lines · schedules | OrderNumber (number) · LineNumber (line) · Supplier (vendor) · Item (material) | live through the API |
In plain words: A quality notification of the supplier type created in the ERP, from a rejected inspection lot at goods receipt or from the floor.
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 IssueType = supplier and Supplier is present # the same criterion in canonical fields {qn.type} = supplier and {qn.vendor} is present
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 | 8D disciplines recorded as tasks with status and dates; notification set to complete at D8 | POST qualityIssues · POST qualityActions |
| Stock position | affected quantity moved to blocked stock and returned to the supplier with a return delivery | POST inventoryTransactions (transfer, scrap, status) |
| Purchase order line | replacement quantity added to the order line | 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 |
|---|---|---|
| Quality notification | Quality Management REST: qualityIssues · qualityActions | QA_RESULTS (collection plans) |
| Supplier master | Procurement REST: suppliers · supplierSites | AP_SUPPLIERS · AP_SUPPLIER_SITES_ALL (write: AP_SUPPLIERS_INT) |
| Inspection lot | Quality Management REST: inspectionResults · inspectionPlans | QA_RESULTS · QA_PLANS |
| Goods receipt | Receiving REST: receivingReceiptTransactions | RCV_SHIPMENT_HEADERS · RCV_TRANSACTIONS (write: RCV_TRANSACTIONS_INTERFACE) |
| Stock position | Inventory REST: inventoryOnhandBalances · inventoryItemLots | MTL_ONHAND_QUANTITIES_DETAIL (write: MTL_TRANSACTIONS_INTERFACE) |
| Purchase order line | Procurement REST: purchaseOrders · lines · schedules | PO_HEADERS_ALL · PO_LINES_ALL · PO_LINE_LOCATIONS_ALL (write: PO_CHANGE_API1_S) |
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.