Domain catalogue Supply chain on Oracle Fusion Cloud

Routings and work centres on Oracle Fusion Cloud

Work centres, capacities and routings as governed master data consistent with the BOMs and the site calendars.

SOURCES, READ IN PLACEOracle Fusion CloudERPASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN ROUTINGS AND WORK CENTRESRoutings and work centresone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
The objects the domain reads in place on Oracle Fusion Cloud, the assembly steps, and who reads the result. Writes go through Fusion REST resources and import management.
3
objects read in place from Oracle Fusion Cloud
catalogue
4
attribute groups assembled
catalogue
4 days
to production-grade
estimate
1
write path, acknowledged and logged
catalogue
0
rows copied to start
product
What the domain reads

The Oracle Fusion Cloud objects behind the golden record

Objects are read through Oracle Fusion's REST resources and, for volume, through BI Cloud Connector extracts landed in your lake; the rows stay in Oracle.

ObjectRead fromFields the domain usesFreshness
Work centres and resourcesWIS_WORK_CENTERS_B · WIS_RESOURCES_B (REST: workCenters · resources)WORK_CENTER_ID · RESOURCE_ID · CAPACITYlive through REST; extracts refreshed on schedule
Work definitionsWIS_WORK_DEFINITIONS_B · WIS_WD_OPERATIONS_B (REST: workDefinitions)WORK_DEFINITION_ID · OPERATION_SEQ_NUMBER · WORK_CENTER_ID · USAGE_RATElive through REST; extracts refreshed on schedule
Work ordersWIE_WORK_ORDERS_B (REST: workOrders)WORK_ORDER_ID · STATUSlive through REST; extracts refreshed on schedule
The keys

How routings and work centres records match, in this system's fields

work centre code + siterouting group + item + site

The first object above carries the strong keys; the standardised attributes come from the same rows. Operations name golden work centres, and the rules keep times and capacities inside the site's calendar.

What is written back

Through the interfaces Oracle Fusion Cloud supports

Writes go through Fusion REST resources or import management. Each call returns the record id or an error, and Lima records both beside the change.

InterfaceUsed forResult
REST workCenters · workDefinitions · work definition import (FBDI)golden values approved for write-back: work centre; routing; operationsthe id or error Oracle Fusion Cloud returns, stored beside the change

Write-back is off per object until a test write succeeds, and approval rules can require a person per object. Reconciliation compares the source row with the golden value on a schedule.

Access and prerequisites

What is in place before the first build

Fusion roles and data-security policies are mapped to Lima access policies once; a person sees the same organisations here as in Fusion.

Register the objects3 objects from the connector catalogue; each shows its rows at once.
Also on Oracle E-Business Suite

The same domain on Oracle E-Business Suite

ObjectOn Oracle Fusion CloudOn Oracle E-Business Suite
Work centres and resourcesWIS_WORK_CENTERS_B · WIS_RESOURCES_B (REST: workCenters · resources)BOM_DEPARTMENTS / BOM_OPERATIONAL_ROUTINGS
Work definitionsWIS_WORK_DEFINITIONS_B · WIS_WD_OPERATIONS_B (REST: workDefinitions)same objects
Work ordersWIE_WORK_ORDERS_B (REST: workOrders)same objects
Nearby

This domain on other systems, and other domains on Oracle Fusion Cloud

Routings and work centres on

Other domains on Oracle Fusion Cloud

Terms on this page

Work centreA machine, line or team where operations are performed.
RoutingThe ordered operations to make an item at a site.
Read in placeThe rows stay in Oracle Fusion Cloud; Lima sends the filter and the columns and Oracle Fusion Cloud returns the matching rows.
Questions

Does this domain copy data out of Oracle Fusion Cloud?

The golden record reads the objects above in place. History the pivot needs at scale is landed in your lake by the Backbone, under the same keys, security and audit.

What does the Oracle Fusion Cloud team need to do?

Grant the read access and the write interfaces listed above and agree the refresh method. Nothing is installed in Oracle Fusion Cloud.

Can we start with reads only?

Yes. Write-back stays off per object until a test write succeeds; the golden view, the API and the pivots work from day one on reads.

See your first domain built on your data

Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.