Inventory Validation Report (17.6.13)

Shows differences between the inventory represented by full replenishment cards and the on-hand inventory balance of the supermarket location. The report compares the two quantities and uses a tolerance percentage specified in Kanban Master Maintenance to identify out-of-tolerance situations. Another field in Kanban Master Maintenance, Lag Factor, lets you specify the number of kanbans that are typically in process for each loop. The system applies this factor to the on-hand balance before comparing the inventory levels. You can use this report to identify situations that might require an audit of card status or an inventory cycle count.

Kanban Card Inquiry (17.3.3)

Shows kanban loop and card data for a specific card.

Kanban Card Status Report (17.3.13)

Lists kanban status data for all the cards in selected loops.

Kanban Card Audit Report (17.3.14)

Compares the system-recommended number of kanban cards for a kanban loop to the actual number of active kanban cards in that loop. You can optionally print the report with a page break inserted at each different supplying source so the report can be distributed to each supermarket for verification of actual kanban card amounts.

Dispatch View by Dispatch ID (17.5.4)

Displays dispatch data for individual cards based on dispatch ID and kanban ID.

Dispatch View by Source/Item (17.5.5)

Displays dispatch data for individual cards based on loop information.

Dispatch Report (17.5.7)

Provides card dispatch information for selected loops; includes option to include card-by-card details.

Item/Loop/Card Transaction View (17.6.8)

Displays kanban and inventory transaction data for individual cards based on item number.

Item/Loop Transactions View (17.6.9)

Displays kanban and inventory transaction data for kanban loops based on item number.

Kanban Card Transactions View (17.6.10)

Displays all kanban transactions associated with a specific kanban card.

Kanban Transaction History Inquiry (17.6.10)

Displays transaction history record for a specified kanban transaction.

Kanban Transactions Audit Report (17.6.15)

Lists kanban transaction history records by various selection criteria associated with the loop, supplying source, or cards.

Authorized Card Report (17.6.17)

Provides summary data on selected replenishment cards that have a status of Auth. For two-card loops, move cards are not included, regardless of their status. When the specified source is a FIFO process, the output also includes replenishment cards with a status of In FIFO. See FIFO Lanes.

Missing Kanbans Report (17.6.18)

Kanbans are sized to print the exact number of cards that fulfill the demand for the kanban-controlled item. When a kanban card is lost or destroyed, it can impact inventory levels negatively.

This report determines the time elapsed between the last time a transaction was entered for a specific kanban card and the current date and time. If the amount of elapsed time is greater than the maximum kanban cycle specified for that kanban, the missing kanban card is included in the report.

Use the Maximum Cycle fields in Kanban Master Maintenance (17.1.1) to define the maximum kanban cycle for each kanban. Kanbans with blank Maximum Cycle fields are ignored by this report.