Inventory issue

In the physical world, inventory is issued when it's handed out of the storeroom to be used in a maintenance task. In Maintenix, the change from unissued to issued is important for tracking stock quantities, triggering financial transactions, creating expected turn-ins for repairable inventory, and for other aspects of material control.

Inventory issue looks different depending on the inventory class and the financial class of the part number. The following table assumes that the tracked item is rotable financial class:
Class Part request status after issue Quantity decrease Issue transaction Issued check box selected
Batch ISSUED Yes Yes No
Serial ISSUED Yes Yes Yes
Tracked ISSUED Yes No Yes
After batch inventory is issued, the bin quantity is reduced for the batch it was taken from and you can see from the part request, that batch inventory was issued. But there's no separate record for the issued or installed items that shows the Issued check box selected. Batch and serial items are consumable so the financial issue transaction is recorded, but rotables even when installed are still considered financially part of the stock. If a tracked item is consumable financial class instead of rotable financial class, then the issue transaction is triggered.
Smaller or larger operations can have different storeroom staffing levels or processes. You can configure inventory issue to meet your requirements with greater or lesser control over whether unissued inventory can be installed. Depending how you operate, inventory is issued in Maintenix in the following ways:
  • Inventory issue is recorded in real time when a supply clerk passes inventory to technician and issues inventory in Maintenix. When the inventory is installed and the work is recorded, validation checks for unissued inventory might be set to block installations.
  • Inventory is auto-issued by Maintenix when the storeroom has not issued the inventory, but the task to install the part is completed:
    • A technician installed the item records the work capture. This scenario could occur when a part is required to address an AOG fault raised on a late night inspection and it's after hours for the warehouse.
    • In an IN WORK work package, a user clicks Complete Task, Batch Complete Tasks, or Batch Complete All Tasks.
    When the installation task is completed, validation checks for unissued inventory might be set to warn or to provide information.
  • Inventory is issued in Maintenix by a store room clerk after it is installed by a technician. This is called after-the-fact issue and an alternative configuration to having Maintenix auto-issue inventory when the storeroom is not available to issue inventory required for maintenance tasks. When the inventory is installed and the work is recorded, validation checks for unissued inventory might be set to warn or to provide information.
  • Inventory is issued in Maintenix when technical records clerks record historical maintenance. In this scenario, clerks enter the information from job cards into Maintenix. When maintenance work is recorded, validation checks for unissued inventory are set to provide information.

Maintenix validation checks and messages for unissued inventory must be configured to block, warn, or provide information to technicians who are installing inventory and recording the work. For information, see the Maintenix Administration Guide.

When inventory is issued by a storeroom clerk, in addition to the part request, quantity, and financial transactions changes, an issue transfer is created from the current location to where needed location, and for repairable parts, an expected turn-in is created.

If there's no part requirement for an item that you issued for a task, Maintenix creates and adds the part requirement to the task. From a part request with reserved inventory for a task in a work package, if you issue inventory but specify a different item that isn't in the system, Maintenix automatically creates a record for item, issues it, and sends an alert to designated users and roles.

The Issue to-do list tab displays a list of reserved inventory items that are waiting to be issued. To prepare for issuing these items, you can pick them from their location in the warehouse and bring them to a pre-draw location that is close to the issue desk. You can then issue the pre-drawn inventory for the work packages for which they were reserved.

Issue tickets, also known as pick tickets, identify the current location of the inventory and the work location where the inventory is needed. An issue list is a printable report that groups together by account, the items to be issued.

When the same inventory item appears in multiple accounts, Maintenix lists the total number of items that must be picked for the first entry, and marks each subsequent entry as already picked. This prevents multiple trips to the same bin to pick the same inventory for multiple accounts. For a reserved item that is part of a kit, both the issue ticket and issue list display the In Kit column, which shows the serial number of the kit that contains the item to be picked.

When you attempt to issue inventory, Maintenix displays an error or a warning message:

  • If a part has usage-based maintenance requirements and the remaining usage for the part is less than the minimum usage required for a task.

  • If a part requires controlled reservation and has a serial number or a batch number that does not match the reserved inventory. In this case, you must issue the inventory item that is reserved.

  • If a kit is incomplete. In this case, you can either cancel the issue attempt, or acknowledge the warning and proceed to issue the incomplete kit.

  • If the ownership type is EXCHRTRN.

Maintenix allows you to install serialized inventory for work packages scheduled externally by automatically issuing inventory and canceling the part request, if the following conditions are met:
Note: If the AUTO_ISSUE_INVENTORY configuration parameter is enabled, inventory is issued irrespective of the following conditions.
  • The work package is scheduled at an auto-issue enabled Vendor Line or Vendor Track location.

  • The inventory is serviceable (with a condition of RFI or RFB).

  • The inventory is available locally.

Auto-issue details

In general, when a TRK, SER or BATCH inventory is specified as the installed part on a part requirement, and the same inventory is reserved for the corresponding part request, then the inventory is automatically issued when the task is completed and the part request is canceled. In other scenarios when the inventory specified for install does not match the reserved inventory or is otherwise not available, then the part request status changes to AWAITING ISSUE or CANCEL depending on the inventory class.

Maintenix only auto-issues inventory that exists the system, exists in the supply location where maintenance is performed, and is currently unissued.

The following table outlines what happens in various scenarios when auto-issue is enabled.
Auto-issue inventory logic
Part request/Part installed Part request status changed to Quantity decrease? Issued transaction Issued check box selected
Part request = Available or Remote

Reserved part installed

Bat Cancel
Ser Cancel
Trk Cancel
Bat Yes
Ser Yes
Trk No
Bat Yes
Ser Yes
Trk No
Bat No
Ser Yes
Trk Yes
Part request = Available or Remote

Unreserved part installed

Bat Await Issue
Ser Cancel
Trk Cancel
Bat No
Ser Yes
Trk No
Bat No
Ser Yes
Trk No
Bat No
Ser Yes
Trk Yes
Part request = Open or any status except Avail/Remote

Unreserved part is installed

Bat Await Issue
Ser Cancel
Trk Cancel
Bat No
Ser Yes
Trk No
Bat No
Ser Yes
Trk No
Bat No
Ser Yes
Trk Yes
Part request = Open

Part reserved for another part request is installed

Bat Await Issue
Ser Cancel
Trk Cancel
Bat No
Ser Yes
Trk No
Bat No
Ser Yes
Trk No
Bat No
Ser Yes
Trk Yes
Note: If the auto-issue inventory feature is enabled and a tracked consignment-owned inventory that is to be installed is not issued to a part request, an error message is displayed indicating that tracked consignment-owned inventory cannot be auto-issued and that the inventory must be issued to a part request in order to be installed.

Undo issue

If you issue an inventory item by mistake, if the task the inventory was issued to is unassigned from the work package, or if the item is defective, you can undo the issue action, unless the item is already installed.

When you undo the issue, the part request for the item changes status from ISSUED to OPEN.

If you undo the issue of a part because the task was unassigned from a work package, the Where Needed location and the Needed By date for the task's part request are updated as follows:
  • If the task is not assigned to a work package then the Where Needed location is cleared and the Needed By date is set to the task's due date. If the task no longer has a due date, the Needed By date on the part request is cleared.
  • If the task is assigned to another work package, the Where Needed location for the part request is updated to the location of the work package. The Needed By date is updated according to the status of the task or work package.