Supply chain and planning on Oracle Fusion

Excess and obsolete inventory review on Oracle Fusion Cloud

Finds stock with cover above a threshold or a long idle time, gives each position to its planner with the options, and posts the decision in the ERP.

SCREENSDATA HANDLERSORACLE FUSION · READ IN PLACES01 Excess positionsS02 Position detailS03 DispositionS04 Finance reviewS05 Warehouse executionS06 Boarddh_stock_positionStock positionInventory REST: inventoryOnhandBalances· inventoryItemLotsdh_material_masterMaterial masterProduct Hub REST: itemsV2dh_forecastForecastDemand Management: forecast measures(REST / planning data extract)dh_sales_order_lineSales order lineOrder Management REST:salesOrdersForOrderHub · linesdh_batchBatchInventory REST: inventoryItemLotsdh_journal_lineJournal lineGeneral Ledger REST: journals · BICC GLjournal lines extractWRITE BACK TO ORACLE FUSIONStock position → POST inventoryTransactions (transfer, scrap, status)Material master → POST/PATCH itemsV2Journal line → POST journals (ERP Integration Service, FBDI)rows 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
6
screens on those rows
catalogue
6 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
Stock positionInventory REST: inventoryOnhandBalances · inventoryItemLotsOnhandQuantity (on hand) · OnhandValue (costing extract) (value) · LastUpdateDate (last movement) · ItemNumber (material)live through the API
Material masterProduct Hub REST: itemsV2ItemNumber (id) · ItemDescription (desc) · ItemType (type) · OrganizationCode (plant)live through the API
ForecastDemand Management: forecast measures (REST / planning data extract)ForecastQuantity (qty) · Item (material) · Organization (plant) · TimeBucket (period)live through the API
Sales order lineOrder Management REST: salesOrdersForOrderHub · linesOrderedQuantity (qty) · OrderNumber (number) · LineNumber (line) · BuyingPartyNumber (customer)live through the API
BatchInventory REST: inventoryItemLotsLotNumber (batch) · ItemNumber (material) · ExpirationDate (expiry) · OriginationDate (produced)live through the API
Journal lineGeneral Ledger REST: journals · BICC GL journal lines extractJournalBatchName / JournalName (document) · AccountCombination (account) · EnteredDr − EnteredCr (amount) · Segment (cost center) (cost center)live through the API
The trigger

The start criterion in Oracle Fusion's own fields

In plain words: A stock position worth more than 5,000 whose on-hand quantity covers more than 12 months of forecast and open orders, or whose last movement is older than 180 days.

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
OnhandValue (costing extract) > 5000 and (OnhandQuantity > 12 months of ForecastQuantity + OrderedQuantity or LastUpdateDate < today - 180)

# the same criterion in canonical fields
{stock.value} > 5000 and ({stock.on_hand} > 12 months of {forecast.qty} + {so.qty} or {stock.last_movement} < today - 180)
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
Stock positiontransfer to another plant or scrap posted as a goods movement; quantity moved to blocked stock while a decision is openPOST inventoryTransactions (transfer, scrap, status)
Material masterplant status set to phase-out so planning stops creating new ordersPOST/PATCH itemsV2
Journal linethe agreed reserve change posted as a journal at month endPOST journals (ERP Integration Service, FBDI)
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
Stock positionInventory REST: inventoryOnhandBalances · inventoryItemLotsMTL_ONHAND_QUANTITIES_DETAIL (write: MTL_TRANSACTIONS_INTERFACE)
Material masterProduct Hub REST: itemsV2MTL_SYSTEM_ITEMS_B (write: MTL_SYSTEM_ITEMS_INTERFACE)
ForecastDemand Management: forecast measures (REST / planning data extract)MRP_FORECAST_DATES · MRP_FORECAST_ITEMS (write: MRP_FORECAST_INTERFACE)
Sales order lineOrder Management REST: salesOrdersForOrderHub · linesOE_ORDER_HEADERS_ALL · OE_ORDER_LINES_ALL (write: OE_HEADERS_IFACE_ALL · OE_LINES_IFACE_ALL)
BatchInventory REST: inventoryItemLotsMTL_LOT_NUMBERS
Journal lineGeneral Ledger REST: journals · BICC GL journal lines extractGL_JE_HEADERS · GL_JE_LINES (write: GL_INTERFACE)
Nearby

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

Excess and obsolete inventory review on

Other apps on Oracle Fusion

Terms on this page

CoverThe months of demand the on-hand quantity serves: on hand divided by the average monthly forecast and orders.
ReserveThe amount finance sets aside against stock that may sell below its book value.
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.