Bookshelf Home | Contents | Index | Search | PDF |
Siebel Field Service Guide > Service Inventory > Service Inventory Overview >
Inventory Transactions
The Service Inventory module is transaction-based. Field Service uses inventory transactions to update inventory levels in response to parts movements between two locations or whenever there is change in an inventory level. Each inventory transaction has a product, a quantity, a source, and a destination.
Here are some examples of business activities that create inventory transactions:
- Perform a part movement by doing an install or uninstall of a part and move it into or out of the service engineer's trunk.
- Allocate or de-allocate a part against a line item on an order, either manually or through the Fulfillment engine.
- Ship an order and click the Process Shipment button on the Shipping screen.
- Receive an order and click the Generate Transaction button on the Receiving screen.
- Create a transactions manually in the Inventory Transactions screen.
Table 86 summarizes the types of inventory transactions.
Table 86. Summary of Types of Inventory Transactions Type Description Adjustment Adjusts inventory levels; for example, if after a cycle count there is a variance between original inventory and counted inventory. Manually generated in the Inventory Transactions screen, or automatically in Cycle Counts > Variance (see Cycle Counts Screen). Allocate Adds inventory to an inventory level with an availability of Reserved. Automatically generated when an Allocate action is called for an order line item. De-Allocate Clears inventory from an inventory level with an availability of Reserved. Automatically generated when a De-Allocate action is called for an order line item. Exchange Between FSEs Moves inventory from one trunk inventory to another. Intended to move inventory between field service engineers. Manually generated in the Inventory Transactions screen. Over-the-Counter Moves inventory from one inventory location or level to another. Intended to move inventory from warehouses to field service engineers' trunks. Manually generated in the Inventory Transactions screen. Receive from TP Moves inventory from a third-party location that is defined in the inventory system (in the Orders screen, Fulfillment view) to the inventory location defined in the Receiving screen, Line Item Receipts view. Receive Internal Moves inventory from an inventory level with the availability of In Transit to a defined physical inventory level, such as a shelf in a warehouse. A stock transfer, automatically generated in the Receiving screen. Receive Other Enters inventory, on receipt, into an inventory level. Part of a transaction with a customer, which uses a virtual inventory location called External Location or Customer. These locations come as seed data with Field Service. Received from the Customer location to the location specified in the Receiving screen, Line Item Receipts view. Ship Internal For internal orders, moves inventory from a physical inventory level to an inventory level with the availability of In Transit. A stock transfer, automatically generated in the Shipping screen. Ship Other For outside orders, moves inventory from a physical inventory level to an inventory level with the availability of In Transit. Part of a transaction with a customer that uses a virtual inventory location called Customer. The Customer location comes as seed data with Field Service. Ship to TP Moves inventory from the location from which the item was allocated and the pick ticket generated to the destination location defined in the Orders screen, Fulfillment view. Stock Transfer Moves inventory from one inventory level or location to another, whether the inventory levels or locations are in the same warehouse or in different warehouses. Manually generated in the Inventory Transaction screen.Conditions for Generating Transactions
Table 87 defines the types of inventory transactions created for combinations of source and destination locations, inventory levels, and serialized versus non-serialized assets.
Table 87. Conditions for Generating Transactions Types Source Destination Inventory Transaction Inventory
Txn Type Inventory Inventory Level Assets1 Inventory Inventory Level Assets1 Part movement on activity Ship Other Trunk of FE On Hand Yes Customer On Hand Yes Receive Other Customer On Hand Yes Trunk of FSE On Hand Yes Allocate action Insertion on order entry Allocate Customer On Order No Ord Part Movement Source Invloc ID Reserved No De-allocate action Insertion on order entry De-allocate Ord Part Movement Source Invloc ID Reserved No Customer On Order No Ship other Ship Other Ord Part Movement Source Inv On Hand Yes Customer On Hand Yes De-allocate Ord Part Movement Source Inv Reserved Yes Customer On Order Yes Ship internal Ship Internal Ord Part Movement Source Inv On Hand Yes Order header. Destination Invloc ID In Transit Yes De-allocate Ord Part Movement Source Invloc ID Reserved Yes Customer On Order Yes Receive RMA/PO Receive Other Customer On Hand Yes Ord Part Movement Dest Inv Ord Part Movement Avail/Status Yes Receive internal Receive Internal Order Hdr Destination Inv In Transit Yes Ord Part Movement Dest Inv On Hand Yes Ship RO Ship to TP2 Ord Part Movement Source Inv On Hand Yes Order header. Destination Invloc ID On Hand Yes De-allocate Ord Part Movement Source Invloc ID Reserved Yes Customer On Order Yes Receive RO Receive from TP2 Order Hdr Destination Inv On Hand Yes Ord Part Movement Dest Inv On Hand Yes
1The assets rows are included in the transaction validation if the product is serialized.
2Third-party provider.
The following rules regulate the generation of inventory and asset transactions:
- If a product is serialized:
- The asset for the part movement must be specified.
- The quantity of the part movement must be 1.
- The asset must belong to the source inventory.
When these conditions are met, the inventory transaction is validated and the inventory database is updated.
- If the product is not serialized and no asset number is specified, a committed inventory transaction is generated without validation and committed successfully.
- If the product is not serialized and no asset number is specified, neither an asset validation nor an asset transaction takes place. The inventory location is not stamped on the asset.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Field Service Guide Published: 21 April 2003 |