Supply chain and planning on Oracle Fusion

New product introduction readiness on Oracle Fusion Cloud

Tracks every part of a new product through the readiness gates each function owns, reading the material, BOM, routing, source, inspection and price records live until launch.

SCREENSDATA HANDLERSORACLE FUSION · READ IN PLACES01 Launch registerS02 Readiness boardS03 Part checklistS04 Supply gateS05 Quality gateS06 Launch sign-offS07 Trackerdh_material_masterMaterial masterProduct Hub REST: itemsV2dh_bill_of_materialsBill of materialsProduct Hub REST: itemStructures ·componentsdh_routingRoutingManufacturing REST: workDefinitions ·operationsdh_supplier_masterSupplier masterProcurement REST: suppliers ·supplierSitesdh_inspection_lotInspection lotQuality Management REST:inspectionResults · inspectionPlansdh_price_conditionPrice conditionPricing REST: priceLists ·priceListItemsWRITE BACK TO ORACLE FUSIONMaterial master → POST/PATCH itemsV2Bill of materials → POST/PATCH itemStructuresrows 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.
6
objects read in place from Oracle Fusion
catalogue
7
screens on those rows
catalogue
8 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
Material masterProduct Hub REST: itemsV2ItemNumber (id) · ItemDescription (desc) · ItemType (type) · OrganizationCode (plant)live through the API
Bill of materialsProduct Hub REST: itemStructures · componentsItemNumber (parent) · ComponentItemNumber (component) · Quantity (qty) · StartDate (valid from)live through the API
RoutingManufacturing REST: workDefinitions · operationsWorkDefinitionName (group) · OperationSequenceNumber (operation) · WorkCenterName (work center) · SetupTime (resources) (setup)live through the API
Supplier masterProcurement REST: suppliers · supplierSitesSupplierNumber (id) · Supplier (name) · Country (country) · Status (block)live through the API
Inspection lotQuality Management REST: inspectionResults · inspectionPlansInspectionNumber (lot) · Item (material) · InspectionType (origin) · Result (result)live through the API
Price conditionPricing REST: priceLists · priceListItemsItemNumber (material) · Customer (pricing strategy) (customer) · BasePrice (amount) · PricingUOM (unit)live through the API
The trigger

The start criterion in Oracle Fusion's own fields

In plain words: The launch lead registers a new product with its target launch date and part numbers on S01.

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

The launch lead registers a new product with its target launch date and part numbers on S01. 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
Material masterplant status set to active for the launch plant when the launch is signedPOST/PATCH itemsV2
Bill of materialsthe released structure's valid-from aligned to the launch datePOST/PATCH itemStructures
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 handlers6 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
Material masterProduct Hub REST: itemsV2MTL_SYSTEM_ITEMS_B (write: MTL_SYSTEM_ITEMS_INTERFACE)
Bill of materialsProduct Hub REST: itemStructures · componentsBOM_STRUCTURES_B · BOM_COMPONENTS_B (write: BOM_BILL_OF_MTLS_INTERFACE)
RoutingManufacturing REST: workDefinitions · operationsBOM_OPERATIONAL_ROUTINGS · BOM_OPERATION_SEQUENCES
Supplier masterProcurement REST: suppliers · supplierSitesAP_SUPPLIERS · AP_SUPPLIER_SITES_ALL (write: AP_SUPPLIERS_INT)
Inspection lotQuality Management REST: inspectionResults · inspectionPlansQA_RESULTS · QA_PLANS
Price conditionPricing REST: priceLists · priceListItemsQP_LIST_HEADERS_B · QP_LIST_LINES
Nearby

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

New product introduction readiness on

Other apps on Oracle Fusion

Terms on this page

Plant viewThe part of a material record that holds planning, purchasing and storage settings for one plant.
Usage decisionThe quality verdict recorded on an inspection lot: accepted, rejected or accepted with conditions.
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.