Hi,
I have a question regarding Salesforce Revenue Lifecycle Management (RLM) pricing procedures.
I created a Procedure Plan Definition with a Rule-Based process type, which invokes a Pricing Procedure. In the pricing procedure, I configured a step to copy the value of a source field into the standard ListPrice field on the Quote Line Item.
However, the pricing procedure executes successfully, but the ListPrice field is not being updated. To verify that the pricing procedure itself is working, I replaced the target field with a custom field and tested again. In that case, the custom field was updated successfully, indicating that the pricing procedure can perform field assignments.
This leads me to believe that the standard ListPrice field may have special behaviour or system-controlled logic that prevents it from being updated directly through a pricing procedure.
Could you please clarify the following:
- Is it supported to update the standard ListPrice field using a Pricing Procedure in RLM?
- If yes, are there any additional configurations, permissions, pricing elements, procedure plan settings, or Revenue Settings that are required?
- Is the ListPrice field recalculated or overwritten by another pricing engine process after the pricing procedure executes?
- Are there any restrictions on updating system pricing fields such as ListPrice through field assignment actions?
- If direct updates to ListPrice are not supported, what is the recommended approach for setting a custom price in ListPrice field through RLM pricing logic?
Additionally, I would like to confirm my understanding of the RLM architecture. In Salesforce CPQ, we use Price Rules to implement custom pricing logic. Is it correct to consider Pricing Procedures in RLM as the equivalent replacement for CPQ Price Rules, or are there functional differences that I should be aware of?
Any guidance would be greatly appreciated.
Thank you. @Jayaprakash . #Revenue Cloud
, you cannot override the List Price. RCA does not support this feature. If there is custom pricing, use custom fields, attribute tags and assign it to NetUnitPrice.
Pricing procedure is equivalent to Price Rules. Also you can use Apex hooks for complex scenarios.
