Enter the default templates for the system to use when it calculates average demand and safety stock, either when you run Average Demand Calculation (17.2.1) or Safety Stock Calculation (17.2.2), or when related information is updated from a workbench program.

See Defining Demand Templates.

These values default to the supermarket item detail records for new loops in Kanban Master Maintenance (17.1.4).

This field indicates the default print setting for new kanban loop records defined in Kanban Master Maintenance (17.1.4). Enter Yes to print kanban ID barcodes on kanban cards.

To implement barcodes, you must have a barcode-capable printer. You may also need to add printer-control codes in the Bar Code Control frame in Printer Setup Maintenance (36.13.2). See QAD System Administration User Guide for details.

This field indicates the default print setting for new kanban records. Enter Yes to print item number barcodes on kanban cards.

Optionally, enter codes representing the barcode formats used outside or inside your company. For example:

This field indicates the default print setting for new kanban loop records. Enter Yes to print the kanban container quantity on each kanban card.

Specify the allowable tolerance percentage between the total amount planned to be scheduled and the total amount actually scheduled in Level Mix Workbench (17.14.1). This value defaults to the Tolerance % field in Level Mix Workbench. You can change it when you run the program. See here.

Specify the default number of calendar days into the future, starting from today, where flow scheduled orders are considered frozen and will not be automatically rescheduled by Level Mix Workbench. This value defaults to the Time Fence Days field in Level Mix Workbench. You can change it when you run the program.

When the workbench value is 0 (zero), the system does not freeze any flow schedules.

Enter Yes to activate automatic kanban card reconciliation functionality. This is also the default setting for the same field in the following programs:

When Card Reconciliation is Yes in one of those programs, the system automatically creates or modifies replenishment cards so the total of all active cards multiplied by the kanban quantity is equal to the maximum buffer size for the loop.

If reconciliation requires cards to be added, the system uses the phase-in method defined in Kanban Control to determine whether to activate any available inactive cards before creating new ones. See Phase-In Method.

If cards must be removed, the system first looks at the Decrease at Consume value specified for the loop in Kanban Master Maintenance:

For two-card loops, use Move Card Sizing to control how card reconciliation affects move cards.

See Decrease at Consume.

Specify whether you typically update the number of move cards in two-card loops in response to changes made by the automatic card-reconciliation function. This is the default setting for the same field in the following programs:

Valid values are:

If not evenly divisible, the number of move cards is rounded to the nearest whole integer value.

Optionally enter up to five reference codes related to calendar adjustments specified in Process Calendar Except Maint (17.1.14) or Process Non-Workday Update (17.l.25). The system validates entries against that program. See Set Up Process Shifts.

These fields default to Preliminary Level Schedule Report (17.14.2), Level Mix Workbench (17.14.1), and Level Mix Workbench Export (17.14.1).

Time adjustments are typically used to identify such exceptions to the standard shift calendar as holidays or irregularly scheduled meetings that cannot be accounted for by shortening the shift hours.

Optionally enter the default paths to the directories where the workbench export and import programs place output files and look for import files. You can change these directories when you export or import data. See Using External Applications.

The workbench export and import programs are typically required only if you do not use the included versions of the workbench programs. In that case, use the export programs to create comma-delimited files containing the same records provided to the workbenches. You can then manipulate the data with a custom external program, export the results to a data file, and use the associated workbench import program to load the updates into the system.

Optionally enter the default minimum EPEI for new processes defined in Kanban Process Maintenance (17.1.3). The default is 0 (zero). See EPEI.

The Kanban Control field uses decimal days. However, in Kanban Process Maintenance, the system converts the value to the units specified in the EPEI Display Option field for the process.

Specify a minimum process EPEI, for example, when you never want to set up the machines in your processes more than once each day. If the calculated EPEI is less than the specified minimum, the system uses the minimum value instead.

Specify the default method the system uses for calculating the lead time for each item produced by a kanban process. This value defaults to Kanban Process Maintenance. You can change it for individual processes.

Specify the default method used for kanban card piece reporting. This value defaults to Kanban Master Maintenance. You can change it for individual loops.

This setting affects kanban sizing calculations performed using the kanban workbenches.

Specify the percentage of the total calculated time available during the EPE interval that the system can use for planning the load on a kanban process. The default is 80%. This value defaults to Kanban Process Maintenance. You can change it for individual processes.

If the planned load for a process based on the time required for setups and the cycle time is greater than this percentage, the system displays a warning message in the workbench.

Specify the default fractional kanban percentage for new kanban loops. The default is 0 (zero). When the setting for a loop is 0 (zero), the system does not use fractional kanban logic. It cannot be greater than 99%. This value defaults to Kanban Master Maintenance. You can change it for individual loops.

When you use Kanban Sizing Workbench to size loops, the Fractional Kanban value for the loop lets you control the point at which the system increases the order quantity to provide an additional card. When both the preliminary order point and the preliminary order quantity are greater than zero but less than this percentage of the kanban quantity, the revised order quantity is set to zero. Otherwise, it is set to the revised kanban quantity, resulting in an additional card in the loop.

Specify the method used by card management and automatic reconciliation functions when adding cards to kanban loops. This is a system-wide control; all kanban loops use the value specified here.

Specify the method used by card management and automatic reconciliation functions when removing cards from kanban loops. This is a system-wide control; all kanban loops use the value specified here.

Specify whether you typically want to have cards that are no longer needed based on card management or automatic reconciliation functions removed from the loop the next time they are consumed. This is the default setting for the same field in new Kanban Master Maintenance records.

Optionally enter the identifier for the cost set used in inventory value calculations in the kanban workbenches. The default is blank. Entries are validated against records defined in Cost Set Maintenance (30.1).

