Download PDF
Download page Configuring Asset-Based Pricing without Workflow Rules.
Configuring Asset-Based Pricing without Workflow Rules
Using a workflow rule to obtain the price of an asset during Asset-based operations has certain limitations. You could use workflow rules to fetch asset pricing on quantity and term updates but the process gets complicated when it involves attribute or other field changes.
Asset pricing without workflow rules helps you pick the selling price of an asset or its new price from the Price List item as and when needed.
With this feature, you can choose to
- Retain the asset price on the cart (default asset price)
- Go back to the Price List Item and fetch the new price of the asset. This happens when the parameters driving pricing undergo change.
Configuration
To turn ON Asset-based pricing without creating a workflow rule, you must configure the following two parameters:
- Default Asset Pricing Indicator: When checked, the system loads the asset price by default in the cart and monitors the changes done to fields added in the Asset Pricing Criteria.
Go to Custom Settings > Config System Properties to turn ON the pricing indicator. - Criteria Field Names: Enter the API name of the field like Quantity or attribute that drives pricing.
Go to Custom Settings > Config Asset Pricing Criteria Fields to provide the field APIs. Any changes to the fields specified here will trigger the flip and you will see the price from PLI on the cart. If you revert the update, the price will change to the default asset price.
- If the default asset pricing indicator is off, then no asset pricing criteria should be defined.
- Asset pricing is always turned on if there asset pricing criteria defined.
- Asset pricing indicator is at a global level. You can turn off asset pricing from the custom setting Config Asset Pricing Default based on asset line status on the cart load.
In the CPQ Admin UI, you can use PAV extension fields to create asset pricing criteria. Criteria fields can use attributes only from the out-of-the-box product attribute value (PAV) extension objects. CPQ does not support custom PAV extension objects.
Use Case 1
1. Create a product ‘B’ with tiered pricing. The per unit price of the product is $1200.
2. Ensure Default Asset Pricing Indicator is set to True.
3. Create a Quote with one unit of product ‘B’ for 1200. Offer a discount of $200 to see that the price of asset ‘B’ now becomes $1000.
4. Navigate to Setup > Develop > Custom Settings > Config Asset Pricing Criteria Fields. The Config Asset Pricing Criteria Fields page is displayed.
5. Click New. The Config Asset Pricing Criteria Fields Edit page is displayed.
6. In the Name field, enter a name for the asset pricing criteria.
7. In the Criteria Field Names, enter Apttus_Config2__Quantity__c (API name of the Quantity field).
8. Keep the Line Status field blank.
9. From the CSR flow, select this asset ‘B’ and perform the ABO operation of Change. You will see the asset price of $1000 on the cart.
10. Change the Quantity to ‘5’ and you will see that asset price is now set to $1200 (from the PLI).
Use Case 2
1. Create a product ‘B’ with tiered pricing. The per unit price of the product is $1200.
2. Ensure Default Asset Pricing Indicator is set to True.
3. Create a Quote with one unit of product ‘B’ for 1200. Offer a discount of $200 to see that the price of asset ‘B’ now becomes $1000.
4. Navigate to Setup > Develop > Custom Settings > Config Asset Pricing Criteria Fields. The Config Asset Pricing Criteria Fields page is displayed.
5. Click New. The Config Asset Pricing Criteria Fields Edit page is displayed.
6. In the Name field, enter a name for the asset pricing criteria.
7. In the Criteria Field Names, enter Apttus_Config2__Quantity__c (API name of the Quantity field).
8. In the Line Status field, enter Renewed.
9. From the CSR flow, select this asset ‘B’ and perform the ABO operation of Change. You will see the asset price of $1000 on the cart.
10. Ensure that the line status changes to Renewed.
10. Change the Quantity to ‘5’ and you will see that the asset price is still $1000.
The asset pricing criteria works for change in quantity, but the asset pricing criteria does not work for Renewed. Though you change quantity, you will still see the asset pricing.
Standalone Asset - Quantity Update
Similar to the above use-case, the parameter Quantity drives pricing in the following case.
Standalone Asset | Asset pricing Enabled | Base Price | Quantity | Term | Extended Price | Discount | Net Price | Asset Net Unit Price (Net price |
|---|---|---|---|---|---|---|---|---|
Initial Sale | N/A | 100 | 2 | 12 | 2400 | 350 | 2050 | 85.416 |
On load of the Cart | True | 85.416 (fetched from Asset Line Item) | 2 | 12 | 2050 | 2050 | ||
On Change (asset) | True | 85.416 (fetched from Asset Line Item) | 4 | 12 | 4100 | 100 | 4000 | 83.333 |
Standalone Asset - Quantity Update
The Attribute Service Level type Gold has the price $100 and type Platinum $200. The Asset price will change based on the changes made to Service Level attribute.
Standalone Asset | Attribute (Service Level) | Base Price | Quantity | Term | Extended Price | Discount | Net Price | Asset Net Unit Price (Net price |
|---|---|---|---|---|---|---|---|---|
Initial Sale | Gold | 100 | 2 | 12 | 2400 | 350 | 2050 | 85.416 |
On load of the Cart | Gold | 85.416 (fetched from Asset Line Item) | 2 | 12 | 2050 | 2050 | ||
On Change (asset) | Platinum | 200 (fetched from Price List Item) | 2 | 12 | 4800 | 100 | 4700 | 195.8333 |