Siebel Field Service Guide > Service Inventory > Service Inventory Overview >
Mobile Inventory Transactions
Siebel Field Service can record part movements in the field (mobile inventory) without synchronizing with the Field Service server. This allows field service engineers to record transfers of assets without having the asset number or serial number on their laptop computers.
Normally, recording transfers of assets without having asset numbers or serial numbers would cause a transaction to fail. However, with Field Service, the part movement is recorded but not applied to the inventory database.
If the mobile computer is disconnected, the local database is updated. When the mobile computer is synchronized with the Siebel server, the information about the part movement is transferred to the server. If the asset was identified in the database on the remote computer, the server records the change in inventory location in the database and then creates a transaction.
If a part movement was not validated on the remote computer (this includes all add-in assets), an uncommitted part movement appears in the Administration - Service screen > Parts Movement Administration view. For more information, see Parts Movement Administration View. An administrator must review uncommitted part movements and reconcile add-in serial numbers with existing asset numbers. The Commit button then creates transactions. For more information, see To commit transactions reported by mobile clients. For information about the types of transactions created for specific combinations of source and destination locations, see Setting Up Service Inventory.
The next time the remote computer is synchronized, its local database is updated to match the server database.
Commit buttons appear on the Activities screen's Expense Tracker, Part Tracker, and Time Tracker views; and on the Administration - Service screen's Parts Movement Administration view. The commit step of a transaction begins when the record is saved with the Commit flag set. The field service engineer uses the Commit button on the Activities screen to perform validations as described in the following procedure.
To perform validation checks using the Commit button
- Are source and destination inventories specified? This condition must be met first. If the asset does not belong to the source inventory level, leave it uncommitted.
- Is the position of the owner of the activity associated with a trunk inventory (location type Trunk)?
- If an asset number is provided, is it valid?
- For each asset transaction, is the asset at the specified inventory source location? This validation is not performed for the External location or the Customer location. For more information, see Setting Up External Locations.
- Is the item available? Availability and status are verified. This validation is not performed for the External location.
- Does the source inventory have the quantity of assets specified? This quantity is 1 if the part is serialized.
- If the product is serialized, does the total quantity for an inventory transaction equal the total number of assets entered for this transaction?
If these validation checks are successful, the Commit flag is set in Part Tracker records and records are generated to record inventory movements. See the following procedure for more information.
To generate records to record inventory movements
- Create a committed inventory transaction; for example, Receive Other.
- Create assets for the inventory transaction.
- Create new database records for the inventory location: source and destination.
- Update the asset record (ID).
- Create asset transactions; for example, Install.
- Commit the part movement by updating the database.