About Engine Processing

QAD 2017 Enterprise Edition > User Guides > Warehousing > Engine Processing > About Engine Processing

QAD Warehousing lets you use software routines, or engines, to process transactions within a warehouse. The system creates engine workfiles—requests for a transaction—when processing warehouse tasks, such as picking and put-away. You can use the engines to process engine workfiles in the Engine menu (4.7). The engine workfiles are always in use, though, in QAD Warehousing, whether you choose not to process them with the engines.

Programs in the Engine menu let you process different time-consuming functions and decrease user waiting by running the processes in the background. You can use the programs to delay the creation of warehouse transactions, select and modify engine workfiles, and process engine workfiles singularly or in batch mode.

Engine workfiles have two different modes: AUTO and MANUAL. When in AUTO mode, the system processes engine workfiles automatically without user intervention. This is the most common use. When in MANUAL mode, you must start one of the engine processor programs in the Engine menu to process an engine workfile request. Engine workfiles can be any of the following requests:

• Create a task, including the put-away logic when applicable.

• Start the picking logic and create a picking task.

• Confirm a task.

• Print a tag.

See AUTO and MANUAL Mode Processing.

Note: Warehouse staff typically print tags during task creation, confirmation, exception processing, or when they need an ID tag.

You can modify engine workfiles using the following engine workfile programs:

• Engine Workfile by Order Maint (4.7.13)

• Engine Workfile by Date Maint (4.7.14)

See here.

You use the following engine processor programs to process engine workfiles:

• Engine Processor – Order Display (4.7.9)

• Engine Processor – Date Display (4.7.10)

• Engine Processor – Lot/Serial Ref (4.7.11)

See here.

Use Transaction Type (4.7.1) and Warehouse Transaction Type Maintenance (4.7.5) to define fields related to consolidating similar records—such as the receipt of two separate shipments of the same item, which could be consolidated into a single put-away. You can also specify whether the controls that allow overpicking should have priority at the storage location group level or at the transaction type level.

Warehouse Transaction Type Maintenance (4.7.5) lets you set up values for the same fields as Transaction Type Maintenance, but relating only to a specified warehouse at a specified site. At the warehouse level, you can also set values for picking level fields related to the transaction type.