Siebel Field Service Guide > Fulfillment > Fulfillment Overview >

Parameters for the Fulfillment and Part Locator Engines


By specifying input parameters to the Fulfillment and Part Locator Engines, an administrator can define the logic for a specific set of orders (using Order Search Specifications), for a single order (using Order ID), and for a single line item (using Line Item ID). Table 78 contains the parameters for the Fulfillment and Part Locator Engines that are set in the Server Requests screen for the server components FSFulfill and FSLocate.

Table 78.  Parameters for the Fulfillment and Part Locator Engines
Parameter
Value
Comments
InputMode
ORDERSEARCHSPEC
Specifies the WHERE clause for the orders and the engine will fulfill the orders based on the criteria.
ORDERID
Specifies the Single Order ID to be fulfilled and the engine will fulfill the specified Order.
LINEITEMID
Specifies the Single Order line item ID to be fulfilled and the engine will fulfill the specified Order line item.
TEMPTABLE
Places all required values into a temporary table with a particular Client Request ID and passes that ID to the server to retrieve the parameters from Temp Table.
ClientReqId
A row ID for retrieving line items input from the temporary table
Required when InputMode = TEMPTABLE.
RowId
Row ID of a single order to fulfill or Row ID of a single line item to fulfill
Required when InputMode = ORDERID or
InputMode = LINEITEMID.
OrderSearchSpec
A Where clause
Required when InputMode = ORDERSEARCHSPEC.

To set Fulfillment and Part Locator Engine parameters

  1. Identify the predefined system preferences to determine the defaults for the Fulfillment Engine.
  2. Read all the input parameters and identify all the line items from parameters or temp table based on mode.
  3. Fulfill each line item:
    1. Find the product and/or substitute product to fulfill the line item:
    2. Queue the start invloc as the seed to start the search in the relationship.
      Search the product throughout the entire inventory location hierarchy:
      If this invloc has not previously been visited:
      Add the Invloc to the set of Visited Invlocs.
      Search the product for required/available Qty in the Invloc
      hierarchy.
      If the Qty Product < Qty Required, search the substitute product for
      the remaining/available Qty.
      If Qty Product or Qty Substitute is > zero, add the product
      and substitute availability to the warehouse list for the entire
      relationship.
      If the warehouse list is created, then:
      Add Qty Product to Qty Prod Found.
      Add Qty Substitute to Qty Subst Found.
      Determine whether the product is found or the search should
      continue:
      If the allocation rule is Substitute if ship from one location:
      If Qty Product + Qty Substitute is Qty Required,
      stop the search.
      Or else, continue the search.
      If the allocation rule is No substitute if exact found:
      If Qty Product is Qty Required, stop the search.
      Or else, continue the search.
      If the allocation rule is Always substitute:
      If Qty Prod Found + Qty Subst Found is >
      Qty Required, stop the search.
      Or else, continue the search.
      If continue the search, then:
      Queue up all relationships for this invloc for further search.
      Continue the search loop until found or all invloc relationships
      are exhausted.
      If Qty Prod Found or Qty Subst Found is > zero, select the
      best allocation from the list according to the allocation rules.

    3. Allocate the product:
    4. Generate the inventory transaction for all the products of type Allocate, and generate the inventory transaction for all the substitute products of types Substitute and Allocate.

    5. Generate the pick ticket.

 Siebel Field Service Guide 
 Published: 21 April 2003