Bookshelf Home | Contents | Index | PDF |
Siebel Field Service Guide > Service Inventories > About the Process Flow for Setting Up Service Inventories > Inventory LocationsYou use inventory locations to consolidate and manage all records pertaining to a service inventory. An inventory location can be a trunk for a field service engineer, a warehouse, or a portion of a warehouse, such as a shelf or an aisle. An inventory level specifies the availability and status of a product. You can add an inventory level to any location in an inventory structure. For more information about inventory locations, see Creating Inventory Locations (End User). NOTE: Inventory levels are product buckets in previous versions of Siebel Field Service. Consider the following factors when setting up inventory locations:
You can define different types of inventory locations. The following types of locations are basic to service inventory:
External Inventory LocationsThe seed data in Siebel Field Service contains an inventory location value of External Location. This inventory location that has a Type field value of Virtual is the default inventory location if a source or destination location is not specified. Inventory transactions can occur between organizations by using 2 transactions and the inventory location value of External Location as follows:
Do not delete the External Location record. The ROW_ID (VIRTUAL_INVLOC) makes this record unique. Some C++ code in Siebel Field Service uses this ROW_ID. If you delete this record and re-create it, then the record is assigned a new ROW_ID and some inventory transactions fail. However, you can rename this record. To make sure that all field service engineers in any organization in the company can use the External Location value, use the Organization field to associate all organizations in the company with the External Location value. Trunk Inventory LocationsTo manage trunk inventories, field service engineers record part movements on their laptop computers. They periodically connect their laptop computers to a Siebel Server and synchronize data. To maximize performance during synchronization to and from the local database of the field service engineer, docking rules control the number and context of the records that are extracted, initialized, and synchronized. Because of these rules, an engineer might not see asset records needed to commit a field part movement for a serialized product. To solve this problem, the engineer can add the asset numbers. After synchronization, an administrator reconciles the add-in asset numbers with the corresponding Siebel database records, and the administrator commits the transaction. After the administrator commits the transaction, the field service engineer must synchronize again to update the local database. After the field service engineer synchronizes the laptop computer in the field, an administrator can use the Parts Movement Administration view to review and commit transactions. For more information, see Committing Transactions from Mobile Computers. |
Siebel Field Service Guide | Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |