Configuration for Condition Generation Optimization and Product Exceptions

When generating conditions, the system evaluates the entries in condition tables as follows:

The system determines the planning account when generating conditions. If the planning account is Hierarchy Node, the system expands the planning account if the condition table contains any of the following fields: Customer Number, Payer, Goods Recipient, or Invoice Recipient.
Post-evaluation of the product level depends on the settings that you have made in Customizing for Customer Relationship Management under Trade Promotion Management Trade Promotions Condition Maintenance Define Condition Generation and on data that is maintained in the Planning assignment block.
- If you specify only one Customizing entry for the product level, the system creates condition records by product.
- If you specify an entry for a higher product level (product group or product hierarchy), you can generate condition records on this higher level. In doing so, the system uses this higher level, which is in the planning layout, for key figure planning.
  - If you select the planning profile group 4TPM in the General Data assignment block, the planning layout in the Planning assignment block contains the product group level.
  - If you select the planning profile group 4TPH, the planning layout contains the product category level.
  Once you have maintained Customizing entries for the product level and for the higher product levels, the system creates condition records for the higher product levels and for those products whose values you have maintained differently.

Example Example

You have maintained condition tables for the product and the product group level for a specific condition type in Customizing. You have assigned five products, numbered 1001 to 1005, to your trade promotion; these products belong to product group PG1. You have maintained the following variable trade spends in the Planning assignment block:

Product	Trade Spend
1001	USD 2
1002	USD 2
1003	USD 1
1004	USD 2
1005	USD 2

The system creates a condition record for product group PG1 with the condition amount USD 2 and a condition record for product 1003 with the condition amount USD 1.

End of the example.

Example Example

In the second case you have maintained the following variable trade spends in the Planning assignment block:

Product	Trade Spend
1001	USD 2
1002	USD 2
1003	USD 2
1004	USD 2
1005	USD 2

The system creates a condition record for product group PG1 with the condition amount USD 2.

End of the example.

Recommendation

If you are using condition tables for the product and the product group level, we recommend that you set the condition tables in the access sequence as exclusive. You do this in Customizing for Customer Relationship Management under Master Data Conditions and Condition Technique Condition Technique: Basics Create Access Sequences .

You can assign a product group or category to a trade promotion and at the same time, assign one or more products of this product group or category to the trade promotion. You can exclude one or more products, meaning that the discount of the trade promotion is applied to all products of the product group or category except to the excluded products. You can define one or more products as exceptions, meaning that the discount of the trade promotion is the same for all products of the product group or category except for the exception products, for which you can define a different discount.

Example Example

You have assigned product group PG2 to your trade promotion. You have also assigned two products that belong to this product group, 2001 and 2002, to your trade promotion. You have excluded product 2001 and you have set product 2002 as an exception product. You have maintained the following variable trade spends:

Product Group/Product	Trade Spend
PG2	USD 2
2001	Not applicable. It is added to the Product assignment block and it is set as excluded.
2002	USD 1

The system creates a condition record for product group PG2 with the condition amount USD 2, a condition record for product 2001 with the condition amount of USD 0, and a condition record for product 2002 with the condition amount USD 1.

End of the example.

If a sales order is created that includes product 2001 or product 2002, in order not to apply both the condition record at the product level and the condition record at the product group level, you have to set the access sequence corresponding to the condition type of the condition records as described in the sections below.

Configuration of Access Sequences That Contain the Partner Level

You can make settings similar to those shown in the following table.

Access Sequence	Condition Table	Exclusive Condition Access Indicator
10	Sold-to-party/product level	Is selected
20	Sold-to-party/product category level
30	Sold-to-party/product group level
40	Hierarchy node/product level	Is selected
50	Hierarchy node/product category level
60	Hierarchy node/product group level

Configuration of Access Sequences That Do Not Contain the Partner Level

You can make settings similar to those shown in the following table.

Access Sequence	Condition Table	Exclusive Condition Access Indicator
10	Product level	Is selected
20	Product category level
30	Product group level

Configuration of Access Sequences That Contain the Target Group or the Product Segment Level

It is not possible to set tables with two multiple-value fields as exclusive. The Target Group, Product Segment, and Campaign fields are multiple-value fields. Since for short-term planning the Campaign field is always part of the pricing condition tables, any table that contains the Target Group or Product Segment field or both, will contain two or more multiple-value fields. For long term planning, the Campaign field is never part of the condition tables. However, a table that contains the Target Group and Product Segment fields will contain two multiple-value fields.

When the access sequence contains tables with two or more multiple-value fields, you cannot set the tables at the product level as exclusive. Let us assume that condition generation is optimized or you are able to use exception products while you include tables with more than one multiple-value field in the access sequences used by a trade promotion. Then, in the sales orders, two discounts will be applied, one at the product level and one at the product category or product group level. To be able to use exception products and condition generation optimization, you have to set the access sequences properly, depending on the origin of the condition rates and the planning level. For more information, see: