AP-205 Consumer Goods Cloud: Trade Promotion Management Accredited Professional Questions and Answers

In the Salesforce Consumer Goods Cloud (CGC) architecture, data is split between the core Salesforce platform (where standard objects like Assortments and Products reside) and the Cloud Processing Service (the high-performance calculation engine usually hosted on Hyperforce/Heroku).

When a Key Account Manager (KAM) updates a Product Assortment in the core platform—for example, adding a new SKU to the "Summer 2025" list—this change is committed to the Salesforce database immediately. However, the TPM Planning Grid (the P & L view) and the Promotion Product Selector rely on the Processing Service to render data quickly. The Processing Service uses a cached or synchronized version of the master data to perform its complex calculations.

If the KAM immediately tries to create a promotion for the new product, it might not appear in the selector because the Processing Service is unaware of the update. Merely refreshing the screen (Option C) only reloads the UI, not the underlying data cache. Therefore, to bridge the gap between Core Salesforce and the Calculation Engine, the KAM or an automated process must Sync the changes (specifically the Assortment-Product links) to the processing service. This action pushes the new relationship into the engine's memory, making the product available for immediate promotion planning and calculation.

In a standard enterprise architecture for CPG companies, the Enterprise Resource Planning (ERP) system 3 remains the single source of truth (System of Record) for Master Data (Customers and Products).

Role of ERP: It handles the financial and logistical execution—invoicing, shipping, and fulfillment. If the product code or customer billing address is incorrect in the ERP, orders cannot be processed.

Role of TPM: Consumer Goods Cloud TPM is a consumption system for this master data. It imports Customers and Products from the ERP so that KAMs can plan promotions against them 4 .

A consultant must recommend maintaining the ERP as the system of record 5 . Trying to master this data in Salesforce (Option B) or Data Cloud (Option A) creates synchronization risks where the "Plan" in Salesforce refers to a product that doesn't exist or is priced differently in the "Execution" system (ERP), leading to failed orders and financial discrepancies.

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

In Consumer Goods Cloud TPM, funds are governed by Fund Templates. These templates define the rules of engagement for the budget, including strictness on spending limits.

The scenario describes a situation where a KAM needs to overspend (go into a negative balance) because the fund doesn't yet have enough money (common at the start of the year before rate-based accruals have built up) 10 .

To permit this, the administrator must configure the Overdraw settings on the Fund Template 11 :

Fixed Overdraw %: Defines how much a fixed fund can be overspent.

RBF Overdraw %: Defines how much a Rate-Based Fund (RBF) can be overspent.

If these are set to 0%, the system will block the promotion. By adjusting these percentages on the Fund Template (Option B), the system allows the KAM to approve the promotion even with insufficient current funds, assuming the deficit will be covered by future sales accruals. Option A is incorrect as transaction templates define the movement of money, not the balance limits. Option C is incorrect as Account Extensions hold customer attributes, not fund rules.

This question tests the understanding of Time Aggregation and Day Weighting logic within the TPM calculation engine.

Here are the variables:

Promotion Duration: December 1 to December 15 = 15 Days .

Baseline Input: 70 units per week.

Weekday Share Profile: None configured.

In Consumer Goods Cloud TPM, if no specific "Weekday Share Profile" (or "Day Weighting") is applied, the system defaults to a linear, even distribution of volume across the week.

Calculate Daily Average: A standard week has 7 days. If the weekly baseline is 70, the daily baseline is $70 / 7 = 10$ units per day.

Calculate Promotion Total: The promotion runs for 15 days.

Calculation: $15 \text{ days} \times 10 \text{ units/day} = 150 \text{ units}$.

If the system had used a specific profile (e.g., "High Weekend Sales"), the math would differ based on how many Saturdays/Sundays fell within the Dec 1–15 window. However, with "no weekday share profile," the linear calculation applies. Option B (140) would imply exactly two weeks (14 days), but the period is 15 days. Option A (100) is incorrect. Thus, 150 is the correct calculated baseline volume.

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 .

In Consumer Goods Cloud TPM, Templates are the foundational architectural element for creating executable records, including Funds, Promotions, and Tactics. You cannot create a valid Fund record without it being based on a Fund Template. The template defines the rules, anchors (e.g., Customer, Org), and characteristics of the fund. Therefore, the recommended and mandatory workflow is to configure the Fund Template first, and then instantiate the specific Fixed Funds using that template.

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

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.

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 for viewing data 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 an External 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 customer 3 .

This question focuses on the precise configuration of KPI Definitions within the Calculation Engine (Processing Services). Every KPI in TPM (like "Revenue" or "Volume") requires specific instructions on how and when to calculate.

The critical requirement in the prompt is that the calculation must occur in the "Shipment Time frame." In TPM, a promotion typically has multiple timeframes:

Placement/In-Store: When the product is on the shelf.

Shipment: When the product is delivered to the retailer (often weeks earlier).

Consumption: When the shopper buys it.

If a KPI is configured with the default time scope (often "Promotion" or "Placement"), the engine will calculate revenue based on the dates the promotion is active in the store. However, financial recognition for the manufacturer usually happens at Shipment . Therefore, to ensure the "Component-level revenue" reflects the financial reality of when goods were shipped, the Time Scope setting in the KPI configuration must be explicitly set to Shipment .

