Collects each function's view of a new material on its own screen, checks duplicates and completeness, and creates the record in the ERP when every view is released.
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 | ItemNumber (id) · ItemDescription (desc) · ItemType (type) · OrganizationCode (plant) | live through the API |
| Bill of materials | Product Hub REST: itemStructures · components | ItemNumber (parent) · ComponentItemNumber (component) · Quantity (qty) · StartDate (valid from) | live through the API |
| Supplier master | Procurement REST: suppliers · supplierSites | SupplierNumber (id) · Supplier (name) · Country (country) · Status (block) | live through the API |
| Price condition | Pricing REST: priceLists · priceListItems | ItemNumber (material) · Customer (pricing strategy) (customer) · BasePrice (amount) · PricingUOM (unit) | live through the API |
In plain words: A requester submits 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.
A requester submits S01. 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 |
|---|---|---|
| Material master | material master created with basic, plant, purchasing, sales and accounting views through the material interface; status set to active when every view is complete | POST/PATCH itemsV2 |
| Price condition | initial sales price condition created for a sold material with its validity | PATCH priceListItems |
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) |
| Bill of materials | Product Hub REST: itemStructures · components | BOM_STRUCTURES_B · BOM_COMPONENTS_B (write: BOM_BILL_OF_MTLS_INTERFACE) |
| Supplier master | Procurement REST: suppliers · supplierSites | AP_SUPPLIERS · AP_SUPPLIER_SITES_ALL (write: AP_SUPPLIERS_INT) |
| Price condition | Pricing REST: priceLists · priceListItems | QP_LIST_HEADERS_B · QP_LIST_LINES |
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.
