Enter the number of the item that is replenished with this kanban loop. It must be defined in Kanban Item Master Maintenance (17.1.1).

The same item can have more than one loop. For example, one loop for a purchased item could identify a supplier as the supplying source and a storeroom as the consuming destination. Another loop for the same item could identify the storeroom as the supplying source and a location in production as the consuming destination.

Specify a step number associated with this item for this kanban loop. When you are defining a new kanban loop, the item/step combination must already be defined in Kanban Item Master Maintenance.

Using step numbers lets you identify an item at a stage of the manufacturing process independent of any associated routing information. By using step numbers, you can distinguish between multiple loops with the same item, site, and supermarket.

Enter the site code where the kanban supermarket is located. This value must be defined in Site Maintenance (1.1.13).

Enter the identifier representing the kanban supermarket that is supplied by this loop. This value must be defined for the specified site in Supermarket Maintenance (17.1.2). See Setting Up Kanban Supermarkets.

If you modify an existing record by changing this field, the system prompts you to confirm the change.

Enter the site code associated with the process or inventory supermarket that supplies this loop. This field does not display when Source Type is Supplier.

Enter a process defined in Kanban Process Maintenance (17.1.3) as either a pacemaker or a standard process. This field displays only when Source Type is Process. See here.

When you have associated a range of routing operations with this process in Kanban Process Maintenance, the system displays them at the bottom of the frame.

Enter Yes to display an additional frame that lets you enter one or more references to FIFO lane processes used to produce this kanban item. See here.

This field defaults to No for new kanban master records. When FIFO processes have been entered, the field defaults to Yes. Set it to No if you do not want to enter, delete, or resequence FIFO processes for the kanban loop.

Enter a supermarket defined in Supermarket Maintenance (17.1.2) that supplies this kanban loop. This field displays only when Source Type is Inventory. See here.

Enter a valid, active supplier code defined in Supplier Create (28.20.1.1) and completed in Supplier Data Maintenance (2.3.1).

Optionally identify the purchase order used to obtain this kanban item from the supplier. This must be a valid, open purchase order. It is validated against the item number only when you also specify a line number.

This can be a discrete PO, a supplier schedule, or a blanket PO. If you specify a scheduled order, the system date must fall within the order effective date range; otherwise:

For a blanket PO, when you send a dispatch list to the supplier authorizing replenishment of an empty kanban, you can have the system attempt to release a PO against the blanket by:

When Impact Inventory is Yes in the Kanban Transaction Control frame, the system automatically generates purchase receipt transactions for the specified purchase order when you process replenishment cards for this loop using Kanban Fill/Receive (17.6.5). If you leave these fields blank, the system prompts you for PO information when you record the card. See Inventory Effects.

Enter the sequence in which material goes through FIFO lanes during this process. You can resequence existing records by entering a decimal. For example, if you want to insert a new FIFO process between existing sequence numbers 1 and 2, enter sequence 1.5 for the new process. When you save your changes, the system reassigns sequences 1, 2, and 3 to the process records.

Enter a valid FIFO process ID. This must be defined in Kanban Process Maintenance with Process Function set to FIFO.

If the Kanban Process Maintenance record includes a range of operations, the system displays it for reference. See Process Function.

Optionally specify the supermarket inventory level at which a replenishment order is signaled to the supplying process. When you run the kanban workbenches, the system updates this field based on kanban and supermarket sizing calculations.

This should be a multiple of the value specified in Pack Quantity.

The system displays the actual current supermarket size based on the number of active replenishment cards using the following formula:

For example, inactivating a card in Kanban Card Maintenance (17.3.1) does not automatically reduce the Buffer Maximum value. It does, however, reduce the value of Working Buffer.

Optionally specify the maximum quantity of the item to be maintained in inventory at this supermarket. When you run the kanban workbenches, the system updates this field based on kanban and supermarket sizing calculations.

When you review actual or projected supermarket performance using Historical Buffer Evaluation (17.2.13) or Supermarket Workbench (17.2.7), you can update this field based on a system-calculated optimized maximum buffer size.

This should be a multiple of the value specified in Pack Quantity.

The system indicates whether the initial buffer size has been updated.

This value displays for reference in Historical Buffer Evaluation.

The system displays the last date when the value of Critical Limit or Warning Limit was modified. A blank indicates that the fields are still set to their initial values.

Specify the percentage of the Buffer Maximum value or quantity of items the system should use in determining whether the supermarket buffer size is too small. Use Limit Display to control whether this value is a percentage or a quantity.

When you run Historical Buffer Evaluation or Supermarket Workbench, the system analyzes the actual or projected performance of the buffer size as it relates to this value. Based on the result, it may display recommendations for increasing the buffer maximum.

This cannot be greater than the value in Warning Limit.

You also can update this field using Historical Buffer Evaluation.

See Evaluating Supermarkets.

Specify the percentage of the Buffer Maximum value or quantity of items the system should use in determining whether the supermarket buffer size is too large. Use Limit Display to control whether this value is a percentage or a quantity.

When you run Historical Buffer Evaluation or Supermarket Workbench, the system analyzes the actual or projected performance of the buffer size as it relates to this value. Based on the result, it may display recommendations for increasing the buffer maximum.

This cannot be less than the value in Critical Limit.

You also can update this field using Historical Buffer Evaluation.

Optionally enter the expected daily demand for the item supplied by this kanban loop.

The system automatically updates this value when you run Average Demand Calculation (17.2.1), as well as when you perform kanban and supermarket sizing using Kanban Sizing Workbench. See here.

Optionally specify the template used to calculate the value in Daily Demand when you run Average Demand Calculation or update demand using the kanban workbenches. The template specifies the number of past and future days used in the demand calculation. The field is validated against records set up in Demand Calculation Template Maintenance (17.1.6).

When this field is blank, the system does not calculate average demand for the loop.

The system indicates whether the value of Daily Demand has been updated from its initial setting.

Enter the variability factor for this item. This value is used in order point and order quantity calculations.

Variability must be greater than zero. The default is 1.

Use this field to limit or increase the amount of inventory in the supermarket buffer. Variability factor is similar to safety stock, but can be a more convenient means of estimating variations for factors such as seasonality or sales promotions.

If you adjust the variability factor when performing kanban and supermarket sizing using the kanban workbenches, the system updates this field.

If the supplying source for this loop provides the same item to more than one supermarket, enter the percentage of that source’s total demand consumed by this supermarket.

When you adjust the percentage in the kanban workbenches and save your changes, the system updates this field.

Specify the number of items that are included in the standard packaging for this item. For example, if an item is packaged in a box of 25, set the field to 25.

The system uses this value to calculate the quantity per kanban.

Order Quantity and Buffer Maximum should be multiples of this value.

Optionally specify the type of packaging that holds the quantity shown in Pack Quantity. For example, this could be Box or Case. This field is for reference only. Its value is not validated.

Specify the average inventory calculation method for this loop.

The system calculates the value of the Average Inventory Units field in the kanban workbenches based on this method, as well as various other values from the workbench. See Workbench Data.

Valid values are Standard and Mfg1. This field defaults from Kanban Item Master Maintenance (17.1.1). The calculation methods are described in the discussion of that program. See Average Inventory Calculation Method.

Specify the allowable percentage of variation between the kanban inventory or WIP quantity (depending on the location type specified in Supermarket Maintenance), calculated as the number of full kanbans times the kanban quantity, and the system inventory balance, adjusted by the quantity represented by Lag Factor. The default is 5%.

Inventory Validation Report (17.6.13) marks the loop as out of tolerance if the difference between the inventory quantities varies by more than this percentage. See here.

Specify the number of kanbans that are expected to be in process at any particular time. The default is 0 (zero).

When you run Inventory Validation Report for this loop, the system accounts for the kanban quantity currently in process by multiplying the Lag Factor value by the kanban quantity, then subtracting the result from the system quantity on hand. It then compares the result with the kanban inventory level and determines if the difference is out of tolerance based on the specified percentage.

You can specify a lag factor when a kanban item is a component that is backflushed when the parent item is received sometime later than when the kanban is reported as consumed.

Optionally enter the quantity that is maintained at the supermarket as a buffer to offset unanticipated fluctuations in supply or demand, such as material shortages or special customer orders. See Safety Stock.

