Defining Conditions

Certain conditions may affect how long it takes to complete a specific task type. For example, the rack level where inventory is located may affect how long it takes to pick material. You can account for these types of situations by creating condition records.

You can specify conditions when you:

• Assign a sub-element to an element.
• Add an element to an operation.
• Use Operation Chooser to assign operations to WMS tasks.

After you create new conditions, the system creates the reverse condition statement, which is referred to as a NOT condition, and makes the reverse condition statement available for use. After you assign conditions to elements, operations, and operation choosers, you can select a standard Condition or the Not Condition.

If the data you want to set a condition on is not available in the request from WM to Labor, you can create a user-definable field to pass the information to the labor engine. To add a user-definable field, a SQL statement must be added in WM to retrieve the data. When the labor request is made, the statement is run and the data is passed in a user-definable field. Conditions can be configured in Labor to inspect the user-definable fields and determine if additional operations/elements/subelements should be added to the labor standard.

For example, if the labor standard value should be dependent on the carrier for the shipment order, the select statement queries the carrier from the shipment order. It is passed in the Labor request. A condition is created against the user-definable field that checks for the appropriate carrier and adds in the appropriate subelement times needed for that carrier.