Siebel Field Service Guide > Service Inventory > Service Inventory Overview >

Inventory Relationships


An inventory location is linked to other locations by relationships that define physical spaces, replenishment sources, fulfillment sources, and cycle counting lists. An inventory structure consists of a network of relationships.

Siebel Field Service can implement an inventory structure in several ways:

While considering fulfillment, generating cycle counting lists, or running the Replenishment Engine at the warehouse level, all inventories below the Warehouse level (and connected using sublevels) are automatically considered.

To boost performance (for example, to avoid traversing a tree every time it is necessary to find all sublevels of inventory for a warehouse), Field Service uses a denormalized table. This table stores every child, direct child, or grandchild (to any number of levels deep) of a parent inventory. If an inventory hierarchy is defined as follows:

Then Table 85 summarizes the entries in the denormalized table.

Table 85.  S_INVLOC_ROLLUP
Parent Invloc
Invloc
A
B
A
C
A
D
A
E
A
F
B
E
B
F

Inventory locations may also be related through replenishment. However, replenishment relationships should be defined for inventory locations of type Warehouse only. For example, configuring the replenishment relationship "Oakland field office replenishes trunk" may result in the trunk inventory being overstocked if the trunk location is already a sublevel of a parent inventory.

NOTE:  Fulfillment and replenishment relationships between inventory locations should be set at the warehouse level, and not at lower levels; for example, aisles, bins, or shelves. When using relationships, the Fulfillment, Replenishment, and Part Locator Engines automatically search for parts at lower levels by using sublevel relationships.


 Siebel Field Service Guide 
 Published: 21 April 2003