Managing Inventory Transactions
  • 23 Jan 2023
  • 1 Minute to read
  • Contributors
  • Dark
    Light

Managing Inventory Transactions

  • Dark
    Light

Article Summary

The Inventory Transactions table lists all events (such as used, lost, broken, or transferred) for the objects tracked through the Mobileforce FSM Inventory, which may consist of parts, tools, equipment, or consumables.

Example:

If a technician is working on a service task that requires borrowing a jackhammer from the warehouse, installing equipment using four bolts from their truck, and consumes a can of silicone spray, then each of these would be tracked through an inventory transaction.

This table allows you to review the inventory that was used for this task for planning, auditing, and purchasing decisions.

Mobileforce displays the Inventory Transactions section on the Service Task page, allowing you to review all transactions for the task.

image.png

Additionally, you can click the image238 button to open the table in its own window.

image.png

The Inventory Transactions table lists the following columns:

  • Name:
    The name of the transaction.
  • Transaction Type:
    Descriptions that help track inventory creation and consumption. These types can also be customized for your specific business needs. If you need further customization for this list, please contact Mobileforce Support.
    The default values are:
    • Borrowed for a Service Task
    • Returned to Warehou se
    • Stored on Fleet
    • Used in a Service Task
    • Scrapped or Discarded
    • Lost or Misplaced
    • Transferred to another Warehouse
Note:

Transaction Types are meant primarily for inventory tracking, and not for your entire inventory lifecycle management

  • Inventory:
    The inventory item used for the service task. This item is listed in the Mobileforce FSM Inventory table.
  • Fleet:
    The vehicle or equipment associated with the inventory transaction. (for example, the truck where the item is stored on, or a vehicle, such as a cement mixer, that was borrowed for the task.)
  • Service Task:
    The name of the service task associated with the transaction.
  • Customer Location:
    The user who generated the transaction in Mobileforce FSM.
  • Quantity:
    The number of the specified inventory item used or borrowed to complete the service task. .
  • Comments:
    Any information that needs to be communicated between the technician and the agents and dispatchers who will review the transaction. (For example, how equipment became broken or why specific equipment was required for the task.)
  • Created Date:
    The date and time when the transaction was created.
  • Modified Date:
    The date and time when the transaction was last updated.

Was this article helpful?