Salesforce AP-205 - Consumer Goods Cloud: Trade Promotion Management Accredited Professional

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 theinputto demand planning (providing the promotional lift), but it also consumes theBaseline 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 theTrade Planningaspect 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.

In Salesforce Consumer Goods Cloud TPM, the KPI Set is the fundamental collection of metrics (Volume, Spend, Profit) used for calculations. While KPI Sets are assigned to templates (like a Promotion Template), the underlying calculation engine (Processing Services) aggregates these definitions at the Sales Org level to build the calculation grid.

Option A is correct because it addresses the architectural constraint: the system must generate a cohesive calculation model (often referred to as the "Big JSON" or calculation payload) that encompasses all the read, write, and calculated fields required for that Sales Org. If a consultant creates an excessive number of KPIs—or complex interdependencies across Accounts, Promotions, and Funds—this payload increases in size.

There are hard limits on the number of KPIs and columns the processing engine can handle efficiently in memory. If these limits are exceeded, users will experience significant performance degradation (slow save times, timeouts on P&L loads) or even calculation failures. Therefore, consultants must optimize the KPI Set by reusing metrics where possible and avoiding redundant definitions, ensuring the total configuration for the Sales Org fits within the platform's scalability guardrails.

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.

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

Time is a foundational dimension in Trade Promotion Management. Most organizations operate on standard Gregorian calendars (Jan 1 – Dec 31), but many, like Ursa Major Solar, utilize Fiscal Calendars (e.g., Oct 1 – Sept 30).

AStandard Calendarin Salesforce Consumer Goods Cloud is hard-coded to the Gregorian year. If UMS were to use this, "Month 1" would always be January, which contradicts their business reality where "Period 1" is October.

To support a Fiscal Year starting in October, the consultant must implement aCustom CalendarwithCustom Periods.

Custom Calendar:Defines the overall structure (Fiscal Year).

Custom Periods:Allows the administrator to explicitly define the start and end dates of every period. For example, "Period 1, 2025" is defined as "2024-10-01 to 2024-10-31".

This configuration ensures that when a KAM views a "Year to Date" report or a monthly split in the P&L, the data aggregates correctly according to the company's financial reporting cycle.

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, thePromotion TemplateandAccount P&Lmust be configured forAggregation.

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 systemwhichchildren 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, andsum 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.

To address the client's needs comprehensively:

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

Monitor Compliance and Offline Capabilities:This is the core function ofRetail 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.

While Salesforce Lightning Reports (Option C) are excellent for standard object data (Name, Slogan, Phase), they struggle to access the calculated KPIs (Volume, ROI, Spend) that reside in the Processing Service's memory or JSON blobs, unless those KPIs are explicitly written back to the database. Even with writeback, joining them in a formatted "Promotion Level Report" (often implying a tear-sheet or printable summary) can be rigid.

Real-Time Reporting (RTR)(Option A) is a UI component forviewingdata on a screen, not generating a persistent "Report" document.

Therefore, for a requirement that mixes standard metadata (Slogan, Phase) with complex calculated KPIs into a cohesive report, the recommended best practice in the TPM ecosystem is often anExternal Reporting Solution(Option B) such as CRM Analytics (Tableau CRM) or a third-party generator. These tools can ingest the Writeback data (or query the API), join it with the Promotion Object metadata, and render the pixel-perfect layout required by the customer3.

This scenario highlights a common business setup: Category Management. A large retailer (e.g., "SuperStore") is a single Customer Account, but the manufacturer has different sales reps (KAMs) for different business units—one KAM handles "Frozen Foods" and another handles "Dairy."

To support this in Consumer Goods Cloud TPM without duplicating the Customer Account (which would break master data integrity), you utilizeUser Settings.

TheUser Settingsin TPM allow you to map specificProduct Categoriesto specificUsersfor specificAccounts.

For KAM A, you configure User Settings: Account = SuperStore, Product Category = Frozen Foods.

For KAM B, you configure User Settings: Account = SuperStore, Product Category = Dairy.

When KAM A opens the promotion calendar or P&L for "SuperStore," the system filters the product list. They will only see and be able to add "Frozen Foods" to their promotions. They cannot unintentionally plan a "Dairy" promotion because those products are effectively invisible or locked to them in the planning context. This feature (Option C) perfectly isolates responsibilities while maintaining a single "SuperStore" account record, avoiding the complex data duplication suggested in Option A (creating different Sales Orgs/Divisions).