Enter an optional sequence identifier used to generate the batch number assigned to cards when they are dispatched using Kanban Dispatch List Processing. This value must be defined in Number Range Maintenance (36.2.21.1) for target dataset knbd.dispatch_id.

See QAD System Administration User Guide for information on number ranges.

This field is required only if you use dispatch lists to communicate kanban demand data to source suppliers, processes, or supermarkets.

When this field is blank, Kanban Dispatch List Processing does not generate dispatch ID numbers. Although you can still generate non‑EDI dispatch lists in simulation mode by setting Update Dispatched Cards to No, the actual processing can take place only when a sequence is defined.

While creating a dispatch list using this sequence, the system stores the number as a dispatch ID associated with the cards included in that dispatch session. You can use this ID in several programs on the Kanban Dispatch Menu (17.5) to retrieve information about dispatched cards.

Enter the period of time, in seconds, to display a frame containing kanban card information during a kanban transaction session. The information frame displays for the number of seconds specified before the system prompts for the next kanban ID. The kanban information is used for verification purposes only. Enter 0 (zero) if you do not want to display the kanban information frame. See Record Kanban Transactions.

This field indicates whether the system prompts for an effective date at the beginning of a kanban transaction session. Enter Yes to allow the entry of an effective date for a kanban transaction session. Enter No to use the system date for kanban transactions.

Enter Yes to display a prompt during Kanban Ship (17.6.4) that lets you update the current FIFO process as the source of the kanban transaction. See FIFO Process Data.

This setting applies only to kanban loops that have Use FIFO set to Yes in Kanban Master Maintenance.

When this field is No, the prompt does not display during Kanban Ship. The system records the current process as the source of the transaction.

Indicate the level of control placed on kanban data entry during a kanban transaction session. Use controlled entry to mandate that selected kanban data must be the same for the duration of a kanban transaction session. For example, you can limit kanban entry to kanban cards associated with a specific supplier.

When this field is set to Warning or Error, a frame displays during a kanban transaction session allowing entry of control data. The control data is used for all transactions during that session.

Specify whether the system typically prompts for purchase order receiving information when a card is recorded in Kanban Fill/Receive. This is the default for new loop records in Kanban Master Maintenance.

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

Specify whether the system typically prompts for a lot number and reference when a card is recorded in Kanban Fill/Receive. This is the default for new loop records in Kanban Master Maintenance.

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

Specify whether users are typically allowed to update default values when recording kanban fill/receive or ship transactions. This sets the default value for new loop records in Kanban Master Maintenance.

When Modify Inventory Data is Yes for a loop, Kanban Fill/Receive and Kanban Ship display editable fields for certain kinds of inventory data. Depending on the source of the loop (supplier, inventory, process) and the transaction, fields can include:

Enabling this option lets you record receipt and shipment transactions on which the quantity processed does not have to equal the kanban quantity. For example, you can record the quantity scrapped when receiving a card for a process loop. In a similar situation, with the loop Modify Inventory Data field set to No, Kanban Fill/Receive automatically records the kanban quantity. You cannot account for scrap.

Specify the default 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 to new loop records in Kanban Master Maintenance.

When Modify Inventory Data is Yes for a loop and the user changes the actual quantity received or shipped from the default (the kanban quantity), the system calculates the difference as a percentage of the kanban quantity. If the percentage is equal to or greater than the specified threshold, a warning message displays.

When this field is 0 in the loop record, the system does not validate the quantity entered.

When recording a card for this loop in Kanban Fill/Receive, you enter 40 in the Quantity Accepted field. The system calculates the difference between this and the kanban quantity (50 – 40 = 10). It then determines the percentage of the kanban quantity represented by the difference (10 / 50 = 0.20). Since 20% is greater than the specified threshold of 10%, the system prompts you to confirm the quantity accepted.

However, if you enter 48 in Quantity Accepted, the difference is only 2 (50 – 48). This represents only 4% of the kanban quantity (2 / 50 = 0.04). Since that is less than the specified threshold, the system accepts the quantity without a warning prompt.

Specify how cards are typically managed when they are recorded in one of the programs on the Kanban Transactions Menu and the system determines that certain card and loop values are no longer identical. This is the default for new loop records in Kanban Master Maintenance.

Regeneration is required when one of the following is true:

1. Item/step records defined in Kanban Item Master Maintenance

2. Item/site detail records

3. Item master records

4. Routing and BOM codes that are the same as the item number

Indicate the level of enforcement for minimum kanban cycles. Use minimum kanban cycles to control how quickly kanban data for the same card can be entered into the system. Enforcing a minimum kanban cycle prevents the problem of inadvertently entering the same kanban card twice during a kanban transaction session.

The minimum kanban cycle is the sum of the days, hours, minutes, and seconds entered in the Minimum Cycle fields for each kanban card.

This field sets the default for new kanban loop records defined in Kanban Master Maintenance.

A minimum kanban cycle is the sum of the days, hours, minutes, and seconds entered in these fields. These fields set the default for new kanban loop records.

Maximum kanban cycle is used by Missing Kanbans Report (17.6.18) to determine whether a kanban card is misplaced. A kanban card is considered missing when the elapsed time between the last transaction for that card and the current date and time exceeds the maximum kanban cycle. See Generating Reports.

The maximum kanban cycle is the sum of the days, hours, minutes, and seconds entered in these fields. These fields are used as the default for new kanban records. A maximum kanban cycle is not enforced when a maximum cycle time is not specified.

Specify whether the system enforces the sequence in which kanban replenishment or move card transactions are recorded.

See Sequence Enforcement.

Specify the number of seconds the system pauses each time before cycling through applicable loop records when Accumulator Monitor is running. Valid values are 1 to 999. See Monitor Accumulator Quantities.

Use these fields to specify the level of sequence enforcement associated with each kanban transaction event. 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 typically 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.