Leave this field set to 0 (zero) to have the system calculate a quantity based on the settings in Safety Stock Method, Service Level, and Peak Average Days when you run Safety Stock Calculation (17.2.2). Additionally, if you update the safety stock in the kanban workbenches and save your changes, the system updates this field. Other programs that can update safety stock include Supermarket Workbench and Historical Buffer Evaluation. See Calculate Average Demand and Safety Stock.

This must be less than the values entered in Order Point and Buffer Maximum.

Optionally specify the template used to calculate safety stock when you run Safety Stock Calculation (17.2.2) or update safety stock using the kanban workbenches. The template specifies the number of past and future days used as the basis of demand for safety stock calculations. The field is validated against records set up in Demand Calculation Template Maintenance (17.1.6).

Enter the number of days of demand to be covered by safety stock quantity. When you run Safety Stock Calculation or other programs that update safety stock such as the kanban workbenches or Historical Buffer Evaluation, the system updates the safety stock quantity based on the average demand over this number of days.

If you update the safety days in the kanban workbenches and save your changes, the system updates this field.

Enter a service level associated with this item for this kanban loop. This number cannot be less than 50.00 (the default) or greater than 99.99.

The service level is the percentage of time that inventory for this item does not typically run out before the replenishment time has been reached. For example, 50.00 means that 50% of the time, you will run out of this item before reaching the replenishment time. Higher numbers mean that the supermarket maintains more inventory for the item in the form of safety stock.

When Safety Stock Method is Peak, enter the number of days the system should use as a basis for determining peak average demand. The system calculates the average demand for each period of this number of days over the horizon defined in Demand Calculation Template Maintenance. The highest average demand over one of those periods is the basis of the safety stock calculation.

When Safety Stock Method is Peak, you must enter a value in this field.

Optionally enter a fax number and an e-mail address for the supermarket supplied by this kanban loop.

These values are used when a kanban dispatch list is output as a fax or e-mail. When dispatch lists are processed, kanban data can be sorted by supplying source and/or consuming destination. The dispatch list can be faxed or e-mailed to the supplying source, consuming destination, or both. See Generate Dispatch Lists.

When these fields are blank, the system uses the information specified in Supermarket Maintenance (17.1.2).

You also can enter an alternate fax number. When primary and secondary fax numbers are specified, both numbers, separated by a comma, are printed on the first line of the fax report.

The layout of the first Card Tracking Control frame varies based on this setting. When it is One, the card tracking frame includes a single set of fields for the replenishment card. When it is Two, the frame displays separate columns so that you can define replenishment and move cards independently. See Card Tracking Information.

Optionally, enter the code for the planner who is responsible for this kanban loop. If you enter a value, it is validated against codes entered in Generalized Codes Maintenance for field knb_planner.

Optionally, enter the identifier of a freight carrier associated with a supplier kanban loop. This ID must be defined in Carrier Maintenance (2.17.1). The default is the carrier specified for the supplier in Supplier Data Maintenance (2.3.1).

If an e-mail address is specified in Carrier Maintenance, it defaults to the Carrier E-Mail field. You cannot update it.

Enter the number of units the supplying source will replenish when the inventory level at the supermarket reaches the order point. This can be represented by a single card or by an accumulated quantity from multiple cards. Use the next frame to specify whether multiple cards are accumulated based only on the quantity or on a combination of the quantity and interval-based factors.

You can enter a value manually or have the system update the field when you size the kanban loop using the kanban workbenches.

This should be a multiple of the value specified in Kanban Quantity.

Enter the number of cards to be included in this kanban loop. The system may update this field when the supermarket maximum buffer size is modified.

Enter the number of items per kanban.

Kanban Quantity represents the actual quantity to be placed in each container, regardless of the capacity of that container. For example, you use a standard container that holds 100 items, but you only want 50 items at a time.

Kanban Quantity must be the same as or less than Container Capacity. It should be a multiple of the value specified in Pack Quantity.

The system displays a warning message if you set this field to 0 (zero).

Optionally enter the type of container associated with this kanban item when it is replenished, such as bin or carton. This field defaults from Kanban Item Master Maintenance (17.1.1).

