Northern Trail Outfitters (NTO) wants to roll out the Consumer Goods Cloud TPM application to the US market. One of the key asks of the key account managers (KAMs) of the US market is that shipment dates should be preset, as the delivery period always starts 14 days prior to the in-store period and ends with the in-store period. A TPM consultant is brought in to assess the requirement and recommend a feasible solution.
What should the consultant recommend doing to meet NTO's requirements?
Answer : A
To automate the calculation of dates in Consumer Goods Cloud TPM, consultants utilize the Promotion Template, specifically the settings governing Timeframe Determination. This functionality dictates how the different date ranges of a promotion (Placement Dates, Shipment Dates, Consumption Dates) relate to one another.
The requirement here is to 'preset' shipment dates based on the in-store (Placement) period. Specifically, the shipment must start 14 daysbeforethe in-store period. This is a classic 'Anchor' and 'Offset' relationship. The In-Store Date is the 'Anchor,' and the Shipment Date is 'Derived' from it.
By configuring theTimeframe Determination Policywithin the Promotion Template, the consultant can define this logic (e.g., Shipment Start = Placement Start - 14 days). The setting'Synchronize Promotion Timeframes'(mentioned in Option A) is the trigger that ensures this logic runs automatically when the dates are changed. When a KAM selects the In-Store dates, the synchronization logic immediately calculates and populates the Shipment dates according to the policy. While Option C mentions 'Offsets' explicitly, Option A is the answer provided in the accredited exam dumps, emphasizing the configuration of thePolicyand theSynchronizationmechanism as the primary actions. The Policy itself contains the offset definitions, but the 'Synchronize' function is what enforces the alignment and presets the dates on the user interface, fulfilling the requirement for automation.
Cloud Kicks is a consumer packaged goods (CPG) organization with an in-house solution for predicting an optimized baseline for trade promotions, which should not be changed in Consumer Goods Cloud TPM.
What should a consultant recommend when integrating this in-house solution with Consumer Goods Cloud TPM?
Answer : A
Baseline Volume is the forecasted sales volume expected without any promotional activity. In the Salesforce TPM architecture, the Customer Business Plan (CBP) is the primary container for high-level volume planning and targets for the year.
When an organization has an external, sophisticated 'Optimized Baseline' engine (like an AI/ML demand planning tool), this data acts as the 'source of truth' for the year's forecast.
Integration Target:The consultant should integrate this data into theCustomer Business Plan (CBP)object. The CBP holds the weekly/monthly volume data for the account.
Data Flow:When a KAM creates a specific promotion in TPM, the promotion's calculation engine looks up the CBP to find the 'Base Volume' for the relevant weeks and products.
Read-Only Integrity:By loading it into the CBP (often into a locked or read-only KPI column within the CBP), the system ensures that the 'Optimized Baseline' remains immutable during the promotion planning process, serving as the trusted anchor for calculating 'Uplift' and 'Incremental' volume.
During user acceptance testing, key users realize that not all products that have the KAM status for at least 1 day of the promotion period (Date From - Date Thru) can be added to the promotion.
Which setting in the promotion template configuration should the TPM consultant check?
Answer : A
In Consumer Goods Cloud, Product KAM Status determines if a specific product is valid for a specific customer (e.g., 'Listed,' 'Delisted,' 'Test'). A common issue arises when a product is only active for part of a promotion's duration.
The behavior of the product selector---whether it includes or excludes these 'partially active' products---is controlled by the'Consider Product KAM Status'setting on thePromotion Template(Option A).
If configured strictly, the system might require the product to be active for theentireduration of the promotion.
If the users expect to see products that are active for 'at least 1 day,' this setting must be adjusted to apply the correct logic (e.g., 'Overlap' logic rather than 'Fully Contained' logic).
TheTimeframe Determination Policy(Option B) controls dates (Shipment vs. Consumption), not product eligibility.Product Definition Policy(Option C) handles how products are defined in the hierarchy, not their status validity5.
A beverage company wants to capture marketing activity on the day of the Super Bowl, across the country with all retailer stores and chain of outlets.
How should a consultant recommend using the promotions module?
Answer : A
In the Salesforce Consumer Goods Cloud TPM architecture, a Mega Event (often referred to as an 'Event' or 'Campaign' object in the hierarchy) serves as a high-level container designed specifically for this use case.
When a marketing activity is tied to a specificOccasion---like the Super Bowl, Christmas, or Black Friday---that spans across multiple different retailers, geographies, and accounts, creating individual, disconnected promotions for each customer makes high-level reporting difficult. A Mega Event allows the manufacturer to define the 'Super Bowl Campaign' once at the top level.
Individual trade promotions for specific retailers (e.g., a 'Super Bowl Promo for Walmart' and a 'Super Bowl Promo for Target') are then linked as child objects to this parent Mega Event. This structure provides two critical benefits:
Aggregation:The system can roll up the volume, spend, and profit from all the child promotions into the Mega Event, giving the beverage company a 'Total Super Bowl Performance' view instantly.
Top-Down Planning: The headquarters can define the strategic guidelines and total budget for the occasion in the Mega Event, which then guides the Key Account Managers (KAMs) as they execute the specific deals.
Option B (Customer Sets) is a mechanism for grouping stores for a single promotion, but it does not inherently solve the 'Occasion' tracking across the entire country and different distinct retail chains as effectively as the Mega Event structure.
A key account manager (KAM) at Cloud Kicks wants to set up Customer Business Plans (CBPs) for a Planning Customer. The KAM wants to create a CBP for next year.
How should a consultant advise the KAM to set up the CBP?
Answer : B
Customer Business Plans (CBPs) in Consumer Goods Cloud are the high-level containers used for annual volume and financial planning. Unlike specific promotions which have granular start and end dates (e.g., 'Jan 1st to Jan 14th'), a Customer Business Plan is structurally designed to cover a standard fiscal or calendar year.
The recommended and standard best practice for setting up a CBP is to link it to aBusiness Year. When configuring the system, the administrator defines the Calendar and Business Years (e.g., 2024, 2025) in the master data. When a Key Account Manager (KAM) creates a new plan, they select the specificYearfrom a dropdown menu rather than manually entering a 'Date From' and 'Date Thru.'
This approach ensures data integrity and alignment with the corporate fiscal calendar. By selecting 'Business Year: 2025,' the system automatically understands the exact start and end dates based on the master calendar configuration (which might be Jan 1--Dec 31, or a fiscal offset like Oct 1--Sept 30). This prevents user error, such as a KAM accidentally creating a plan that runs for 13 months or starts on the wrong day of the week. It also facilitates 'Year-over-Year' reporting, as the system can easily compare 'CBP 2024' vs. 'CBP 2025' because they are strictly defined by the Business Year object, ensuring that targets and baselines are aggregated into the correct annual buckets.
=============
Northern Trail Outfitters wants to send email to approvers, when the key account manager (KAM) is not able to approve promotions due to a threshold limitation of plan spend being more than US$50,000.
How should a consultant configure this scenario, when promotion plan spend is more than $50,000?
Answer : B
This requirement describes a conditional approval workflow. In Consumer Goods Cloud TPM, the lifecycle of a promotion (Draft -> Submitted -> Approved) is governed by the Workflow engine (State Machine).
When a KAM attempts to approve a promotion that exceeds a spending limit (e.g., >$50k), the system must prevent immediate approval and instead route it for review. This is handled by aState Transition.
Transition Logic:You define a transition from 'Draft' to 'Submitted for Approval' (or a specific review status) that triggersonlywhen the condition Plan Spend > 50,000 is met.
Workflow Action:Attached to this specific transition is anAction. In this case, the action is to 'Send Email.'
Therefore, Option B is the correct configuration. You configure theWorkflow State Transitionto detect the threshold and automatically trigger theEmail Actionto the approver. Option A (Validation Action) is typically used toblockan action entirely (e.g., 'Error: You cannot save this promotion'), which wouldn't facilitate the routing process to the approver. Option C (API) is a custom development approach that is unnecessary given the standard Workflow functionality.
Cloud Kicks (CK) has decided to extend its existing Salesforce solution by implementing Consumer Goods Cloud TPM. CK has started a discovery workshop and, due to a multi cloud solution, wants to have specific security requirements to limit users' access to certain customers and products. Customer and product accessibility should be set by selecting specific combinations of elements, and also by using the customer and product hierarchy.
How should a consultant meet these requirements?
Answer : A
Security in Consumer Goods Cloud TPM operates on two layers: the standard Salesforce record access (Sharing Rules) and the application-specific TPM User Settings.
For the complex requirement of 'selecting specific combinations of elements' (e.g., User A handles 'Beverages' for 'Walmart' but only 'Snacks' for 'Target'), standard Salesforce Sharing Rules are often too blunt or require excessive maintenance. TPM addresses this viaUser Settings.
In the TPM application configuration, you can defineManaged AccountsandManaged Productsfor each user or user profile. This acts as a filter for the Planning Grid (P&L view). When a Key Account Manager (KAM) logs in, the system checks these User Settings to determine which part of the massive Product x Customer hierarchy to load into their view. This ensures they only see and plan for the specific intersection of Customers and Categories they are responsible for. Option A correctly identifies this mechanism ('User settings') as the standard and intended way to handle this granular, matrix-based responsibility assignment within the TPM module, rather than relying solely on broad Platform security or Permission Sets.