Takes a deviation reported on the floor through containment, root cause, corrective action and an effectiveness check, with the notification, blocked stock and batch status kept 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 | IssueNumber (number) · IssueType (type) · Item (material) · Supplier (vendor) | live through the API |
| Inspection lot | Quality Management REST: inspectionResults · inspectionPlans | InspectionNumber (lot) · Item (material) · InspectionType (origin) · Result (result) | live through the API |
| Batch | Inventory REST: inventoryItemLots | LotNumber (batch) · ItemNumber (material) · ExpirationDate (expiry) · OriginationDate (produced) | live through the API |
| Stock position | Inventory REST: inventoryOnhandBalances · inventoryItemLots | ItemNumber (material) · OrganizationCode (plant) · Subinventory (sloc) · OnhandQuantity (on hand) | live through the API |
| Production order | Manufacturing REST: workOrders | WorkOrderNumber (number) · ItemNumber (material) · PlannedStartQuantity (qty) · PlannedStartDate (start) | live through the API |
In plain words: An operator or inspector submits a deviation on the mobile screen S01; a quality notification of the internal defect type created directly in the ERP opens a case as well.
This app starts from a screen, so the first read happens when the instance opens; the criteria on the arrows use the fields above.
An operator or inspector submits a deviation on the mobile screen S01; a quality notification of the internal defect type created directly in the ERP opens a case as well. The instance then reads its rows from Oracle Fusion through the handlers above.
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 | notification created from the mobile screen with defect code, tasks and status; set to complete at closure | POST qualityIssues · POST qualityActions |
| Stock position | affected quantity moved to blocked stock and back with a goods movement | POST inventoryTransactions (transfer, scrap, status) |
| Batch | batch status set to restricted during containment and released after the decision | PATCH inventoryItemLots |
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) |
| Inspection lot | Quality Management REST: inspectionResults · inspectionPlans | QA_RESULTS · QA_PLANS |
| Batch | Inventory REST: inventoryItemLots | MTL_LOT_NUMBERS |
| Stock position | Inventory REST: inventoryOnhandBalances · inventoryItemLots | MTL_ONHAND_QUANTITIES_DETAIL (write: MTL_TRANSACTIONS_INTERFACE) |
| Production order | Manufacturing REST: workOrders | WIP_DISCRETE_JOBS (write: WIP_JOB_SCHEDULE_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.
