Siebel Field Service Guide > Service Inventories > About Inventory Transactions >

Asset Transactions

The asset transactions that maintain an installed base are Install, Uninstall, Upgrade, and Downgrade. These transactions do not directly update quantities in inventory levels.

When a field service engineer reports part movements in the field, inventory and asset transactions are automatically generated. For example, a part movement record with a Source field value of Customer and a Destination field value of Trunk means that the field service engineer took a part out of the installed base for the customer and put it in the trunk. The Mobile Inventory Transaction Engine reflects this transfer by creating an inventory transaction (to receive the part into a trunk) and an asset transaction (to change the installed base).

When a field service engineer repairs, updates, or replaces products in a service order, the engineer selects Service Order as the Source field value and Customer as the Destination field value. Because the engineer adds the product to the installed base for the customer, only an asset transaction is generated. You can manually create asset transactions in the Transactions view of the Assets screen.

If you perform any inventory transaction on a hierarchical asset, then only the Inventory Location field of the parent component shows the correct location. The Inventory Location field of the child subcomponents are blank or have a value of External Location.

Changes can occur in some other fields of the parent component for the asset according to the type of inventory transaction. These changes occur in the fields of the child subcomponents for the hierarchical asset if the fields are set to cascade values from the parent to the children. For more information, see Hierarchical Assets.