This scenario addresses a common data granularity mismatch: the Planning is done at the Parent (Anchor) level, but the Data (Base Volumes) resides at the Child (Sub Account) level.

To bridge this gap, the Promotion Template and Account P & L must be configured for Aggregation .

Select Sub Accounts on Account P & L: The Key Account Manager must essentially "opt-in" the relevant sub-accounts into the view. This tells the system which children contribute to this plan.

Calculation Mode: Sub Account Aggregation: This is the specific setting in the Promotion Template that dictates the engine's behavior. Instead of looking for a baseline volume record attached directly to the Parent Account (which doesn't exist in this scenario), the engine is instructed to look at the selected Sub Accounts, retrieve their individual baselines, and sum them up (Aggregate) to display the total at the Planning Account level.

Without this "Sub Account Aggregation" mode, the baseline at the planning level would likely show as zero because the system would default to looking for a direct match at the parent level. Option B correctly identifies the combination of UI selection (P & L) and calculation logic (Aggregation Mode) required to surface this data.

In Salesforce Consumer Goods Cloud TPM, Bill of Materials (BOM) or "Shippers" are handled through a relation object (often the Product Bill of Material or similar junction object) that links the parent BOM product to its component products. To maintain historical accuracy for past promotions while accommodating future changes (Slowly Changing Dimensions), you should not simply overwrite the existing record. Instead, the best practice is to "expire" the current relationship by setting the Valid Thru date to the day before the change. Then, create a new BOM relation record with the new quantity and a Valid From date starting on the day of the change. This ensures that calculations for historical promotions use the old quantity, while new promotions use the new quantity.

=============

The Ad-Hoc Sync feature in Consumer Goods Cloud is a critical administrative tool used to push metadata and configuration changes to the Processing Service immediately, bypassing the standard nightly batch windows. This is essential during setup or debugging (like scenario planning configuration) to verify results instantly.

To determine which objects need syncing, analyze what was changed:

New Fields & Linking: The admin created fields and updated the KPI Map . The KPI Map tells the engine how to read/write data from Salesforce fields into the calculation grid. If this isn't synced, the engine won't know the new fields exist.

Configuration: The Promotion Template was modified to include the new KPI Set. The template is the blueprint; the engine needs this new blueprint to know which KPIs to display and calculate.

Transactional Data: Promotions were created using this template. For the scenario planning to work on these specific records, the promotion instances themselves must be recognized by the processing layer.

While "Customer Extension" (Option B/C) is important for account-level attributes, the scenario specifically highlights changes to the KPI definition , Template structure , and the Promotions themselves. Therefore, the set {KPI Map, Promotion Template, Promotion} represents the specific metadata chain that must be refreshed for the calculation engine to correctly process the new scenario planning logic.

The Trade Promotion Management (TPM) lifecycle is generally cyclical, consisting of Strategic Planning, Promotion Planning/Execution, and Post-Event Analysis. The specific pain point identified in the scenario is the inability to "measure the effectiveness" of promotions. This activity falls squarely into the Post-Event Analysis phase.

During Discovery for this phase, a consultant must investigate how the client currently evaluates success. This involves identifying which Key Performance Indicators (KPIs) are necessary to determine "effectiveness"—commonly metrics like Return on Investment (ROI), Uplift Volume, Incremental Revenue, and Trade Spend Efficiency. To provide a recommendation, the consultant needs to understand what data is currently missing or difficult to access. For example, are they lacking actual shipment data from an ERP to compare against the plan? Do they lack baseline data to calculate the "lift"?

By focusing discovery on Post-Event Analysis, the consultant can ensure the solution is designed backwards from these requirements. If the system is not configured to capture the necessary "Actuals" or if the calculation engine is not set up to compute "Incremental" values vs. "Base" values, the client will never be able to measure effectiveness. Therefore, while planning is important, the measurement problem is solved by designing robust analytics and feedback loops that characterize the Post-Event Analysis phase 1111 .

A robust TPM implementation relies heavily on data that originates outside of Salesforce. The set of systems listed in Option A represents the critical "backbone" integrations required for Trade Promotion Management:

ERP (Enterprise Resource Planning): This is the source of truth for "Actuals." To settle claims and analyze promotion performance, TPM needs shipment and invoice data, which lives in the ERP.

MDM (Master Data Management) / PIM (Product Information Management): TPM requires a clean, hierarchical structure of Products and Customers. Synching this master data ensures that the "Product A" planned in Salesforce matches the "Product A" shipped by the warehouse.

Demand Planning: TPM is often the input to demand planning (providing the promotional lift), but it also consumes the Baseline Forecast (what would sell with no promotion) from Demand Planning tools to calculate accurate ROI.

While POS data (Option B) is useful for Retail Execution (checking shelf prices), it is less critical for the Trade Planning aspect compared to shipment data. Similarly, HRM (Option C) is generally irrelevant to trade promotion calculations. Therefore, Option A covers the essential data flow: Master Data (MDM/PIM) - > Baseline (Demand Planning) - > Execution/Actuals (ERP) 3333 .

Scenario Planning in TPM allows Key Account Managers to create "What-If" versions of a promotion (e.g., "What if I increase the discount to 15%?") without affecting the live plan. To facilitate this, the user interface needs to know specifically which KPIs are relevant for these experimental adjustments.

In the TPM configuration, KPI Subsets are used to group KPIs for specific UI contexts (e.g., the Volume Card, the Spend Card). For Scenario Planning, there is a specialized subset purpose, often referenced as the PromotionScenarios subset (or similarly named configuration hook depending on the specific release version, but conceptually the "Scenario" subset).

By adding the "Adjustment KPIs" (the specific metrics where users input their simulation data, like Simulated Lift % ) to this specific subset in the KPI Set , the consultant ensures that when a KAM enters "Scenario Mode," these specific fields appear and are editable. This segregates the scenario inputs from the standard operational data, allowing the calculation engine to compute the "Scenario Result" separately from the "Active Plan Result" for comparison.

To address the client's needs comprehensively:

Plan and Manage Trade Promotions: This is covered by Trade Promotion Management (TPM) .

Monitor Compliance and Offline Capabilities: This is the core function of Retail Execution (RE) , which allows field reps to check compliance (audits) in stores.

Field Service: In the Salesforce Consumer Goods Cloud architecture, Field Service (specifically the dispatcher and scheduling engines) often serves as the backend infrastructure that powers the Retail Execution visits, routing, and mobile offline capabilities.

Therefore, the combination of TPM (Planning), Field Service (Routing/Scheduling infrastructure), and Retail Execution (Compliance/Offline execution) is the correct solution set.

This scenario describes Gap Planning, a critical part of the Account Planning process (Customer Business Plan or CBP). The KAM has a "Target" (Goal) and a "Baseline" (Forecast). The difference is the "Gap."

The constraint in the question is key: "without creating incremental volume."

Incremental Volume is generated by Promotions (Tactics like price cuts or displays). Therefore, Option C (Plan sellable promotions) is incorrect because that is explicitly about driving incremental volume.

If the KAM needs to close the gap without running new promotions, they must adjust the Baseline or Base Forecast assumptions. For example, they might believe the market will grow organically, or a new product listing will drive steady sales. In Consumer Goods Cloud TPM, this is done using Adjustment KPIs directly within the Account Plan (CBP) view. By editing these adjustment fields (e.g., "Baseline Adjustment" or "Manual Forecast Override"), the KAM effectively modifies the "Base" volume prediction to match the "Target," thereby closing the gap in the plan. Option A correctly identifies this direct manipulation of the Account Plan KPIs as the method to align forecasts without resorting to trade activity.