Pricing Options

This option determines if one or multiple Price Models are applied to a part during pricing evaluation.

• Yes: (default) Only the first Price Model that matches the Pricing Rule criteria to the part. If the same part is in multiple Pricing Rules, and within multiple Price Models within a rule, the Pricing Rule price value is derived from the first rule (as shown in the list of rules on the Administration page) and the first Price Model within the rule (as shown in the Linked Price Models section for the rule).
• No: All Price Models that match the Pricing Rule criteria to the part.

View Example

This pricing option determines whether to transfer Pricing Engine calculation information JSON from Price Models to Commerce line attribute calculation information _price_calculation_info.

• On - Send Price Model JSON information to Commerce.

• Off – Don't send Price Model JSON information to Commerce. *default value

  Turn this option off for better performance if you don't use this functionality in Commerce.

This option modifies the order of actions and calculation of prices. Depending on your adoption of Pricing Engine, this setting may have been set automatically and may limit which options you may choose.

• Version 1 represents the legacy pricing behavior. If you adopt CPQ Pricing Engine for pricing calculation, you should use pricing behavior Version 2 or higher.
• Version 2 runs the CPQ Pricing Engine as part of pricing calculations and provides for the following adjustments to the Invocation and Pricing flows: Main Document attributes populate before the Sub Document modify execution occurs; and Global Pricing calculations occur immediately before the execution of Formulas.
• Version 3 retains all Version 2 adjustments in addition to the following change: The Document Advanced Default BML will no longer execute when the 'Revert to Default' selection is selected for attribute(s) on the modify tab of an Action.

• Version 4 retains all Version 3 adjustments and improves commerce pricing performance. Pricing Calculation is optimized to run once in Commerce actions between Before Formula and Formula. As a result, the pricing calculation result is accessible in Formula and After Formula BML, but is not available in Before Formula BML.

Beginning in Oracle CPQ 23D, Charge Definitions can be used to categorize charges. When enabled, the Pricing administrator selects a Charge Definition first when creating a charge.

• On - Enable Charge Definitions
• Off – Disable Charge Definitions

This option enables the Pricing Engine to reference CPQ Exchange Rates to automatically convert prices from the base currency to other enabled currencies on the site. When enabled, customers only need to set the site base price currency for a product price or charge and the other enabled currencies can be automatically generated.

• On - Enable the Pricing Engine to activate automatic currency conversion from the site base currency for unspecified enabled currencies.

• Off - Disable automatic currency conversion. When no price is defined in Pricing Engine for the transaction currency, the pricing applied falls back to the previous Price Model price, Price Book price, or Part price that is available in the transaction currency. This is the legacy behavior for CPQ Pricing.

When this option is enabled, multiple charges from absolute Price List type price models are applied as a whole. In other words, CPQ will only apply equivalent charges from the last absolute Price List type price model. When this option is disabled, the charges are applied additively.

For example, two absolute price value Price Lists are applicable for a product. Price list 1 has charges A & B, price list 2 has charges B & C.

• When this option is enabled, the final charges are charges B & C.

• When the option is disable, all charges (A, B, and C) are applied.

The default value for this option is Off. If a site does not have any pricing data, the default value for this option is set to On.

When this option is enabled, a discount or markup to a charge is only applied if the target charge has been established in a previous absolute Price List type price model.

For example, part 1 has a $5 Activation charge discount, but no Activation charge has been defined.

• When this option is enabled, the $5 discount is not applied.

• When this option is disabled, a -$5 charge is applied.

The default value for this option is Off to support existing implementations. If a site does not have any pricing data, the default value for this option is set to On

When this option is enabled, pricing calculation is only executed in Commerce if the Commerce Recalculate action is active in the current Commerce Process Workflow Step. It also ensures that Commerce sub-document actions only invoke pricing immediately before Formulas for Pricing Behaviors v2 or higher.

The default value for this option is Off to support existing implementations. If a site does not have any pricing data or Advanced Price Models, the default value for this option is set to On

Complete the following steps to set pricing options.

1. Navigate to the Admin page.

2. Click Pricing Portal in the Products section.

3. Click on the Pricing Options card.

4. Click Edit.

5. Set the Apply Only the First Matching Price Model option.

   This option determines if one or multiple Price Models are applied to a product during pricing evaluation.

   • On - Only the first Price Model that matches the Pricing Rule and Price Model criteria for a product. *default value

     If the same product is in multiple Pricing Rules, and within multiple Price Models within a rule, the Pricing Rule price value is derived from the first rule (as shown in the list of rules on the Administration page) and the first Price Model within the rule (as shown in the Linked Price Models section for the rule) that applies to the product and context.

   • Off - All Price Models that match the Pricing Rule and Price Model criteria for a product are applied.