If you enter a value, it must be defined in Container Type Maintenance (17.1.5). See Kanban Containers and Labels.

This information is printed on kanban cards.

Enter Yes to print the kanban quantity on each kanban card. This value defaults from Kanban Control.

Enter Yes to print a kanban ID barcode on each kanban card. This value defaults from Kanban Control.

Enter Yes to print an item barcode on each kanban card. This value defaults from Kanban Control.

Optionally enter an alphanumeric reference (up to eight characters) to this kanban loop. This value displays on various reports and inquiries.

Optionally, enter the number of kanbans that serves as the lowest common denominator for system loop-sizing calculations. If you do not want to enforce an order quantity multiple, leave the field set to the default 0 (zero).

If you enter a value here, the kanban workbenches increase the order quantity until it is a multiple of this value. For example, if you enter 3, the system cannot size the loop at 2 or 5 cards. Instead, it rounds up the order quantity to the next multiple of 3, resulting in a number of cards that is also a multiple of 3: a loop size of 2 would become 3, a loop size of 5 would become 6, and so on.

Optionally enter a one or two-character code specifying the required routine ship or delivery patterns for this kanban loop. Entries are validated against codes defined in Generalized Codes Maintenance for field sch_sd_pat.

The ship/delivery pattern typically specifies the frequency when shipments or deliveries are accepted; for example, any day Monday through Friday, or Tuesday only.

This field is for reference only and can appear on some selected reports and inquiries.

Optionally enter a two-character shipping delivery time (SDT) code associated with this kanban loop.

SDT codes typically relate to exact times for supplier deliveries. Daily item requirements can be split into hour and minute buckets based on these codes.

This field is for reference only. It is not associated with SDT codes used elsewhere in the system.

Optionally enter a code representing the location where the kanban item supplied by this loop is used. Entries are validated against codes defined in Location Maintenance.

This field is for reference only.

Optionally enter a code representing the location where the kanban item supplied by this loop is delivered. Entries are validated against codes defined in Location Maintenance.

This field is for reference only.

Enter Yes to update or enter comments related to cards in this kanban loop; otherwise, enter No. Comments defaults to Yes if comments are already associated with the cards; otherwise, the default is No.

When Comments is Yes, the transaction comments screen displays for you to enter or review comments regarding the cards.

Indicate whether to allow selection of this kanban when dispatch lists are processed.

No: This kanban is ignored when dispatch lists are generated.

Yes: This kanban can be selected for dispatch list processing. When you click Next, the Dispatch Options frame displays. See Dispatch List Information.

Enter the time required to replenish the item in days, hours, minutes, and seconds. This value is used in the calculations performed by the kanban workbenches. If you modify the replenishment time in that program and save your changes, the system updates this value.

Replenishment time includes the total time between recognizing that a product should be reordered and having the product supply available for use. This field represents a contract between supplying and consuming sites, reflecting maximum turnaround time.

Enter the amount of time—in days, hours, minutes, and seconds—required for this item to complete the total number of internal FIFO processes defined for the kanban loop. See FIFO Lanes.

This value is used in due date calculations and the calculations performed by the kanban workbenches. If you modify the internal FIFO time in that program and save your changes, the system updates this value.

This field applies only to loops that are supplied by a primary process that includes one or more FIFO processes.

Enter the amount of time—in days, hours, minutes, and seconds—required for this item to complete the externally performed FIFO processes defined for the kanban loop.

When you run Process Item Operation Rollup for a process that includes operations with subcontract lead times specified in Routing Maintenance, the system adds the lead times for all those operations and enters the total here.

This value is used in due date calculations and the calculations performed by the kanban workbenches. If you modify the external FIFO time in that program and save your changes, the system updates this value.

This field applies only to loops that are supplied by a primary process that includes one or more FIFO processes with subcontract operations.

Specify the method used for kanban card piece reporting. This value defaults from Kanban Control.

This setting affects kanban sizing calculations performed using the kanban workbenches. See Card Reporting for more information.

Specify the fractional kanban percentage for this loop. It cannot be greater than 99%. This field defaults from Kanban Control. See here for more information.

