OptimonCoreSync Studio
IE
WMS-UI-01 CatalogueUI-02 Connection & 3PL scopeUI-03 Capability matrixUI-04 Warehouse contractsUI-05 BindingsUI-06 Inventory reconciliationUI-07 InboundUI-08 OutboundUI-09 LocateLinkUI-10 Count / return / holdUI-11 Recovery & qualificationUI-12 Simulation labImport checks
CS-CON-0253

Oracle Fusion Cloud Warehouse Management

DETAILproposed target — not qualified← CS-CON-0252CS-CON-0254 →
Synthetic warehouse workspace. No native WMS source has been connected. Every profile is a proposed target, no adapter is live or qualified, and no row here was read from a WMS, a WES/WCS or an RTLS. The 18 warehouse payload specs are proposed additive specializations of the V9 canonical contracts, not approved replacements.

Source identity and scope

Aliases
Oracle WMS Cloud · LogFire lineage
Segment
Enterprise WMS
Engine
rest
Read scope
WMS outbound LPN inventory, inventory history/summary, shipping containers, loads, parcel manifests and wave-pick information through approved REST, SFTP or events
Interface detail
Object/direction matrix reviewed. Pin actual WMS endpoint and interface schema from the tenant/current interface package; no generic Fusion SCM endpoint substitution
Incremental and recovery
Capture company+facility+object identity and revision; preserve inventory-history sequence or extract manifest and snapshot cutoff where exposed
Limitations
Inbound in the vendor matrix means data going into WMS, not read acquisition by CoreSync. Do not present inbound write APIs as source-read endpoints
Implementation
Not built / not qualified
Configuration schema reference
catalogue/config-schemas/CS-CON-0253.schema.json

Reviewed primary source

Evidence
DETAIL — Technical reference reviewed
Document
Warehouse Management business objects available for integration — 25C
URL
https://docs.oracle.com/en/cloud/saas/supply-chain-and-manufacturing/25c/faips/wm-business-objects-available-for-integration.html
Review date
2026-09-22
Evidence scope
WMS outbound LPN inventory, inventory history/summary, shipping containers, loads, parcel manifests and wave-pick information through approved REST, SFTP or events.
Remaining verification
Inbound in the vendor matrix means data going into WMS, not read acquisition by CoreSync. Do not present inbound write APIs as source-read endpoints.

DETAIL means the stated technical reference was reviewed — it does not mean every warehouse function of this product was verified, and vendor wire formats are never inferred from the supplied normalized fixtures.

Required configuration — 10 settings

company_codesfacility_codeswms_releaseinterface_package_refextract_channelapproved_endpoint_bindingfacility_mapping_set_refowner_mapping_set_refsource_timezoneobject_contract_refs

Every one of these must be supplied before a connection draft is accepted. Secrets are held as opaque references; no credential value is ever entered or displayed here.

Configure a simulated connection →

Per-object capability matrix — 17 objects

Warehouse objectNative supportSource-version qualification
Bin / location masterunverifiednot_run
Item / owner masterunverifiednot_run
Handling unitsunverifiednot_run
Inventory balancesunverifiednot_run
Inventory movementsunverifiednot_run
Reservationsunverifiednot_run
Inbound adviceunverifiednot_run
Goods receiptsunverifiednot_run
Warehouse tasksunverifiednot_run
Wavesunverifiednot_run
Outbound ordersunverifiednot_run
Shipmentsunverifiednot_run
Cycle countsunverifiednot_run
Adjustmentsunverifiednot_run
Returnsunverifiednot_run
Stock holdsunverifiednot_run
Location observationsunverifiednot_run
Capability discoveryRun the 12 scenariosRecovery & qualificationBack to WMS catalogue