Validation Checks for Commit Buttons

Commit buttons appear in the Part Tracker view of the Activities screen and the Parts Movement Administration view of the Administration - Service screen. The commit step for a transaction begins when users save the record and select the Commit check. The field service engineer uses the commit buttons in the Part Tracker view to perform the following validation checks:

  1. Verify that the source and destination inventories are specified. If the asset does not exist in the source inventory, then do not commit the asset.

  2. Verify that the position of the activity owner is associated with a trunk inventory. Trunk inventories have a Type field value of Trunk.

  3. If an asset number is specified, then verify that the number is valid.

  4. For each asset transaction, verify that the asset exists at the specified inventory source location. This validation is not performed for the External location or the Customer location. For more information about external inventory locations, see Inventory Locations.

  5. Verify that the asset is available. Verify the availability and status. This validation is not performed for the External location.

  6. Verify that the quantity of specified assets exists in the source inventory. This quantity is 1 if the product is serialized.

  7. If the product is serialized, then verify that the total quantity for the inventory transaction is equal to the total number of specified assets for the transaction.

If these validation checks are successful, then the Commit check box is selected for the records, and transaction records for part movements are generated in the Siebel database.

The commit buttons validate the movement of serialized and nonserialized assets that are recorded in the local database. If the part movement record defines an asset, then an asset transaction is recorded.

A user can create a part movement record without changing the inventory levels. To change the inventory levels, the user selects the Commit check box for the record or clicks the Commit button for the record.

The Commit button creates a transaction for a selected uncommitted record in the view. The Commit All button creates transactions for all uncommitted records in the view. Committed records are read-only. You cannot uncommit a record that is committed.