Example of Tactic Product Conditions
Here are a few scenarios in which the system creates conditions.
Required Editions
Available in: Lightning Experience Available in: Enterprise and Unlimited Editions where Consumer Goods Cloud is enabled |
Condition Creation without Time Constraint (Condition Change Rule = Update)
Consider this data for Customer ABC:
| Object | Valid From | Valid Thru | Configuration |
|---|---|---|---|
| KPI Definition | — | — |
|
| Sales Org | — | — | Enable Tactic Condition Creation = Yes |
| Promotion Template | — | — | Enable Condition Creation = Yes |
| Promotion | Oct 01, 2019 | Oct 31, 2019 | Based on the promotion template with this configuration:
|
| Tactic (assigned to the promotion) | Oct 07, 2019 | Oct 20, 2019 | Based on the tactic template with this configuration:
Also, Condition Maintenance (tactic) = Upsert |
| Products (assigned to the promotion) | — | — |
|
- Creating Conditions: When this promotion is created with all the related information, the system creates two tactic product condition records—one for Beverages and the other for Snacks. As the time scope is Complete, the timeframe for both these conditions is the tactic timeframe (Oct 07 - Oct 20) and the corresponding values are 100 and 50 respectively. After creation, the version of the tactic product condition is set to 1.
- Updating Conditions: After condition creation, if the total value for Beverages is updated to 25, the value of the existing condition is updated to 25 and the version is set to 2 (incremented by one).
- Deleting Conditions: After the update, when the Condition Maintenance (tactic) option is set to Delete, the status of the existing condition is set to Deleted and the version is set to 3 (incremented by one).
Condition Creation with Time Constraint (Condition Change Rule = Finish)
Consider this data for Customer PQR:
| Object | Valid From | Valid Thru | Configuration |
|---|---|---|---|
| KPI Definition | — | — |
|
| Sales Org | — | — | Enable Tactic Condition Creation = Yes |
| Promotion Template | — | — | Enable Condition Creation = Yes |
| Promotion | Oct 01, 2019 | Oct 31, 2019 | Based on the promotion template with this configuration:
|
| Tactic (assigned to the promotion) | Oct 07, 2019 | Oct 20, 2019 | Based on the tactic template with this configuration:
Also, Condition Maintenance (tactic) = Upsert |
| Tactic Condition Creation Definition (TCCD record created for the tactic) | — | — |
|
| Products (assigned to the promotion) | — | — |
|
- Creating Conditions: When this promotion is created with all the related information, the
system creates two tactic product condition records with measure code ABCD—one for Beverages
and the other for Snacks. For each of these scenarios, current date is the date when the
nightly batch is launched.
- Case 1: Current date is Oct 08, 2019. Here, the timeframe for both the conditions is Oct 09, 2019 - Oct 20, 2019. Value of the condition related to Beverages is 20 and value of the condition related to Snacks is 40. As running conditions exist, the Valid From of both the conditions is set to tomorrow.
- Case 2: Current date is Oct 05, 2019. Here, the condition timeframe is equal to the tactic timeframe as the time scope is Complete. Value of the condition related to Beverages is 20 and the one related to Snacks is 40.
- Updating Conditions: After creation, if promotion is updated, then the corresponding
conditions are updated accordingly. If the total value for Beverages is 25, here’s how the
corresponding conditions are updated:
- Case 1: Current date is Oct 10, 2019. Here, the existing condition is ended today (Valid Thru = Oct 10, 2019). A new condition is created with the timeframe as Oct 11, 2019 – Oct 20, 2019. The value of this condition is updated to 25 and the version is incremented by one.
- Case 2: Current date is Oct 05, 2019. Here, the existing condition is updated with the new value as 25 and the version is incremented by one.
- Deleting Conditions: For the same promotion, if the Condition Maintenance mode of the tactic
is set to Delete, then the corresponding conditions are updated accordingly.
- Case 1: Current date is Oct 11, 2019. Here, the existing condition is ended today (Valid thru = Oct 11, 2019) and the version is incremented by one. No new conditions are created.
- Case 2: Current date is Oct 05, 2019. Here, the existing condition is updated and the status is set to Deleted. And, the version is set to increment by one as the record is updated.
Condition Creation Based on Product Assortments
Consider the following data for Customer XYZ:
| Object | Valid From | Valid Thru | Configuration |
|---|---|---|---|
| KPI Definition | — | — |
|
| Sales org | — | — |
|
| Promotion Template | — | — | Enable Condition Creation = Yes |
| Promotion | Sep 01, 2019 | Sep 30, 2019 | Based on the promotion template with this configuration:
|
| Tactic | Sep 01, 2019 | Sep 30, 2019 | Based on the tactic template with this configuration:
|
Consider a product assortment for the same customer with this data:
| Customer | Category | Products (assigned to the tactic) | Valid From | Valid Thru |
|---|---|---|---|---|
| XYZ | Beverages | A | Sep 02, 2019 | Sep 08, 2019 |
| B | Sep 16, 2019 | Sep 29, 2019 |
The image shows the tactic timeframe and the timeframe of the products that are assigned to the promotion.
Case 1: When the Condition Change Rule is set to Update, two new conditions are created—one for Product A and the other for Product B. The conditions timeframe is the same as that of the validity of the corresponding product because the product is relevant for the promotion only on the dates specified in the product assortment.
Case 2: When the Condition Change Rule is set to Finish and the current date is within the tactic timeframe, a new condition is created on Product B:
- If the current date is Sep 11, 2019, then a condition is created for Product B and the
timeframe is the same as the Product B timeframe.
Note A condition timeframe is dependent on the relevant product assortment timeframe and time scope of the corresponding tactic. No conditions are created for products for which the relevant condition timeframe is in the past. So, no conditions are created for Product A. - If the current date lies within the Product B timeframe, then the condition is created starting with the day after the current date and the Valid Thru of the condition = Valid Thru of the Product B timeframe.
Condition Creation for standard and BOM products with respect to BOM Scope and Product
Level of the Source KPI Definition
Consider the following data for Customer ABC:
| Object | Valid From | Valid Thru | Configuration |
|---|---|---|---|
| KPI Definition | — | — |
|
| Sales Org | — | — | Enable Tactic Condition Creation = Yes |
| Promotion Template | — | — | Enable Condition Creation = Yes |
| Promotion | Oct 01, 2021 | Oct 31, 2021 | Based on the promotion template with this configuration:
|
| Tactic (assigned to the promotion) | Oct 07, 2021 | Oct 20, 2021 | Based on the tactic template with this configuration:
Also, Condition Maintenance (tactic) = Upsert |
| Tactic Condition Creation Definition (TCCD record created for the tactic) | — | — |
|
Consider these products assigned to the promotion:
| Category | Products | Total Value |
|---|---|---|
| Snacks | Snacks Chocolate 6*128 (BOM Header) | 15 |
| Lopples Chocolate Wafers (BOM Component 1) | 10 | |
| Upples Chocolate Coconut (BOM Component 2) | 5 | |
| Upples Chocolate Wafers (Standard Product) | 20 |
Case 1: BOM Scope = Product and Component and Product Level = Product
- Creating Conditions: As the product level for creating condition is set to Product, the system creates tactic product condition records at Product level for standard and BOM header products, but not for BOM components. Here, the system creates only two tactic product condition records—one for the BOM header (Snacks Chocolate 6*128) and the other for the standard product (Upples Chocolate Wafers). As the time scope is Complete, the timeframe for both these conditions is the tactic timeframe (Oct 07 - Oct 20) and the corresponding values are 15 and 20 respectively. After condition creation, the version of the tactic product condition is set to 1.
- Updating Conditions: After condition creation, if the total value for Snacks Chocolate 6*128 is updated to 20, the value of the existing condition is updated to 20 and the version is set to 2 (incremented by one).
- Deleting Conditions: After the update, if the Condition Maintenance (tactic) option is set to Delete, the status of the existing condition is set to Deleted and the version is set to 3 (incremented by one).
Case 2: BOM Scope = Product and Component and Product Level = Component
- Creating Conditions: As the product level for creating condition is set to Component, the system creates tactic product conditions for standard products and BOM components, but not for BOM headers. In this case, the system creates three tactic product condition records—one for the BOM component 1 (Lopples Chocolate Wafers), one for the BOM component 2 (Upples Chocolate Coconut), and one for the standard product (Upples Chocolate Wafers). As the time scope is Complete, the timeframe for all these conditions is the tactic timeframe (Oct 07 - Oct 20) and the corresponding values are 10, 5, and 20 respectively. After condition creation, the version of the tactic product condition is set to 1.
- Updating Conditions: After condition creation, if the total value for Snacks Chocolate 6*128 is updated to 15, the value of the existing condition is updated to 15 and the version is set to 2 (incremented by one).
- Deleting Conditions: After the update, if the Condition Maintenance (tactic) option is set to Delete, the status of the existing condition is set to Deleted and the version is set to 3 (incremented by one).
Did this article solve your issue?
Let us know so we can improve!