6. Select the Pricing Behavior version.

   This option modifies the order of actions and calculation of prices.

   Important: Switching from one Pricing option to another may impact existing pricing and past transactions within the system. Oracle recommends thoroughly testing the impact of the Pricing option change before implementing the change in a production environment. Once the Pricing option is changed in a production environment, returning transaction data to its previous state may require significant effort.

   Depending on your adoption of Pricing Engine, this setting may have been set automatically and may limit which options you can choose.

   • Version 1 represents the legacy pricing behavior. If you adopt CPQ Pricing Engine for pricing calculation, you should use pricing behavior Version 2 or higher.
   • Version 2 runs the CPQ Pricing Engine as part of pricing calculations and provides for the following adjustments to the Invocation and Pricing flows: Main Document attributes populate before the Sub Document modify execution occurs; and Global Pricing calculations occur immediately before the execution of Formulas.
   • Version 3 retains all Version 2 adjustments in addition to the following change: The Document Advanced Default BML will no longer execute when the 'Revert to Default' selection is selected for attribute(s) on the modify tab of an Action.

   • Version 4 retains all Version 3 adjustments and improves commerce pricing performance. Pricing Calculation is optimized to run once in Commerce actions between Before Formula and Formula. As a result, the pricing calculation result is accessible in Formula and After Formula BML, but is not available in Before Formula BML.

7. Select one of the following Charge Definition options:

   Enable Charge Definitions

   1. Set Enable Charge Definitions to On.
   2. Click Save or Update.

   3. If you have not yet defined any pricing in CPQ using the new productized Charge feature,
      
      click Proceed to complete the enabling of Charge Definitions.

      --OR—

      If you have defined Charges pricing in CPQ, complete the following:

      1. Select Generate Charge Definitions Only to automatically create the Charge Definitions from the combinations of Price Type and Charge Type that you have already used.
      2. Review and verify the Charge Definitions that have been automatically created before taking the next step.
         
         

      3. Once you are satisfied with the Charge Definitions you will be using, click Proceed and the Charge Definitions will be automatically populated on each existing pricing charge.

         

   Disable Charge Definitions

   1. Set Enable Charge Definitions to Off.

   2. Click Save or Update.

   3. Click Proceed to clear all pricing data of their Charge Definition values.

8. Set the Transfer Price Model JSON to Commerce option.

   This option determines whether to transfer Pricing Engine calculation information JSON from Price Models to Commerce line attribute calculation information _price_calculation_info.

   • On - Send Price Model JSON information to Commerce.

   • Off – Don't send Price Model JSON information to Commerce. *default value

   Turn this option off for better performance if you don't use this function in Commerce.

9. Set the Enable Currency Conversion in Pricing Engine option.

   This option enables the Pricing Engine to reference CPQ Exchange Rates to automatically convert prices from the base currency to other enabled currencies on the site.

   • On - Enable automatic currency conversion from the site base currency for unspecified enabled currencies.

     • Oracle CPQ strongly recommends that customers enable the Enable Currency Conversion in Pricing Engine option.

     • Conversion rates must be defined for each currency in which you wish to convert prices, refer to CPQ Exchange Rates.

   • Off - Disable automatic currency conversion. When no price is defined in Pricing Engine for the transaction currency, the pricing applied falls back to the previous Price Model price, Price Book price, or Part price that is available in the transaction currency. This is the legacy behavior for CPQ Pricing.

10. Set the Apply multiple charges in a price list as a whole option.

    This option determines how charges from multiple absolute Price List type price models are applied.

    as a whole. In other words, CPQ will only apply equivalent charges from the last absolute Price List type price model.

    • On - Apply multiple charges from absolute Price List type price models as a whole. Only charges from the last absolute Price List type price model are applied.

    • Off - Apply multiple charges additively. *default value

      If a site does not have any pricing data, the default value for this option is set to On.

11. Set the Apply adjustments on existing charges only option.

    • On - Only apply discounts or markups to a charge if the target charge has been established in a previous absolute Price List type price model.

    • Off - Apply discounts or markups to a charge even if a target charge has NOT been established in a previous absolute Price List type price model. *default value

      If a site does not have any pricing data, the default value for this option is set to On.

12. Set the Observe commerce process Steps for the pricing action in quoting option.

    • On - Only invoke pricing calculation Commerce if the Commerce Recalculate action is active in the current Commerce Process Workflow Step. It also ensures that Commerce sub-document actions only invoke pricing immediately before Formulas for Pricing Behaviors v2 or higher.

    • Off - Invoke pricing calculation for all Commerce main document actions. Pricing calculation is invoked even if the pricing action is disallowed in the current Commerce Process Workflow Step. *default value

      If a site does not have any pricing data or Advanced Price Models, the default value for this option is set to On.

13. Click Save or Update to save your changes, or Cancel to keep previous settings.