You are here:
Create a Pricing Search Strategy
Configure the prioritized sequence of search steps used to look up pricing conditions.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise and Unlimited Editions in Manufacturing Cloud, Automotive Cloud, and Consumer Goods Cloud, with required add-ons. |
A pricing search strategy is a set of key attribute combinations that determine pricing conditions. The search strategy assigned to a pricing specification defines how condition lookups execute from most specific (for example, customer-specific rate) to least specific (base price fallback).
-
Create the Search Strategy.
- From the App Launcher, find and select Pricing Search Strategy, and then click New.
- Enter a Name.
- Select a Context Definition.
- Optionally, search for and select an Internal Organization Unit.
- Click Save.
-
Add Search Strategy Steps.
A search strategy consists of steps processed in a defined sequence. Strategy steps link key types to the search strategy.
- Select the newly created pricing search strategy.
- Click the Expression Set Versions link to open the Business Rules Engine builder.
- In the builder, add a Pricing Search Strategy Step.
-
Provide the step configuration details:
- Pricing Key Type: Select the applicable Pricing Key Type.
- Search Sequence: Enter a numeric sequence value (for example, 10). Lower sequence numbers execute first.
- Account Role Type: Select the account role type (for example, Orderer).
- Account Hierarchy Level: Select the account hierarchy level (for example, CustLevel1).
- Product Hierarchy Level: Select the product hierarchy level (for example, ProdLevel1).
- Exclusive: Optionally check this box to indicate this step should be evaluated exclusively of other steps.
- Click Save, and then click Activate to make the search strategy available.
Note The platform doesn't validate that a Search Strategy Step's Pricing Key
Type belongs to the same Internal Organization Unit (IOU) as the Search
Strategy itself. A step can reference a Key Type scoped to a different IOU and still
save and activate without error or warning — but this can cause External Pricing Key
Value lookups to resolve against the wrong IOU, or fail to resolve at runtime. Before
saving a step, confirm the selected Pricing Key Type's IOU matches the strategy's own
IOU.
Did this article solve your issue?
Let us know so we can improve!
