How You Use Assets in Service Logistics

Maintain your customer assets at customer locations using field service or return them for service using depot repair. To do so, you assets require a specific setup and must be based on a maintenance-enabled item that's full-lifecycle tracked. Also, your assets must operate in a maintenance-enabled inventory organization. Through an integration with Oracle Service Logistics, work orders costs are captured in the asset's operating organization.

Overview of Service Logistics

Service Logistics is a part of Oracle Fusion Cloud Supply Chain & Manufacturing and interacts with Oracle B2B Service and other SCM products to support customer and field service as well as manage preventive maintenance work on customer-owned assets.

Using the Service Logistics work area, you can order parts for service requests and work orders that are created in Oracle B2B Service UIs. You can also order parts for third party service requests and work orders. You can set up a variety of field stocking locations and manage the trunk stock of these stocking locations as well as the inventory of field service technicians. Service Logistics also offers depot repair functionality so that you can manage the repair and return of broken parts.

For more details, refer to the Getting Started with Service Logistics Implementation guide

Field Service Preventive Maintenance

Organizations that maintain assets deployed at their customer locations need to perform preventive maintenance activities on those assets using field service functionality. There are two ways to execute field service preventive maintenance: through an OFSC (Oracle Field Service Cloud) activity or through a B2B Service generic work order.

Preventive maintenance work orders for the installed base assets are created in the Oracle Maintenance application.
A scheduled process is run in Service Logistics to generate B2B service SR (service request) and service work orders with the maintenance work order details. These service requests and service work orders are then accessible in the B2B Service UIs, Service Logistics UIs, as well as the Field Service application.
Field service technicians execute these work orders and create debrief using the Field Service application.
Field service administrators edit and create part requirements, review, debrief, finalize, and post charges for the work orders in Service Logistics.
The maintenance work order is then updated to reflect the task completion.

Service Logistics facilitates the integration between Maintenance, B2B Service, and Field Service cloud applications such that field service administrators can oversee preventive maintenance work on customer-owned assets using the Service Logistics application.

When a work order is completed and debriefed, the field service administrator reviews the charges submitted by field service technicians.
The field service administrator may add or edit the debrief lines, make price adjustments if required, and post the charges.
At this stage, a maintenance work order is created to capture the cost of the service, adjust the inventory balances, and update the asset configuration. It's important to configure the items, assets, and the inventory organization properly so that the maintenance work order is created successfully. Note that these setups are specific to field service debrief posting.

Depot Repair

Service Logistics also offers depot repair functionality so you can manage the repair and return of broken parts. In complex depot repair and return logistics environments, the customer asset may be transferred across several locations before it's returned to the customer, for example from a local warehouse to a distribution center and then to the repair depot.

The repaired product may also need to be transferred from the repair depot back to the local warehouse before it's shipped back to the customer. To manage such a multi-location and complex depot repair process, it's important that you set up the depot repair and return supply chain properly in Oracle SCM. Check that your organization, subinventories, interorganization parameters, and ship methods are defined to execute transfer orders between your source and destination organization.