Enter Yes if the source that supplies this item runs the quantity needed to use the entire supply of a given material regardless of the kanban quantity. Otherwise, enter No. This value defaults from Kanban Item Master Maintenance.

Especially in situations with extensive setup times to change over to a key material, it is not always efficient to set up a work center for just the kanban quantity. Instead, you can make enough items to consume an entire bulk quantity of that material. For example, if changing over a process to set up a coil of steel takes significant time, you could consider using the entire coil each time you run the item. The total amount of material available, the quantity required to produce each item, and the amount of time required to change over to a new supply can be useful information for analyzing kanban setup and sizing alternatives.

This field is for reference. The value displays in the kanban workbenches and is included in files created by Kanban Workbench Export, along with the related run-out parameters defined in Kanban Item Master Maintenance.

See Card Accumulators.

Run Accumulator Monitor (17.617.1.6) to update card status and display the status changes in real time. See Monitor Accumulator Quantities.

When Accumulator Type is set to Time, specify in days, hours, minutes, and seconds how often the system can authorize empty kanbans for this item, assuming that the total of empty kanbans has reached the value in Order Quantity.

When Accumulator Type is Time or Schedule, the system calculates and displays the next date and time that Accumulator Monitor will check for empty cards for this loop, based on the value of Accumulator Interval or the Work Day and Time settings.

You can manually override these system-calculated values to check accumulators earlier or later.

When Accumulator Type is Schedule, specify whether the system can authorize empty kanbans for this item on this day of the week, assuming that the total of empty kanbans has reached the value in Order Quantity.

For each day that is set to Yes, you can specify the time of day that the system searches for empty cards.

This display-only field indicates whether loop information has changed that might require you to regenerate and reprint kanban cards using Kanban Card Create (17.3.12). For example, if you print the kanban quantity on your cards and loop resizing updates that quantity, you can regenerate and print correct cards. See Create or Regenerate Cards.

Enter the optional identifier for a kanban label definition associated with this loop. This value must be defined in Kanban Label Definition Maint (17.3.18). See Defining Kanban Labels.

Kanban label definitions are currently for reference only.

Specify whether dispatch list processing attempts to release a PO from a blanket order. When this is Yes and you enter a valid blanket PO number in the Purchase Order field in the Source Master Data frame, dispatch list processing uses that blanket order as the default. When the loop does not specify a blanket PO number, the system attempts to find an available blanket order matching the supplier and item. See Purchase Order and Line.

Indicate whether to allow selection of this kanban when dispatch lists are processed in fax format. When set to No, this kanban is not included in dispatch list fax reports.

Enter the fax number for the supplying source. This number is used when dispatch lists are reported by source. When this field is blank, the system uses the fax number defined in the supplier or site address. When a dispatch list is sorted by supplying source and printed in fax format, this fax number, preceded by a # symbol, is printed on the first line of the report.

Indicate whether to e-mail dispatch lists for this kanban. When set to No, this kanban is not e-mailed or included in dispatch list e‑mail reports.

Enter the e-mail address for the supplying source. This address is used when dispatch lists are reported by supplying source. When this field is blank for a loop supplied by an external supplier and you are using the Supplier Performance module, the e-mail address defined for the supplier is used. Otherwise, the system does not search further. For details on Supplier Performance, see QAD Purchasing User Guide.

Enter Yes to generate dispatch lists for this loop in electronic data interchange format for export to the loop supplier using EDI eCommerce. The default is No. See EDI Dispatch List Transmittal.

When you select this option for a supplier kanban, the system verifies that an EDI eCommerce trading parameter called Send Kanban Dispatch exists for the supplier and has been set to Yes. This is a logical parameter in Trading Partner Parameter Maintenance (35.13.10). If this is not defined, a warning displays.

Specify how cards are managed for this loop when they are recorded in one of the programs on the Kanban Transactions Menu and the system determines that cards should be regenerated. This occurs when certain card-detail values are no longer synchronized with loop values. This field defaults from Kanban Control.

Valid values are:

See Regeneration Enforcement for more information.

Indicate the level of minimum kanban loop cycle enforcement. This field defaults from Kanban Control.

Valid values are:

See Kanban Cycle Enforcement for more information.

