Legit AP-205 Exam Download

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.

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.

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

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.

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 Subsetsare 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 thePromotionScenariossubset (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, likeSimulated Lift %) to this specific subset in theKPI 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.