Tactic Product Conditions
Tactic product conditions contain relevant detail about the corresponding tactic and products—Standard and BOM—at the configured product level. When condition creation is enabled for your sales org, promotion template, and tactic template, the system automatically creates tactic product conditions with or without any time constraint when a nightly batch is launched and specific criteria are met.
Required Editions
Available in: Lightning Experience Available in: Enterprise and Unlimited Editions where Consumer Goods Cloud is enabled |
Tactic product conditions are categorized into external and internal depending on the table in which the conditions are stored:
- External conditions: The conditions stored in the Tactic Product Condition table. The system stores all conditions in this table by default.
- Internal Conditions: The tactic product conditions that are additionally stored in the Account Product Measure table when the Condition Creation Definition Level field of the tactic template is set to Tactic and the Target field of the tactic condition creation definition record contains Internal.
Configurations for Creating Tactic Product Conditions
Depending on the condition creation definition level that’s selected in the tactic template, the system uses the configurations defined either in the tactic template or the TCCD records to create conditions for tactic products (standard and BOM). See the table for more details:
| If the Condition Creation Definition Level is set to | then | ||
|---|---|---|---|
| Tactic Template | The system uses the configurations, such as the Condition Source KPI, Condition Product Group Level, Condition Change Rule, and Additional Condition KPIs that are defined in the tactic template to create conditions in this way: | ||
| If the BOM Scope of the Condition Source KPI is set to | And Condition Product Group Level is set to | Then | |
| Product | Product | Conditions are created at the Product level for standard products. | |
| Product group | Conditions are created at the specified product-group level only. | ||
| Product and Header | Product | Conditions are created at the Product level for both standard and BOM header products. | |
| Product group | Conditions are created at the specified product-group level only. | ||
| Tactic | The system uses the configurations, such as the Source KPI Definition, Product Level, Change Rule, Measure Code, and Additional KPI Definitions that are defined in the TCCD records created for the tactics to create conditions in this way: | ||
| If the BOM Scope of the Source KPI Definition is set to | And Product Level is set to | Then | |
| Product | Product | Conditions are created at the Product level for standard products. | |
| Product group | Conditions are created at the specified product-group level only. | ||
| Product and Header | Product | Conditions are created at the Product level for both standard and BOM header products. | |
| Product group | Conditions are created at the specified product-group level only. | ||
| Header | Product | Conditions are created at the Product level for BOM header products. | |
| Product group | Conditions aren’t created. | ||
| Component | Component | Conditions are created for each BOM Component1 of the BOM header products. | |
| Product and Component | Product | Conditions are created at the Product level for both standard products and BOM header products. | |
| — | Product group | Conditions are created at the specified product-group level only. | |
| — | Component | Conditions are created for both standard products and BOM components. | |
| A BOM scope combination | None | The system automatically determines the suitable product level at which conditions are created based on the user actions. | |
Creating Tactic Product Conditions
See the different types of tactic product conditions and the criteria for creating the conditions.
Ensure that:
- For at least one active tactic, the Enable Tactic Condition Creation and Enable Condition Creation options of the corresponding sales org, promotion template, and tactic template are selected.
- The Condition Maintenance option of the tactic is set to Upsert.
- Conditions Without Time Constraint
- The system creates tactic product conditions without time constraint only when the Condition Change Rule option of the corresponding tactic template is set to Update.
- Conditions with Time Constraint
- The system creates tactic product conditions with time constraint only when the Condition Change Rule option of the corresponding tactic template is set to Finish.
The creation of conditions based on product assortments is additionally dependent on the selection of the Consider Account Product List option of the corresponding promotion template, as described in this table.
| Scenario | Description |
|---|---|
| The Consider Account Product List option of the corresponding promotion template is deselected. | The system creates tactic product conditions without time constraint only when the Condition Change Rule option of the corresponding tactic template is set to Update. |
| The Consider Account Product List option of the corresponding promotion template is deselected. | The system creates tactic product conditions with time constraint only when the Condition Change Rule option of the corresponding tactic template is set to Finish. Also the start date of the relevant tactic timeframe, considering the time scope of the condition source KPI, is greater than the current date. Or, the current date is within the time range of the relevant tactic timeframe (Date From of the tactic considering the time scope of the condition source KPI <= current date <= Date Thru of the tactic considering the time scope of the condition source KPI). |
| The Consider Account Product List of the corresponding promotion template is selected for a time-dependent sales org (Account Product List Type = Time-Dependent). | For all such tactics, the system verifies that the Condition Product Group Level of the corresponding tactic template is set to Product. Then, the system determines the products for which the time-dependent account product list timeframe overlaps with the relevant tactic timeframe, considering the time scope of the condition source KPI). The system considers the first time-dependent account product list for the determined products and creates tactic product conditions for the same. Note If the Condition Product Group
Level of the corresponding tactic template isn’t set to Product, then the conditions are
created based on the relevant tactic timeframe. |
Updating Tactic Product Conditions
The system updates the tactic product conditions with or without time constraint when one of these values is edited:
- The start and end dates of the corresponding tactic timeframe
- The time scope of the KPI definition assigned to the tactic template
- The condition source KPI or the condition product-group level of the corresponding tactic template
- The promotion phase related to the tactic
- The total value at the product-group level
For conditions with time constraint, when the condition is in the future, the value is updated with the new value. For running conditions, the system ends the condition at the current date and a new condition is created starting with the next date.
Conditions that are created based on product assortments are updated when the time-dependent account product list timeframe is updated and doesn't overlap with the relevant tactic timeframe. After the conditions are generated, only actual changes in the conditions are updated in both Tactic Product Condition and Account Product Measure tables.
Deleting Tactic Product Conditions
The system deletes the tactic product conditions with or without time constraints when one of these conditions is met:
- The Condition Maintenance option of the corresponding tactic is set to Delete.
- The corresponding tactics or products are deleted.
- The relevant timeframe (considering the time scope of the condition source KPI) is removed from the tactic.
- The total value of the level where the condition is created in the product hierarchy grid is removed.
Conditions that are created based on product assortments are deleted when:
- A product is no longer listed.
- A product is removed from the time-dependent account product list.
- The system doesn’t delete conditions for which the relevant tactic timeframe is running, that is, the Valid Thru of the conditions is set to the current date.
- When an external condition is deleted, the system sets the Status field of the Tactic Product Condition table to Deleted. In case of internal conditions, the conditions are deleted or removed from the Account Product Measure table.
- Example of Tactic Product Conditions
Here are a few scenarios in which the system creates conditions.