While "Object Scope" (Option A) and "BOM Scope" (Option C) control what is being calculated (the Tactic or the Component), they do not control the temporal aspect. Only the Time Scope determines the specific date range (Shipment Start to Shipment End) used for the data retrieval and calculation logic.

Funds in Trade Promotion Management represent the financial budget allocated to pay for promotional activities. In the Consumer Goods Cloud data model, Funds are inherently designed to support the commercial relationship with the retailer. Therefore, the Customer is the primary anchor.

A "Fund" is rarely just a floating pot of money for a product; it is money set aside for a specific retailer to promote specific products. The standard anchoring levels supported are:

Customer Only: A general "Trade Budget" for Walmart, usable for any product.

Customer & Product Category: A specific budget for "Walmart - Dairy". This ensures that money allocated for Dairy cannot be spent on Beverages.

Customer & Brand: A specific budget for "Walmart - Nestlé Brand".

Options B and C suggest funds anchored only to Products or Sales Orgs without the Customer dimension. While Sales Org funds (Headquarters Funds) conceptually exist, the standard operational "Trade Fund" used by KAMs is anchored to the Customer hierarchy. Option A correctly reflects the hierarchy of specificity (Broad Customer Fund - > Category Specific - > Brand Specific) used in most CPG financial models supported by the platform.

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.

Tactic Product Conditions (TPCs) are the records generated by TPM to represent the "deal" in a way that can be executed—for example, a pricing condition record sent to an ERP to apply a 10% discount.

The generation of these conditions is not free-form; it is strictly governed by the configuration of the Tactic Template .

Feasibility Constraint: You cannot simply choose to generate a condition at the "Brand" level if the Tactic was designed and configured to operate at the "SKU" level, or vice versa.

Tactic Template Configuration: When setting up a Tactic Template (e.g., "Display - Gold"), the administrator defines the Product Level (e.g., Category, Brand, Product) at which this tactic operates. The system relies on this configuration to know how to aggregate or split the data when generating the conditions.

Therefore, Option B is the correct advice. The system enforces the structure defined in the template. If the Tactic Template is configured for "Product Level" input, the conditions will be generated at the Product Level. If it is configured for "Category Level," the conditions will be generated at the Category Level. Option A is incorrect because the user cannot override the template configuration on the fly. Option C is incorrect because TPM supports conditions at higher levels (like Category) if the template is set up that way; it is not restricted only to the lowest level.

Real-Time Reporting (RTR) in Consumer Goods Cloud TPM is architected to provide exactly what its name implies: zero-latency visibility into the active planning session.

When a Key Account Manager (KAM) or consultant modifies a KPI in the Volume Planning Card (VPC) —for example, increasing the "Planned Uplift Volume"—the system triggers a recalculation within the Processing Service.

In-Memory Calculation: The engine recomputes all dependent metrics (Revenue, Spend, Profit) in memory.

Shared Context: The RTR component sits on top of this same active calculation context. It does not wait for the data to be written back to the Salesforce database, synced to CRM Analytics, or processed by a batch job.

Therefore, the moment the calculation completes (which is typically sub-second or a few seconds), the RTR view reflects the new financial reality immediately . This immediate feedback loop is crucial for "What-If" analysis, allowing users to tweak volume assumptions and instantly see the impact on the bottom line without the delay associated with traditional data warehousing or batch synchronization (Option B or C).

When conducting Discovery sessions, a consultant must tailor their approach to the audience. Executive-level stakeholders (VPs, C-Suite, Directors) are rarely concerned with the tactical nuances of button placement (User Interface - Option C) or the technical novelty of features (Benchmarks - Option B) in isolation. Their primary mandate is the financial and strategic health of the organization.

Therefore, the most critical factor is aligning the TPM solution with Strategic Objectives and ROI . Executives want to know how the system will help them grow revenue, improve trade spend efficiency (getting more sales for every dollar spent on promotions), or expand into new markets.

A consultant must frame the requirements gathering around questions like: "How do you currently measure the profitability of your trade spend?" or "What are your growth targets for the next fiscal year, and how does your current system hinder them?" By anchoring the solution recommendation in these strategic goals (Option A), the consultant ensures executive sponsorship. If the solution is technically perfect but fails to deliver the business insights required for market expansion or margin analysis, it will be deemed a failure by the executive leadership.

In Salesforce Consumer Goods Cloud TPM, the behavior of Key Performance Indicators (KPIs) within the planning grid is governed by the KPI Definition, specifically the Edit Mode property. This property dictates where and how a user can input data.

The requirement here is specific: the Key Account Manager (KAM) must provide a manual input (Writeback) for the discount, but this input is restricted to the Total column (the aggregate for the promotion duration) and must not be allowed in the weekly/periodic columns.

Edit Mode: Total (Option B): This is the correct configuration. When set to "Total," the cell in the Total column becomes editable. When the KAM enters a value (e.g., $10,000), the calculation engine automatically distributes (disaggregates) this amount across the weeks and products based on a defined reference profile (like Baseline Volume). The individual weekly cells remain read-only or are overwritten by the distribution logic, preventing the user from manually "tweaking" specific weeks which could break the distribution logic.

Edit Mode: All (Option A): This would allow editing in both the Total column and the individual weekly cells, violating the requirement.

Editable Storage Level (Option C): This defines where the data is saved in the database (e.g., at the Tactic level vs. Product level), but it does not control the UI behavior of locking the weekly columns while allowing the Total column to be edited.

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