|
Siebel Field Service Guide > Service Inventories >
About Inventory Transactions
The Service Inventory module is transaction-based. Inventory transactions update inventory levels when you move parts between locations or when an inventory level changes. Each inventory transaction has a product, quantity, source, and destination. Some examples of business activities that create inventory transactions follow:
- Perform a part movement by installing or removing the part and moving it out of or into the trunk of the field service engineer.
- Allocate (or reserve) or de-allocate a product for an order line item. You can manually perform this task, or the Fulfillment Engine can perform this task.
- Ship an order, and click the Process Shipment button in the Shipping screen.
- Receive an order, and click the Generate Transaction button in the Receiving screen.
- Manually create a transaction in the Inventory Transactions screen.
Table 32 describes the types of inventory transactions.
Table 32. Types of Inventory Transactions
|
|
Adjustment |
Adjusts inventory levels when, after a cycle count, there is a variance between original inventory and counted inventory. This type is automatically generated in the Variance view of the Cycle Counts screen. You can manually generate this type in the Inventory Transactions screen. |
Allocate |
Adds inventory to an inventory level with an Availability field value of Reserved. This type is automatically generated when an Allocate action is called for an order line item. |
De-Allocate |
Clears inventory from an inventory level with an Availability field value of Reserved. This type is automatically generated when a De-Allocate action is called for an order line item. |
Exchange Between FSEs |
Moves inventory from a trunk inventory to another trunk inventory. This type applies to part movements between trunks of field service engineers. You can manually generate this type in the Inventory Transactions screen. |
Over-the-counter |
Moves inventory from an inventory location or level to another location or level. This type applies to part movements from warehouses to trunks of field service engineers. You can manually generate this type in the Inventory Transactions screen. |
Receive From TP |
Moves inventory from a third-party location defined in the Fulfillment view of the Service Orders screen to the inventory location defined in the Line Item Receipts view of the Receiving screen. |
Receive Internal |
Moves inventory from an inventory level with an Availability field value of In Transit to a physical inventory level, such as a shelf in a warehouse. This type is a stock transfer that is automatically generated in the Receiving screen. |
Receive Other |
Moves received inventory to an inventory level. This type is part of a customer transaction that uses a virtual inventory location of External Location or Customer. These locations are included as seed data in Siebel Field Service. Inventory is received from the Customer location to the location in the Line Item Receipts view of the Receiving screen. |
Ship Internal |
Moves inventory from a physical inventory level to an inventory level with an Availability field value of In Transit. This type is for internal orders and is a stock transfer that is automatically generated in the Shipping screen. |
Ship Other |
Moves inventory from a physical inventory level to an inventory level with an Availability field value of In Transit. This type is for outside orders and is part of a customer transaction that uses a virtual inventory location of Customer. The Customer location is included as seed data in Siebel Field Service. |
Ship To TP |
Moves inventory from the location from which the inventory is allocated (and for which the pick ticket is generated) to the destination location defined in the Fulfillment view of the Service Orders screen. |
Stock Transfer |
Moves inventory from an inventory level or location to another level or location. The inventory levels or locations can be in the same warehouse or in different warehouses. You can manually generate this type in the Inventory Transactions screen. |
Conditions for Generating Transactions
Table 33 lists the types of inventory transactions that are created for combinations of source and destination locations, inventory levels, and serialized or nonserialized assets.
Table 33. Conditions for Generating Transactions Types
|
|
|
|
|
|
|
|
|
|
Part movement on activity |
Ship Other |
Trunk of FSE |
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 Hdr Destination Invloc ID |
In Transit |
Yes |
De-Allocate |
Ord Part Movement Source Invloc ID |
Reserved |
Yes |
Customer |
On Order |
Yes |
Receive RMA and PO |
Receive Other |
Customer |
On Hand |
Yes |
Ord Part Movement Destination Inv |
Ord Part Movement Availability and Status |
Yes |
Receive internal |
Receive Internal |
Order Hdr Destination Inv |
In Transit |
Yes |
Ord Part Movement Destination Inv |
On Hand |
Yes |
Ship RO |
Ship To TP |
Ord Part Movement Source Inv |
On Hand |
Yes |
Order Hdr Destination Invloc ID |
On Hand |
Yes |
De-Allocate |
Ord Part Movement Source Invloc ID |
Reserved |
Yes |
Customer |
On Order |
Yes |
Receive RO |
Receive From TP |
Order Hdr Destination Inv |
On Hand |
Yes |
Ord Part Movement Dest Inv |
On Hand |
Yes |
NOTE: For the asset columns in the preceding table, the assets are included in the transaction validation if the product is serialized. Also, TP represents third-party vendor in this table.
The following rules regulate the generation of inventory and asset transactions:
- If a product is serialized, then:
- If the product is not serialized and no asset number is specified, then a committed inventory transaction is successfully generated without validation.
- If the product is not serialized and no asset number is specified, then an asset validation and an asset transaction do not occur. The inventory location is not associated with the asset.
|
