Runs the monthly sales and operations planning cycle as one app: demand review, supply review, reconciliation and the executive meeting, on the live plan.
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 |
|---|---|---|---|
| Forecast | Demand Management: forecast measures (REST / planning data extract) | Item (material) · Organization (plant) · TimeBucket (period) · ForecastQuantity (qty) | live through the API |
| Planned order | Supply Chain Planning REST: planningSupplies (planned orders) | OrderNumber (number) · Item (material) · Quantity (qty) · StartDate (start) | live through the API |
| Stock position | Inventory REST: inventoryOnhandBalances · inventoryItemLots | ItemNumber (material) · OrganizationCode (plant) · Subinventory (sloc) · OnhandQuantity (on hand) | live through the API |
| Sales order line | Order Management REST: salesOrdersForOrderHub · lines | OrderNumber (number) · LineNumber (line) · BuyingPartyNumber (customer) · ProductNumber (material) | live through the API |
| Budget line | Budgetary Control REST: controlBudgetBalances · EPM plans | ControlBudgetName (object) · BudgetAmount (amount) · PeriodName (year) · BudgetVersion (version) | live through the API |
In plain words: The cycle starts on the first working day of each month, or when the demand director starts it early.
This app starts from a screen, so the first read happens when the instance opens; the criteria on the arrows use the fields above.
The cycle starts on the first working day of each month, or when the demand director starts it early. 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 |
|---|---|---|
| Forecast | agreed forecast version written to the planning system | POST demandForecasts (measure upload) |
| Planned order | firmed supply decisions written back | PATCH planningSupplies (firm, release) |
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 |
|---|---|---|
| Forecast | Demand Management: forecast measures (REST / planning data extract) | MRP_FORECAST_DATES · MRP_FORECAST_ITEMS (write: MRP_FORECAST_INTERFACE) |
| Planned order | Supply Chain Planning REST: planningSupplies (planned orders) | MRP_RECOMMENDATIONS · MRP_PLANNED_ORDERS |
| Stock position | Inventory REST: inventoryOnhandBalances · inventoryItemLots | MTL_ONHAND_QUANTITIES_DETAIL (write: MTL_TRANSACTIONS_INTERFACE) |
| Sales order line | Order Management REST: salesOrdersForOrderHub · lines | OE_ORDER_HEADERS_ALL · OE_ORDER_LINES_ALL (write: OE_HEADERS_IFACE_ALL · OE_LINES_IFACE_ALL) |
| Budget line | Budgetary Control REST: controlBudgetBalances · EPM plans | GL_BUDGETS · GL_BALANCES (budget) |
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.
