Pricing Rules

A price rule defines the conditions that the transaction must meet for the adjustments to apply. The price rule consists of one or more price conditions and one or more price formulas. The price condition defines the set of circumstances that make a price rule applicable to a transaction. The price formula defines the actions that take place when the pricing conditions are met.

Price Rule Conditions

You can enter the conditions for the price rule in either basic or advanced mode. Basic mode enables you to create price rules using the AND operator. Advanced mode enables you to create more complex conditions. You can use the OR operator as well as the AND operator. Advanced mode enables you to enter the values for the price-by fields directly without going through the search or prompt page for the field. It also enables you to build complex conditions by using other conditions that are already defined for the rule. Advanced mode is the default setting for the page.

This is the process for entering a price rule condition in basic mode:

1. For a new price rule, select a transaction.

   This transaction determines the valid price-by field names that are available for the conditions.

   Note:

   In PeopleSoft CRM installations, the field appears by default and is unavailable for entry.

2. Change the default status from Pending to Deployed, Inactive, or Ready to Test.

   Term	Definition
   Pending:	Price rule is incomplete. Price rule validation is not performed when you save the rule.
   Deployed:	Price rule is available for use in price calculations.
   Ready to Test:	Price rule is complete. The price rule is available for use in the simulator, but not for price calculations.
   Inactive:	Price rule is not active. The rule is not available for any price calculations. Use to inactivate a rule that was previously in use.

3. Enter a description for the price rule.

   This is a free-form text field.

4. Enter a short description.

   A truncated version of the long description appears by default.

5. Select the child applications the price rule can be applied to, if the transaction has child applications that use its pricing data.

6. Select a field name in the Rule Conditions group box.

   Enter multiple field names by inserting a new row for each field name. In Basic mode, the system automatically joins the two conditions with the AND operator.

7. Click the Search button to select values for the field names.

   When you click the Search button, the system transfers you to a page from which you can search for and select values for the field name that you select. Values that are already selected for the condition automatically appear as selected. To restrict the search further, enter additional search data in the fields at the top of the page. Click the Search button, select one or more values to apply to the rule condition, and click OK.

   The condition appears in the Rule Definition group box. The rule definition based on the last condition that you built appears. Additions to the existing condition are made using the AND condition.

This is the process for entering a price rule condition in advanced mode:

1. For a new price rule, select a transaction.

   This transaction determines the valid price-by field names that are available for the conditions.

   Note:

   In PeopleSoft CRM installations, the field appears by default and is unavailable for entry.

2. Change the status from Pending to Deployed, Inactive, or Ready to Test.

   Term	Definition
   Pending:	Price rule is incomplete. Price rule validation is not performed when you save the rule.
   Deployed:	Price rule is available for use in price calculations.
   Ready to Test:	Price rule is complete and is available for use in the simulator but not for price calculations.
   Inactive:	Price rule is not active. The rule is not available for any price calculations. Use to inactivate a rule that was previously in use.

3. Enter a description for the price rule.

   This is a free-form text field.

4. Enter a short description.

   A truncated version of the long description appears by default.

5. Select the child applications the price rule can be applied to, if the transaction has child applications that use its pricing data.

6. Select a field name in the Rule Conditions group box.

   You can enter multiple field names by inserting a new row for each new field name.

7. Enter the field name values directly in the Identifier field or click the Search button.

   Enter multiple values by separating the values with commas. Alternatively, you can click the Search button. The system transfers you to a page from which you can search and select values for the field name that you select for the condition. Values that are already selected for the condition automatically appear as selected. To further restrict the search, enter additional search data at the top of the page and click the Search button. Select the fields to apply to the rule condition and click OK.

   The field name and value conditions that are defined in the Rule Conditions group box appear in the Combined Conditions group box. The individual rows in the Combined Conditions group box serve as a foundation for you to create more complex conditions.

8. Select the rows in the Combined Conditions group box that you want to use to create a more complex condition.

9. Select either the AND or the OR operator.

10. Click the Build Rule Definition button to create the advanced price rule.

    The system automatically inserts the new condition in the Combined Conditions group box.

    To create more complex conditions, selecting the new rows in the Combined Conditions group box, select an operator, and click the Build Rule Definition button until you create the desired rule definition.

Note:

The payment methods Voucher, Debit Card, and Procurement Card are not available in the order header payment method field, so price rules are not defined for those payment methods. The multiple payment method field (with those additional values) is available only at payment time.