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.

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

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.

Customer Business Plans (CBPs) in Consumer Goods Cloud are records that establish the targets and planning data for a specific customer and year. If the granularity of the planning needs tochange (e.g., from "Planning Customer + Category" to just "Planning Customer"), the existing CBP records can be deleted provided they are not locked by active workflows or other restrictive dependencies that strictly prevent deletion. Deleting the incorrect CBPs allows the administrator to re-upload or re-create the plans at the correct level of granularity (Planning Customer level) for both the Current Year and Next Year to meet the new business requirement.

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

In the Salesforce Consumer Goods Cloud (CGC) architecture, high-volume calculations and data processing for Trade Promotion Management (TPM) are handled by the Cloud Processing Service (CPS). This off-platform engine is necessary to manage the massive data grids involved in promotion planning.

When a System Administrator needs to interact directly with this engine—specifically to load, register, or sync external data sources (like "Sell through volume") so they can be read as KPIs—they require specific privileges that go beyond standard CRM access. TheCGC Processing Services Registerpermission set license is explicitly designed for this administrative purpose.

This license grants the user the necessary API rights and access controls to manage theData Processing Engine (DPE)definitions and trigger the synchronization jobs that hydrate the CPS with data. Without this specific license, the administrator might be able to see the TPM application screens (if they have the TPM license, Option A), but they would lack the backend permissions required to configure the data ingestion pipelines that feed the calculation engine.

In the Consumer Goods Cloud data model, the concept of "Planning Accounts" (where the plan is created) often differs from the "Execution" or "Format" level (where the volume actually occurs). A retailer might be one Planning Customer (e.g., "Global Retailer Inc."), but they operate distinct store formats like "Hypermarkets" and "Supermarkets" which have different performance characteristics.

To model this, Salesforce utilizes theCustomer Relationshipobject. This object acts as a flexible connector that links the main Planning Account to the specific Format accounts (Sub-Accounts). The correct configuration involves setting theRelationship Typeto"Sub Account".

This architecture allows the system to aggregate data. When a KAM plans a promotion for the main "Planning Account," the system needs to know which underlying stores or formats contribute to that volume. By interfacing the format data into theCustomer Relationshipobject with the "Sub Account" type, the TPM calculation engine can automatically roll up historical data (baselines) from the Supermarkets and Hypermarkets to the Planning Account level. Conversely, it allows for planning at the format level if needed. This is superior to using the standard Trade Org Hierarchy (Option A) for this specific use case because "Formats" are often virtual or logical groupings that existacrossstandard geographic hierarchies, and the Customer Relationship object provides the necessary flexibility to map these many-to-many or specific one-to-many relationships without disrupting the primary sales organization tree.

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

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 asidefor a specific retailerto 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 anchoredonlyto 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.

In Consumer Goods Cloud TPM, many KPIs (like Effective Price) are calculated "on the fly" by the processing engine in the browser or the calculation grid. They do not automatically exist as stored data records in the database that an external integration tool can simply "query."

To make a calculated KPI available for integration (extraction to an ERP or Data Warehouse), you must configureWriteback. Writeback instructs the system to physically save the calculated value into a storage table (typically the Promotion Product or a generic Measurement table) whenever the promotion is saved.

The requirement asks specifically for the value "for each product." Therefore, theStorage Levelmust be set toProduct. If it were set to "Tactic" or "Promotion," the granular product-level price data would be aggregated and lost. Once Writeback is enabled and the storage level is correct, the data exists as physical records in Salesforce objects. These can then be extracted using standard methods like theIntegration APIsorRTR CSV Extracts. Option B describes this exact configuration workflow: Enable Writeback -> Set Level to Product -> Extract via API. Option A discusses "Conditions" which is a different concept related to pricing logic, not generic KPI extraction.