Manufacturing and quality on Oracle Fusion

Production schedule change on Oracle Fusion Cloud

Lets a planner move firmed production orders on a live schedule, shows the effect on components and customer dates, collects the signatures and writes the new dates to the ERP.

SCREENSDATA HANDLERSORACLE FUSION · READ IN PLACES01 Change requestS02 ScheduleS03 EffectsS04 Production checkS05 Sales updateS06 ApprovalS07 Boarddh_production_orderProduction orderManufacturing REST: workOrdersdh_planned_orderPlanned orderSupply Chain Planning REST:planningSupplies (planned orders)dh_sales_order_lineSales order lineOrder Management REST:salesOrdersForOrderHub · linesdh_stock_positionStock positionInventory REST: inventoryOnhandBalances· inventoryItemLotsdh_routingRoutingManufacturing REST: workDefinitions ·operationsWRITE BACK TO ORACLE FUSIONProduction order → PATCH workOrders · POST operationTransactionsPlanned order → PATCH planningSupplies (firm, release)Sales order line → POST/PATCH salesOrdersForOrderHubrows 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
7
screens on those rows
catalogue
7 days
to production-grade
estimate
3
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
Production orderManufacturing REST: workOrdersWorkOrderNumber (number) · ItemNumber (material) · PlannedStartQuantity (qty) · PlannedStartDate (start)live through the API
Planned orderSupply Chain Planning REST: planningSupplies (planned orders)OrderNumber (number) · Item (material) · Quantity (qty) · StartDate (start)live through the API
Sales order lineOrder Management REST: salesOrdersForOrderHub · linesOrderNumber (number) · LineNumber (line) · BuyingPartyNumber (customer) · ProductNumber (material)live through the API
Stock positionInventory REST: inventoryOnhandBalances · inventoryItemLotsItemNumber (material) · OrganizationCode (plant) · Subinventory (sloc) · OnhandQuantity (on hand)live through the API
RoutingManufacturing REST: workDefinitions · operationsWorkDefinitionName (group) · OperationSequenceNumber (operation) · WorkCenterName (work center) · SetupTime (resources) (setup)live through the API
The trigger

The start criterion in Oracle Fusion's own fields

In plain words: A planner or production lead starts a change on S01 for a work center and a window; a breakdown recorded on the floor screen starts one 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.

Start

A planner or production lead starts a change on S01 for a work center and a window; a breakdown recorded on the floor screen starts one as well. The instance then reads its rows from Oracle Fusion through the handlers above.

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
Production orderstart and finish dates changed through the production order interfacePATCH workOrders · POST operationTransactions
Planned orderfirmed planned orders rescheduledPATCH planningSupplies (firm, release)
Sales order lineconfirmed dates updated on the affected customer ordersPOST/PATCH salesOrdersForOrderHub
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
Production orderManufacturing REST: workOrdersWIP_DISCRETE_JOBS (write: WIP_JOB_SCHEDULE_INTERFACE)
Planned orderSupply Chain Planning REST: planningSupplies (planned orders)MRP_RECOMMENDATIONS · MRP_PLANNED_ORDERS
Sales order lineOrder Management REST: salesOrdersForOrderHub · linesOE_ORDER_HEADERS_ALL · OE_ORDER_LINES_ALL (write: OE_HEADERS_IFACE_ALL · OE_LINES_IFACE_ALL)
Stock positionInventory REST: inventoryOnhandBalances · inventoryItemLotsMTL_ONHAND_QUANTITIES_DETAIL (write: MTL_TRANSACTIONS_INTERFACE)
RoutingManufacturing REST: workDefinitions · operationsBOM_OPERATIONAL_ROUTINGS · BOM_OPERATION_SEQUENCES
Nearby

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

Production schedule change on

Other apps on Oracle Fusion

Terms on this page

Firmed orderA production or planned order the planning run leaves in place; a person changes its dates and quantity.
Work centerThe machine or line where an operation runs; the routing states its setup and run time.
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.