Native Inventory flows with Oracle Fusion Field Service

Oracle Fusion Field Service supports searching and recording Fusion on-hand inventory from the Debrief page without using an OIC accelerator. This lets mobile workers work with a consistent Fusion Inventory Management model, including locator support, while staying in the Oracle Fusion Field Service application. Mobile workers can search for and install Fusion inventories directly from the Debrief page in Oracle Fusion Field Service. This capability uses stocking locations that you configure in Oracle Service Logistics and no longer requires the Oracle Integration Cloud Inventory Management accelerator for this specific use case.

Field Service loads eligible Fusion inventory when the mobile workers signs in, based on the stocking locations assigned to the mobile worker’s resource profile. After the data is loaded, mobile workers can search and install inventory from the Debrief page in both online and offline modes.

Note: Fusion inventories aren’t listed on the Field Service Inventory page. Installed items are visible in the Service Work Order debrief in the Fusion environment.

Advantages

  • Enable native inventory interaction between Oracle Fusion Field Service and other Fusion applications, without an OIC accelerator.​

  • Use a single Fusion Inventory Management model end-to-end, including locator-based control and stocking location assignments.

  • Maintain strong offline inventory capabilities so field technicians can continue work even when they have limited or no connectivity.

Before you start

Make sure stocking locations are set up and assigned to the appropriate field service mobile workers in Service Logistics.

  1. In the Service Logistics setup, create stocking locations that link an organization and sub inventory, and mark them as usable.​

  2. Assign stocking locations to the field service mobile workers who will use inventories in Oracle Fusion Field Service.​

  3. Optionally, use the REST APIs to maintain stocking locations programmatically (for example, to create or update locations in bulk).​

For details, see the Service Logistics and SCM REST API documentation.