What it requires. A numeric literal (a rate, a price, an uplift) sits inside a pricing element formula or parameter instead of a decision table or price book reference.
Why it matters. [reasoned from platform semantics] A literal in a step lives in versioned procedure metadata: changing it is a builder-access version edit and re-activation, invisible to data governance, and duplicated copies drift silently. Finance reads one price in the catalog while the engine charges another.
How to fix it. Move the value into the decision table or price source the element should reference; the number becomes data with an audit trail.
Source. Salesforce Help: Use Pricing Elements in Pricing Procedures (semantics; mechanism reasoned)
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.