Initiate Part Requirements

To order parts you must first complete the parts header.

Navigate to the Create Requirements page and create your part requirements:

  1. Select Manage Part Requirements from the navigator.
  2. Click the Create Requirement button.
  3. In the Create Part Requirements page, select a value in the Document Type field.
    1. Service Request: Sell parts, exchange parts, create an RMA.
    2. Service Work Order: Order field service parts.
    3. Replenish Trunk Stock: Replenish technician trunk stock.
    4. Replenish Warehouse: Replenish warehouse.
  4. For service requests and service work orders: Select a value from the Document Number field:
    1. If you select Service Request as the document type: Select the service request number from the list of values in the Document Number field. Ship-to Address Type defaults as Customer and the Ship-to Address is the customer address derived from the Ship-to Customer field. Fields that aren't required are disabled.
    2. If you select Service Work Order as the document type: Select the work order number from the list of values in the Document Number field. The ship-to address is automatically populated based on the work order details.
  5. To replenish technician trunk stock: You don't need a document number or a work order number.
    Select the technician name from the Technician list of values. The other fields in the header region are automatically populated based on the technician selected. The list of values displays all the field service technicians that have the following:
    1. Party type of the employee should be Person in TCA Parties.
    2. Usage code is Field Service Technician. The usage code is automatically assigned to the person party when a stocking location is first assigned to the technician in the Manage Field Service Technicians page.
    3. Ship-to site is defined for the technician in the Manage Customers page and an address is added to that ship-to site.
  6. To replenish warehouse: You don’t need a document number or a work order number.
    • The Address Type field defaults to Warehouse and is disabled.
    • You must enter the business unit, destination organization, and destination subinventory.

Create Part Requirements Page

The following table lists the fields in the header region of the Create Part Requirements page.

Create Part Requirements Page - Header Field Descriptions

Attribute

Description

Document Type

Indicates what you're requesting parts for, such as a service request, work order, or for replenishing a stocking location. Values are derived from the ORA_RCL_SOURCE_DOC_TYPE lookup code. Service Logistics has the following predefined document types:

  • Service Request

  • Service Work Order

  • Replenish Trunk Stock

  • Replenish Warehouse

To order parts for third-party work orders such as from a legacy application, your help desk must set it up as a document type using the Service Logistics lookup, ORA_RCL_SOURCE_DOC_TYPE.

The Service Work Order document type is used for generic work orders, Oracle Field Service Cloud work orders, and standalone work orders.

The rest of the fields in the header are disabled or enabled and required or optional based on the document type selected. The document types Service Request and Replenish Warehouse aren't available to field service technicians.

Document Number

Numeric identifier for the service request or work order for which you're creating the part requirement.

  • For a service request created in Fusion Service, you must select from the list of values that shows all the service requests (with a customer party) for which a part requirement line hasn't been created and where the service request status type isn't Closed or Resolved.

  • For work orders created in Fusion Service, select from the list of values that shows all the noncanceled work orders for which a part requirement line hasn't been created. The work order must have an associated service request with a customer party. The list of values also includes the standalone work orders.

  • For a third-party or customer defined document type, you manually enter the document number in an editable text field.

  • This field is disabled for the parts replenishment document types.

Field service technicians will only see the work orders assigned to them in the Document Number list of values. Note that other fields in the header region are automatically populated with details derived from the document number selected. When the document type is a work order, the values default from the work order.

Ship-to Address Type

Drop-down list shows the following values:

  • Customer when the document type is Service Request or Service Work Order.

  • Customer, Technician, and Warehouse when the document type is Service Work Order.

  • Technician when document type is Replenish Trunk Stock.

  • Warehouse when document type is Replenish Warehouse.

  • No default value for customer defined document types.

Customer

Customer for whom the order is created. Value is required when the ship-to address type is Customer. It defaults from the service request selected. For service work orders, it defaults from the work order.

When document type is customer defined, user can select from the list of values available.

Technician

Required when document type is Replenish Technician Trunk Stock. List of values includes TCA Party Names where:

  • Party_Type is equal to Person.

  • Usage Code is equal to Field Service Technician.

  • Party has a TCA address.

When the document type is Service Work Order and the work order has a technician assigned, the technician name defaults in this field.

The technician name also defaults when the user accessing the page is a field service technician.

Business Unit

Unit in which the order is requested. For service requests and work orders coming from Fusion Service, the value is derived from the service request or work order selected. For customer defined document types and for the Replenish Warehouse document type, users can select from the available list of values.

When technician details are entered for certain document types, the business unit is derived from the destination organization details of the technician's default usable subinventory.

Ship-to Address

Field can be edited only when the Ship-to Address Type is Customer, Technician, or Warehouse. If the address type is Customer, LOV displays all the ship-to party site addresses for the selected customer party. If the address type is Technician, LOV displays the ship-to party site addresses of the technician selected. When the address type is Warehouse, the Ship-to Address field is disabled and the default warehouse's address is displayed.

Ship-to Customer

LOV used to select a different customer than the one entered for the document type. This is an optional field used to ship parts to a customer address that's different from the service request.

When parts requirements are created in Service Logistics, this field appears in the header for the following document types:

  • Service Request
  • Service Work Order, with the ship-to address type, Customer
  • Third-party Work Order, with the ship-to address type, Customer
Note: When you select a different customer, the Ship-to Address field defaults to the ship-to customer’s address.

Need By

Date by which the parts are required. For service requests and work orders coming from Fusion Service, the default date is derived from the service request or work order selected.

Destination Organization

List of values includes all organizations modeled as inventory organizations and with at least one subinventory set up in the Manage Stocking Locations page.

The destination organization list of values for the field service technician is restricted to the organizations that the technician has stocking locations assigned.

The default destination organization for warehouse is the inventory organization assigned to the work order’s work area.

Destination Subinventory

Subinventories set up in the selected destination organization and set up in the Service Logistics Manage Stocking Locations page.

Bill-to Customer The default service request customer party. This field is enabled when the document type is from a third party object or when you select a service request as document number.
Bill-to Account

The default account from the bill-to customer, if there's only one account. If there's more than one account, then select an account from the LOV.

Bill-to Address The default address from the bill-to account's primary bill-to address.
Purchase Order The purchase order from the Debrief header or part requirement.