Manufacturing and quality on Oracle Fusion

Batch release on Oracle Fusion Cloud

Takes a produced batch from complete inspection results through QA review to a usage decision, sets the batch status in the ERP and produces the certificate of analysis.

SCREENSDATA HANDLERSORACLE FUSION · READ IN PLACES01 Batches awaiting releaseS02 Batch record reviewS03 DeviationsS04 Usage decisionS05 CertificateS06 Boarddh_batchBatchInventory REST: inventoryItemLotsdh_inspection_lotInspection lotQuality Management REST:inspectionResults · inspectionPlansdh_production_orderProduction orderManufacturing REST: workOrdersdh_quality_notificationQuality notificationQuality Management REST: qualityIssues ·qualityActionsdh_stock_positionStock positionInventory REST: inventoryOnhandBalances· inventoryItemLotsWRITE BACK TO ORACLE FUSIONInspection lot → POST inspectionResultsBatch → PATCH inventoryItemLotsrows stay in Oracle Fusion · access rules applied at read time · each write acknowledged and logged
The screens of the app, the data handler behind each, and the Oracle Fusion object it reads in place. Writes below the line go through released interfaces with an acknowledgement.
5
objects read in place from Oracle Fusion
catalogue
6
screens on those rows
catalogue
6 days
to production-grade
estimate
2
objects written back
catalogue
0
rows copied to build it
product
What the app reads

The Oracle Fusion objects behind each handler

Objects are read in place through the released REST resources, and bulk history through BI Cloud Connector extracts. The rows stay in Oracle.

ObjectRead fromFields the app usesFreshness
BatchInventory REST: inventoryItemLotsLotNumber (batch) · ItemNumber (material) · ExpirationDate (expiry) · OriginationDate (produced)live through the API
Inspection lotQuality Management REST: inspectionResults · inspectionPlansResult (result) · Disposition (decision) · InspectionType (origin) · InspectionNumber (lot)live through the API
Production orderManufacturing REST: workOrdersWorkOrderNumber (number) · ItemNumber (material) · PlannedStartQuantity (qty) · PlannedStartDate (start)live through the API
Quality notificationQuality Management REST: qualityIssues · qualityActionsIssueNumber (number) · IssueType (type) · Item (material) · Supplier (vendor)live through the API
Stock positionInventory REST: inventoryOnhandBalances · inventoryItemLotsItemNumber (material) · OrganizationCode (plant) · Subinventory (sloc) · OnhandQuantity (on hand)live through the API
The trigger

The start criterion in Oracle Fusion's own fields

In plain words: An inspection lot from production (origin 04) whose results are recorded for every characteristic and whose usage decision is still open.

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
InspectionType = '04' and Result = 'recorded' and Disposition = ''

# the same criterion in canonical fields
{lot.origin} = '04' and {lot.result} = 'recorded' and {lot.decision} = ''
What the app writes back

Through released interfaces

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.

ObjectWhat changesInterface
Inspection lotusage decision posted as accept or reject through the inspection lot interface, with the stock posting from quality inspection to unrestricted, blocked or scrapPOST inspectionResults
Batchbatch status set to released or blocked; certificate of analysis attached to the batchPATCH inventoryItemLots
Acknowledged and logged

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.

Access and prerequisites

What is in place before the first build

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.

  • An integration user with the REST resource roles for the objects the app reads and writes
  • BI Cloud Connector offerings enabled for the objects that need history at scale
  • Allowed IP or private connectivity to the pod
  • Business-unit and inventory-organisation scopes agreed with the process owner
Register the handlers5 objects from the catalog; each shows its rows at once.
Also on Oracle E-Business Suite

The same app on Oracle E-Business Suite

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.

ObjectOn Oracle FusionOn Oracle E-Business Suite
BatchInventory REST: inventoryItemLotsMTL_LOT_NUMBERS
Inspection lotQuality Management REST: inspectionResults · inspectionPlansQA_RESULTS · QA_PLANS
Production orderManufacturing REST: workOrdersWIP_DISCRETE_JOBS (write: WIP_JOB_SCHEDULE_INTERFACE)
Quality notificationQuality Management REST: qualityIssues · qualityActionsQA_RESULTS (collection plans)
Stock positionInventory REST: inventoryOnhandBalances · inventoryItemLotsMTL_ONHAND_QUANTITIES_DETAIL (write: MTL_TRANSACTIONS_INTERFACE)
Nearby

This app on other systems, and other apps on Oracle Fusion

Batch release on

Other apps on Oracle Fusion

Terms on this page

Usage decisionThe decision recorded on an inspection lot that accepts or rejects the inspected quantity and posts its stock accordingly.
Quality inspection stockStock that waits for a usage decision; it becomes available for delivery once posted to unrestricted.
Read in placeThe rows stay in Oracle Fusion; the handler sends the filter and the columns and Oracle Fusion returns the matching rows.
Questions

Does this app copy data out of Oracle Fusion?

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.

What does Oracle Fusion need to allow?

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.

Can I run it on Oracle E-Business Suite as well?

Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, listed above.

See this app on your data

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.