The system uses the logic defined here when the item quantity called for does not represent an exact number of kanbans.

Specify the percentage of kanban size the system uses to round off partial kanban quantities in determining the number of cards to select for automated processing.

This value is used in combination with Quantity Mismatch Method. It applies only when that field is set to Round or Warning. When it is Error, the system does not process loops unless the specified quantity is an exact multiple of the kanban quantity.

Leave Rounding Threshold set to the default 100.00 to always round partial quantities down. Change it to 0.00 to always round them up.

Any other value represents the percent of the kanban quantity that must exist before the system rounds up to select an additional card. If the excess quantity is less than this percentage, the system rounds down.

Enter the minimum kanban loop cycle time in days, hours, minutes, and seconds. Values default from Kanban Control.

Leave these fields blank if you do not want to enforce a minimum kanban loop cycle.

Enter the maximum kanban loop cycle time in days, hours, minutes, and seconds. Values default from Kanban Control.

Leave these fields blank if you do not want to enforce a maximum kanban cycle.

Specify whether you want to have cards that are no longer needed removed from this loop the next time they are consumed, as well as whether the system prompts for confirmation before removing them. This value defaults from Kanban Control.

Indicate whether the system should automatically generate the following types of transactions when this kanban-controlled item is received into the supermarket:

This field defaults to Yes when the supplying source is a manufacturing process. Otherwise, it defaults to No and you cannot update it.

See Inventory Effects.

Specify whether the system prompts for purchase order receiving information when a replenishment card from this loop is recorded in Kanban Fill/Receive. This value defaults from Kanban Control.

When the field is Yes, the system displays optional data-entry fields for a receiving note and packing slip number when the card is recorded.

Specify whether the system prompts for a lot number and reference when a replenishment card from this loop is recorded in Kanban Fill/Receive. This value defaults from Kanban Control.

When the field is Yes, the system displays optional data-entry fields for a lot number and reference when the card is recorded.

Set this field to Yes to allow the process loop to process as a repetitive backflush transaction. When this is No, the system uses unplanned receipt logic.

The system displays the value set in Supermarket Maintenance.

Enter the code representing the location where inventory is stored for this loop. This defaults from Supermarket Maintenance, if a location is specified.

When Modify Inv Data is No, Kanban Fill/Receive automatically uses this as the receipt location. When that field is Yes, this value displays as the default in the Receipt Location field in Kanban Fill/Receive. You can change it.

The system validates this field based on the Automatic Locations setting in Site Maintenance:

Specify whether users can update default values when recording kanban fill/receive or ship transactions for this loop. This value defaults from Kanban Control.

Specify the maximum percentage of the kanban quantity that is considered an acceptable difference between the kanban quantity and the quantity actually recorded in Kanban Fill/Receive or Kanban Ship.

This value defaults from Kanban Control.

Specify the cumulative difference between the expected total receipt quantity (based on the number of times a card was received and the kanban quantity) and the actual receipts.

For new loop records, this field defaults to 0 (zero). Each time a card is recorded in Kanban Fill/Receive, the system determines if the quantity received is different from the kanban quantity. If so, the difference is applied to this field:

This field is updated automatically only when Modify Inv Data is Yes. Otherwise, the amount received is automatically set to the kanban quantity, so differences do not occur.

The system uses this value when you run Kanban Card Management function 7, Process Accumulated Shortfall, which lets you create new limited-use cards to compensate for cumulative shortages. See Process Accumulated Shortfall for information on this feature.

Specify whether sequence enforcement and automatic card print values for this loop are determined by Kanban Control or by Kanban Master Maintenance.

Use these fields to specify the level of sequence enforcement associated with each kanban transaction event for this loop. Values default from Kanban Control.

Valid values for both move card transactions and most replenishment card transactions are:

The Repl FIFO field applies only to loops that are supplied by FIFO processes. It includes additional options that let you control whether warning or error messages apply only to the first FIFO process in the loop or to all FIFO processes.

Use each field to specify whether you reprint cards after they are recorded using the associated transaction. When it is Yes, recording the card sets the Auto Print field in the card detail record to Yes. When you run Kanban Multi-Card Print (17.3.5), you can control whether the system includes these cards in the selection.