Once you activate your strategies, you can use them to calculate your Price Grids or Price Lists through the PSP. This is done in the PSP using Strategy Prioritization. It is good to have an understanding of how Dependent Price List Calculations and Dependent Price Lists and Data Fallbacks work.

Strategy Selection Table

This table contains rules that determine which strategies are calculated for which product and in what order.

1. To set the strategy’s priority, navigate to Company Parameters > StrategySelection > Add Record button (or edit the existing record).

2. In the Company Parameter Value dialog, select the desired priority order in Price Strategy #N fields. For more details, see the Prioritize Strategies (Strategy Designer) | How Prioritization Works section below.

Open

How Prioritization Works

Each product falls into one of the product segments, which are defined by the Price Setting Accelerator. In the example below, there are three product segments: Business Unit, Product Group, and Product Class. Each product has these attributes and therefore falls always within one segment.

In order to determine which rule applies, the product’s attributes are compared with the segment, and the rule with the most specific matching segment is chosen. For example, if we have a product with Business Unit = Food, Product Group = Beef, and Product Class = A, the last rule will be picked. If the product has Product Class = B, then the second from the bottom rule will be picked, and so on. If none of the rules applies, the topmost rule is picked as it covers all segments.

When a rule is determined, the Price Setting Accelerator calculates all the strategies in the left-to-right order. The final price of the calculation will be the price of the first strategy that returns a valid price.

In our example, say the product does not have a competition and the AvgCompetition strategy does not return a price, but the AttributeBased strategy and the My Cost Plus strategy do return one. In such a case, the final price will be the price of the AttributeBased strategy.

Hierarchy Levels

The items in the list of hierarchy levels are fixed and depend on how many levels you have configured in the PSP. You might have only the Default level configured, or you can have more levels. For details on how to configure this, see Dependent Price Lists and Data Fallbacks. Generally, this is configured when the PSP is deployed for the first time on the partition.

In short, you can have different settings per dependency level (or context) in which your price lists and grids are calculated. For example, you can have different settings on a Global level and Country level.

Standard vs. Override (Base) Levels

Rules defined in an Override table always take precedence over rules defined in the Standard table of the same level. Usually, the Standard tables contain rules that are not changed very frequently, and the Override tables contain rules which change a lot. An example of rules in the Override table would be a temporary promotion. Instead of rewriting your Standard Table, you can just add a rule into the Override table of the same level. If two rules with the same segment are found in both the Standard and the Override tables, the rule from the Override table takes precedence. Only if it does not return a price, the rule from the Standard table is evaluated.