Runs quality rules on live master data, routes each failing record to its steward with the fix options, and writes the correction back to 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 |
|---|---|---|---|
| Material master | Product Hub REST: itemsV2 | ItemStatusValue (status) · PostprocessingLeadTime (lead time) · ItemNumber (id) · ItemDescription (desc) | live through the API |
| Supplier master | Procurement REST: suppliers · supplierSites | PaymentTerms (terms) · SupplierNumber (id) · Supplier (name) · Country (country) | live through the API |
| Customer master | Receivables REST: receivablesCustomerAccounts · TCA parties | BusinessUnit (sales org) · AccountNumber (id) · PartyName (name) · Country (country) | 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 record that fails one of the active quality rules, such as an active material with a lead time of 0, a supplier with empty payment terms, or a customer with an empty sales organisation.
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 (ItemStatusValue = 'active' and PostprocessingLeadTime = 0) or PaymentTerms = '' or BusinessUnit = '' # the same criterion in canonical fields ({material.status} = 'active' and {material.lead_time} = 0) or {vendor.terms} = '' or {customer.sales_org} = ''
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 |
|---|---|---|
| Material master | field corrected through the material interface; exception flag recorded beside the record | POST/PATCH itemsV2 |
| Supplier master | payment terms, country or purchasing data corrected; duplicate flagged for deletion | POST suppliers · PATCH supplierSites |
| Customer master | sales organisation data completed or corrected | POST/PATCH receivablesCustomerAccounts |
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 |
|---|---|---|
| Material master | Product Hub REST: itemsV2 | MTL_SYSTEM_ITEMS_B (write: MTL_SYSTEM_ITEMS_INTERFACE) |
| Supplier master | Procurement REST: suppliers · supplierSites | AP_SUPPLIERS · AP_SUPPLIER_SITES_ALL (write: AP_SUPPLIERS_INT) |
| Customer master | Receivables REST: receivablesCustomerAccounts · TCA parties | HZ_PARTIES · HZ_CUST_ACCOUNTS (write: RA_CUSTOMERS_INTERFACE_ALL) |
| 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.
