Page History

...

1. Click to apply or not apply Additional Handling.
2. From the drop-down list, select a Handling Matrix Name that was set-up in Handling Time.

3. Click one of the Determinant Type options to set the determinant type to either Travel or Work.
   
   

   Info
   title Info
   Travel Determinants cannot be set to apply based on a specific set of conditions. These are used to hard-code a specific assignment Start, End, and Drop locations. Travel Determinants must be configured as Assignment Level.

4. If Determinant Type is set to Travel, specify the Start Location, End Location and Drop Location from their respective lists.
5. To specify the standard time for this determinant, enter a function into the Work Time Function text box. The function entered may be a simple constant value, or an algebraic expression.

   1. For expressions, you can use fields as variables. Click 'Insert a Field' link and a popup screen appears. Click a WMS Import field link, which is then populated in the Work Time Function field.
      
      
      ^{Fig.2 Determinant - Work Time Function}

       

      Info
      title Info
      While saving, the system validates the work time function. When Work Time Function is defined it is necessary to list the fields within double quotations “ “, without which the formula will not be valid. The expression may be built using addition,subtraction, division, or multiplication operators: + - / * Also, parentheses may be used to specify order of operations: ( ). The total length of the work time function cannot exceed 80 characters. The formula can be an expression much like that used in Excel. Example: (“Quantity” * “Unit Weight”) * .0006 The formulas can generate a negative number if time needs to be reduced due to a specific task not being preformed on this specific assignment. Example: “Quantity” * -1.234 Total standard time for one assignment is 35,791 minutes (assume employee works eight-hour day this would allow 74 employees to work the same assignment). ProTrack Warehouse stores STD time in milliseconds and the max integer field in SQL Server 2005 is 2,147,483,647.

6. To add a condition to a determinant, click the 'Condition' tab. the screen appears with the Select Condition link and a blank ‘condition’ list.
   
   
   ^{Fig.3 Determinant - Conditions}

    

7. You can add the determinant conditions by clicking 'Select Condition' link.
   
   
   ^{Fig.4 Determinant - Selecting Conditions}

    

8. Select the check box of the individual Field Name.
   
   
   ^{Fig.5 Determinant - Selecting Fields}

    

9. Click  and the selected fields will be listed in the ‘Conditions’ list section of the Determinants screen.
   
   
   ^{Fig.6 Determinant - Conditions}

    

10. You can change the Condition Type for each Determinant Condition by selecting from the list.

• A specific Field Value is required for comparison when the Condition Type is:
  
  

  Condition Type	Description
  Equal To	Every time the field name’s value matches the field value, this condition is true.
  Greater Than or Equal To	Every time the field name’s value is greater than or equal to the field value, this condition is true.
  Greater Than	Every time the field name’s value is greater than the field value, this condition is true.
  Less Than or Equal To	Every time the field name’s value is less than or equal to the field value, this condition is true.
  Less Than	Every time the field name’s value is less than the field value, this condition is true.
  Not Equal To	Every time the field name’s value is not equal to the field value, this condition is true.
  On Change	Compares the current task line value of the field selected to the previous task line value and when the values are not the same, this condition is true.

  ^{Table 3. Condition Type Descriptions}

  Info
  title Info
  The comparison is looking for an exact “case sensitive” match when alpha characters are used. Greater Than, Greater Than or Equal, Less Than, or Less Than or Equal conditions must be used on numeric fields. Example: Cannot compare Greater Than “C”. On Change

...

