Requesting additional clarification on the use of RATE_GEO_COST Basis Operator BETWEEN verses the use of Operators LT, LE, GT and GE.
Questions
NOTE - Detailed examples are also provided below for additional review
1) When using RATE_GEO_COST Basis Operator BETWEEN, does this include, or exclude the values entered? Asked another way, are the bookend values included in the logic when using BETWEEN?
2) Are there Operand Value relationship limitations when using the RATE_GEO_COST Basis Operator BETWEEN? Should it not be used with specific Operand Values such as Weight, Dimensional Weight and/or Volume?
SHIPMENT.WEIGHT
SHIPMENT.DIMWEIGHT
SHIPMENT.VOLUME
3) Are there specific Operand Values for which the use of BETWEEN if preferred over GE & LE?
SHIPMENT.SOURCE.POSTAL_CODE
SHIPMENT.DEST.POSTAL_CODE
SHIPMENT.STOPS.POSTAL_CODE
SHIPMENT.DISTANCE
SHIPMENT.NUMSTOPS
4) Thoughts regarding the benefits in using RATE_GEO_COST Basis Operators LT, LE, GT and GE verses BETWEEN.
4a) Within the UI the Basis Operators LT, LE, GT and GE visually display the mathematical value (per table below), which is more User friendly.
4b) Does BETWEEN include, or exclude the values entered? (question #1) Can beconfusing to Users.
RATE_GEO_COSTBasis Operators
=EQ Equal To
<LT Less Than
<=LE Less Than or Equal To
>GT Greater Than
>=GE Greater Than or Equal To
!=NE Not Equal To
BETWEEN
Detailed example below with use of RATE_GEO_COST Basis Operators with (4) Weight BreakRanges
<50 KG
50-99KG
100-200KG
>200 and less than 500 KG
Example1: Using RATE_GEO_COST Basis Operators LT, LE, GT and GE
All within a single Rate Record (RATE_GEO), but separate RATE_GEO_COST entries
RATE_GEO_COST_SEQ= 1
OPER1_GID= LE
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 50 KG
AND_OR1= (null)
OPER2_GID= (null)
LEFT_OPERAND2= (null)
LOW_VALUE2= (null)
RATE_GEO_COST_SEQ= 2
OPER1_GID= GE
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 50 KG
AND_OR1= A
OPER2_GID= LT
LEFT_OPERAND2= SHIPMENT.WEIGHT
LOW_VALUE2= 100
RATE_GEO_COST_SEQ= 3
OPER1_GID= GE
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 100 KG
AND_OR1= A
OPER2_GID= LT
LEFT_OPERAND2= SHIPMENT.WEIGHT
LOW_VALUE2= 200
RATE_GEO_COST_SEQ= 4
OPER1_GID= GE
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 200 KG
AND_OR1= A
OPER2_GID= LT
LEFT_OPERAND2= SHIPMENT.WEIGHT
LOW_VALUE2= 500
Example2: Using RATE_GEO_COST Basis Operator BETWEEN
All within a single Rate Record (RATE_GEO), but separate RATE_GEO_COST entries
RATE_GEO_COST_SEQ= 1
OPER1_GID= BETWEEN
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 0 KG
HIGH_VALUE1= 50 KG
RATE_GEO_COST_SEQ= 2
OPER1_GID= BETWEEN
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 50 KG
HIGH_VALUE1= 100 KG
RATE_GEO_COST_SEQ= 3
OPER1_GID= BETWEEN
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 100 KG
HIGH_VALUE1= 200 KG
RATE_GEO_COST_SEQ= 4
OPER1_GID= BETWEEN
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 200 KG
HIGH_VALUE1= 500 KG
Questions
NOTE - Detailed examples are also provided below for additional review
1) When using RATE_GEO_COST Basis Operator BETWEEN, does this include, or exclude the values entered? Asked another way, are the bookend values included in the logic when using BETWEEN?
2) Are there Operand Value relationship limitations when using the RATE_GEO_COST Basis Operator BETWEEN? Should it not be used with specific Operand Values such as Weight, Dimensional Weight and/or Volume?
SHIPMENT.WEIGHT
SHIPMENT.DIMWEIGHT
SHIPMENT.VOLUME
3) Are there specific Operand Values for which the use of BETWEEN if preferred over GE & LE?
SHIPMENT.SOURCE.POSTAL_CODE
SHIPMENT.DEST.POSTAL_CODE
SHIPMENT.STOPS.POSTAL_CODE
SHIPMENT.DISTANCE
SHIPMENT.NUMSTOPS
4) Thoughts regarding the benefits in using RATE_GEO_COST Basis Operators LT, LE, GT and GE verses BETWEEN.
4a) Within the UI the Basis Operators LT, LE, GT and GE visually display the mathematical value (per table below), which is more User friendly.
4b) Does BETWEEN include, or exclude the values entered? (question #1) Can beconfusing to Users.
RATE_GEO_COSTBasis Operators
=EQ Equal To
<LT Less Than
<=LE Less Than or Equal To
>GT Greater Than
>=GE Greater Than or Equal To
!=NE Not Equal To
BETWEEN
Detailed example below with use of RATE_GEO_COST Basis Operators with (4) Weight BreakRanges
<50 KG
50-99KG
100-200KG
>200 and less than 500 KG
Example1: Using RATE_GEO_COST Basis Operators LT, LE, GT and GE
All within a single Rate Record (RATE_GEO), but separate RATE_GEO_COST entries
RATE_GEO_COST_SEQ= 1
OPER1_GID= LE
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 50 KG
AND_OR1= (null)
OPER2_GID= (null)
LEFT_OPERAND2= (null)
LOW_VALUE2= (null)
RATE_GEO_COST_SEQ= 2
OPER1_GID= GE
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 50 KG
AND_OR1= A
OPER2_GID= LT
LEFT_OPERAND2= SHIPMENT.WEIGHT
LOW_VALUE2= 100
RATE_GEO_COST_SEQ= 3
OPER1_GID= GE
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 100 KG
AND_OR1= A
OPER2_GID= LT
LEFT_OPERAND2= SHIPMENT.WEIGHT
LOW_VALUE2= 200
RATE_GEO_COST_SEQ= 4
OPER1_GID= GE
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 200 KG
AND_OR1= A
OPER2_GID= LT
LEFT_OPERAND2= SHIPMENT.WEIGHT
LOW_VALUE2= 500
Example2: Using RATE_GEO_COST Basis Operator BETWEEN
All within a single Rate Record (RATE_GEO), but separate RATE_GEO_COST entries
RATE_GEO_COST_SEQ= 1
OPER1_GID= BETWEEN
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 0 KG
HIGH_VALUE1= 50 KG
RATE_GEO_COST_SEQ= 2
OPER1_GID= BETWEEN
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 50 KG
HIGH_VALUE1= 100 KG
RATE_GEO_COST_SEQ= 3
OPER1_GID= BETWEEN
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 100 KG
HIGH_VALUE1= 200 KG
RATE_GEO_COST_SEQ= 4
OPER1_GID= BETWEEN
LEFT_OPERAND1= SHIPMENT.WEIGHT
LOW_VALUE1= 200 KG
HIGH_VALUE1= 500 KG