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

Asset Transactions

The asset transactions that maintain an install 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 generated automatically. For example, a record in the Part Movement list with a source of Customer and a destination of Trunk means that the field service engineer has taken a part out of the customer's installed base and has 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 is repairing, updating, or replacing items referenced in a service order, the engineer selects Service Order as a source and specifies Customer as the destination. Since the item is added to the customer's installed base, only an asset transaction is generated.

You can create asset transactions manually in the Assets screen's Transactions view.

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

Changes can occur in some other fields of the asset's parent component according to the type of inventory transaction. Whether these effects occur on the fields of the hierarchical asset's child subcomponents depends on whether the fields are set to cascade their values from the parent to the child. For more information about hierarchical assets, see Hierarchical Assets.

Siebel Field Service Guide Copyright © 2007, Oracle. All rights reserved.