• conditions only applies within the same assignment, and thus cannot be used to trigger a determinant between assignments. When more than one condition is included in the same determinant, then all conditions must return true or the determinant will not apply. The “and” is implied between conditions.

  
  The following table lists all possible outcomes of the various Determinant Condition Types based on the type of data in the two fields being compared:

  Determinant Condition Type	Value Sent in WMS File Task Field	Value Configured in Determinant	Functional Outcome
  Equal To	numeric	numeric	both values are treated as numeric and evaluated accordingly
  	numeric	varchar	WMSFileFieldValue is converted to varchar and then expression is evaluated
  	varchar	numeric	DetFieldValue is converted to varchar and then expression is evaluated
  	varchar	varchar	Expression is evaluated
  	numeric	no value	both values are converted to varchar and then expression is evaluated as FALSE
  	varchar	no value	DetFieldValue is converted to varchar and then expression is evaluated as FALSE
  	no value	numeric	both values are converted to varchar and then expression is evaluated as FALSE
  	no value	varchar	WMSFileFieldValue is converted to varchar and then expression is evaluated as FALSE
  	no value	no value	both values are converted to varchar and then expression is evaluated as TRUE
  Not Equal To	numeric	numeric	both values are treated as numeric and evaluated accordingly
  	numeric	varchar	WMSFileFieldValue is converted to varchar and then expression is evaluated
  	varchar	numeric	DetFieldValue is converted to varchar and then expression is evaluated
  	varchar	varchar	Expression is evaluated
  	numeric	no value	both values are converted to varchar and then expression is evaluated as TRUE
  	varchar	no value	DetFieldValue is converted to varchar and then expression is evaluated as TRUE
  	no value	numeric	both values are converted to varchar and then expression is evaluated as TRUE
  	no value	varchar	WMSFileFieldValue is converted to varchar and then expression is evaluated as TRUE
  	no value	no value	both values are converted to varchar and then expression is evaluated as FALSE
  Less Than	numeric	numeric	both values are treated as numeric and evaluated accordingly
  	numeric	varchar	WMSFileFieldValue is converted to varchar and then expression is evaluated
  	varchar	numeric	DetFieldValue is converted to varchar and then expression is evaluated
  	varchar	varchar	Expression is evaluated
  	numeric	no value	always evaluated as FALSE
  	varchar	no value	always evaluated as FALSE
  	no value	numeric	always evaluated as FALSE, forced (would be TRUE)
  	no value	varchar	always evaluated as FALSE, forced (would be TRUE)
  	no value	no value	always evaluated as FALSE
  Less Than or Equal To	numeric	numeric	both values are treated as numeric and evaluated accordingly
  	numeric	varchar	WMSFileFieldValue is converted to varchar and then expression is evaluated
  	varchar	numeric	DetFieldValue is converted to varchar and then expression is evaluated
  	varchar	varchar	Expression is evaluated
  	numeric	no value	always evaluated as FALSE
  	varchar	no value	always evaluated as FALSE
  	no value	numeric	always evaluated as FALSE, forced (would be TRUE)
  	no value	varchar	always evaluated as FALSE, forced (would be TRUE)
  	no value	no value	always evaluated as FALSE
  Greater Than	numeric	numeric	both values are treated as numeric and evaluated accordingly
  	numeric	varchar	WMSFileFieldValue is converted to varchar and then expression is evaluated
  	varchar	numeric	DetFieldValue is converted to varchar and then expression is evaluated
  	varchar	varchar	Expression is evaluated
  	numeric	no value	always evaluated as TRUE
  	varchar	no value	always evaluated as TRUE
  	no value	numeric	always evaluated as FALSE
  	no value	varchar	always evaluated as FALSE
  	no value	no value	always evaluated as FALSE
  Greater Than or Equal To	numeric	numeric	both values are treated as numeric and evaluated accordingly
  	numeric	varchar	WMSFileFieldValue is converted to varchar and then expression is evaluated
  	varchar	numeric	DetFieldValue is converted to varchar and then expression is evaluated
  	varchar	varchar	Expression is evaluated
  	numeric	no value	always evaluated as TRUE
  	varchar	no value	always evaluated as TRUE
  	no value	numeric	always evaluated as FALSE
  	no value	varchar	always evaluated as FALSE
  	no value	no value	both values are converted to varchar and then expression is evaluated as TRUE
  ON CHANGE	Current

...

Next TaskValue

• Task Value

  no value

  compares current task line value to previous task line value within the same assignment  if they do not match then the logic is evaluated as TRUE if they do match then the logic is evaluated as FALSE *first task line will be evaluated as FALSE (nothing to compare), therefore determinant will not fire

...

• ^{Table 4. Condition Scenarios}
   

1. Click  to save create the new determinant.

   Info
   title Info
   To delete the Determinant Condition in the Condition Tab, select the corresponding Delete Checkboxes and click .

...