Oracle Fusion Cloud Supply Chain Management
How Oracle Fusion Cloud SCM provides work order serial numbers to BatteryPass through its REST API and Oracle Integration.
This page describes an integration pattern. BatteryPass ships no connector for Oracle Fusion and has no partnership with Oracle; nothing here is a vendor approval.
The serial numbers of a work order are a child resource of the work order in the REST API:
workOrders/{WorkOrderId}/child/WorkOrderSerialNumber. After a work order is completed, the middleware reads them
together with the item and the completion date and writes a file with the generic-csv preset for
units from production.
Events come through the ERP Cloud Adapter of Oracle Integration, which subscribes to business events of the application and starts an integration flow. Use the event as a trigger and read the data through the REST API afterwards. The REST API accepts basic authentication and OAuth 2.0; prefer OAuth 2.0 with a dedicated integration user that may only read work orders and items.
Interfaces and how they were checked
- Vendor
- Oracle
- Deployments
- Cloud: Oracle Fusion Cloud SCM (REST API 11.13.18.05)
Serial numbers of work orders are a child resource of the work order. Events come through the ERP Cloud Adapter of Oracle Integration.
An integration pattern, not a connector: BatteryPass ships no ERP connector and holds no vendor certification.
| Interface | Protocol | Sign-in | Events | Objects | Checked |
|---|---|---|---|---|---|
REST API (fscmRestApi)Items, work orders and their serial numbers, shipments | REST | Basic auth, OAuth 2.0 client credentials | none | Product/material master, Batch/serial number, Production order, Delivery/goods issue | checked in the vendor documentation, 24/10/2026 |
Oracle Integration ERP Cloud AdapterBusiness events to Oracle Integration | REST | OAuth 2.0 client credentials | Business events (not signed) | Product/material master, Production order, Delivery/goods issue | checked in the vendor documentation, 24/10/2026 |
Notes
REST API (fscmRestApi): The serial numbers of a work order are at workOrders/{WorkOrderId}/child/WorkOrderSerialNumber.
Import presets
Generic CSV file (generic-csv): For any ERP and for files a middleware writes itself: GTIN, serial number, manufacturing date, facility (name or GLN), model version and battery status, with German and English column names.
| Column in the export | Field in BatteryPass |
|---|---|
GTIN (also EAN, GTIN-13, GTIN-14) | GTIN (GS1) identification.gtin |
Serial number (also Seriennummer, serial_number) | Serial number identification.serial_number |
Manufacturing date (also Herstelldatum, manufacturing_date) | Manufacturing date identification.manufacturing_date |
Facility (also Produktionsstätte, Facility GLN, Werk-GLN) | Place of manufacture identification.manufacturing_place |
Model version (also Modellversion, model_version) | Model version model_version |
Battery status (also Batteriestatus, battery_status) | Battery status identification.battery_status |
Workflows
- Units from production: Serial numbers from the production confirmation or goods receipt are staged as an import; members review, commit and approve before any passport appears. Key scopes: import
- Passport links back into the ERP: The middleware follows the change feed and writes the GS1 Digital Link and the passport status to the serial number record in the ERP, so labels and delivery papers carry it. Key scopes: read
- Returns and repairs as lifecycle events: Completed repairs, inspections and component replacements from service or return orders appear as events in the unit's history. Key scopes: readcondition
- Product change leads to a new model version: A change to the product master in the ERP triggers a notification; a member creates a new model version in BatteryPass. Declared data is never written automatically. Key scopes: read