Priority lines by operational application

Use the Priority lines by operational application form to define the individual steps of the flexible search path for the selected application. These steps are defined as priority lines.

For each priority line, define the variables that may determine the result of the search path. You can only use the predefined variables for the selected application.

Tips

• When building a flexible search path, you are recommended to give the exceptions the highest priority levels. The highest priority is '1'.
• To deactivate a priority line temporarily, clear the Active check box. To re-activate the line within the search path, just select the Active check box.
• You can define pricing scales by adding 'Quantity' as a variable to a priority line.
• Priority lines can only be deleted if their underlying Priority line values form no longer contains any variables or values.
• At least one variable must be specified for each line,
• and a maximum of ten variables can be used. These variables can be seen as the key variables of your 'own table' within the flexible search path.

Example

You are creating a flexible search path to determine the commercial price. On the first priority line, enter the variables 'Customer' and 'Date'. On the second priority line, enter the variables 'Customer group' and 'Date'.

If a price has been filled in for the customer and date entered on a sales order (a value on the priority lines), then that price is the search path result. If no price has been filled in for the customer and date, the second priority line will be checked. If the customer specified in the sales order is a member of a customer group for which a price has been entered that is valid on the specified date, then that price is the search path result. If no price is found, the third priority line will checked, and so on.

If, after all levels have been checked, the search path still has not returned a valid result, the value specified on the Output fields by application form will be used.