Salesforce AP-213 Dumps Questions Answers

Salesforce explicitly states that changing the Team Member Hierarchy Type for Account Manager Targets causes all existing targets to become read-only. This behavior protects previously distributed target structures from being modified after the hierarchy model used to determine team membership has changed.

Manufacturing Cloud supports two relevant hierarchy models. Forecasts Hierarchy derives team relationships from the forecasting hierarchy configured in Salesforce. Manager Hierarchy instead relies on the Manager field configured on individual User records. When the hierarchy is switched, the organizational relationships used for allocation and target distribution can differ materially. Existing targets therefore cannot simply continue operating under assumptions established by the previous hierarchy.

Salesforce does not delete access to the targets, nor does it return them to Draft status. Historical targets remain available for visibility, reporting, and reference, but Salesforce prevents further modifications by making them read-only.

Administrators should therefore determine the appropriate team hierarchy before large-scale target creation and distribution whenever possible, because changing this setting has a direct effect on all targets already established.

Study Guide references/topics: Configure and Build — Account Manager Targets; Team Member Hierarchy; Manager Hierarchy; Forecasts Hierarchy; Target Administration.

Benefit Mapping is used when the value of a rebate benefit must vary according to an additional dimension such as Product, Product Category, territory, industry segment, or another business attribute.

Salesforce defines benefit mappings as field mappings between the Program Rebate Type Benefit object and the aggregate object, normally Rebate Member Product Aggregate. When a rebate's benefit depends on a Product dimension, equivalent fields are established on the two objects and mapped so that the appropriate benefit can be selected according to the aggregated transaction's product characteristics.

For example, one benefit tier might award different rebate percentages for different product categories even where the transaction amount qualifies for the same overall attainment tier. Benefit Mapping supplies the extra granularity needed to distinguish those outcomes.

Payout configuration determines how earned rebate amounts are settled; it does not define the additional dimensional criteria controlling the benefit. Likewise, rebate-type configuration establishes the broader calculation model but does not replace the benefit mapping required for dimension-specific benefit values.

Therefore, a Product-defined rebate benefit must use the Benefit Mapping related-list functionality.

Study Guide references/topics: Configure and Build — Rebate Management; Benefit Mappings; Program Rebate Type Benefit; Product Dimensions; Rebate Member Product Aggregate.

Products used in transactional Salesforce processes must first be available for sale. Salesforce Manufacturing documentation identifies the Active field on Product as controlling whether the product can participate in processes such as orders, quotes, and sales agreements. Therefore, simply creating Product records is insufficient; the products must be activated.

They also require pricing configuration. Salesforce price books contain the products that an organization sells and their prices, and a Standard Price Book entry establishes the standard price for a product. Salesforce requires a standard price before a product can participate correctly in price-book-driven selling processes.

When a Sales Agreement is created, the user selects a price book, and Salesforce filters available products based on that price book. Consequently, the correct setup is to activate the new products and establish them in the Standard Price Book.

Merely activating Product records does not provide the complete pricing configuration needed for sales agreement product selection.

Study Guide references/topics: Configure and Build — Sales Agreements; Products; Price Books; Product Availability.