Passed Exam Today AP-213

Salesforce controls Sales Agreement renewal according to both the configured renewal period and the agreement's status category.

Current Salesforce guidance specifies that the Renew action is available when the Sales Agreement is in an eligible status such as Activated, Under Revision, or Expired, provided that the agreement is within its configured renewal period and the user has the required permissions. Agreements in statuses such as Draft, Approved, Cancelled, or Rejected are not eligible for renewal.

An Approved agreement has completed approval but has not yet transitioned to the operational status required for normal agreement execution. Approval and activation are separate lifecycle concepts in Manufacturing Cloud. The agreement should proceed to an eligible operational status before renewal functionality is available.

An Expired agreement can still be eligible for renewal, and an Activated agreement becomes renewable once it falls within the defined renewal window.

Therefore, of the statuses presented, Approved prevents the administrator from using the standard renewal operation.

Study Guide references/topics: Configure and Build — Sales Agreement Lifecycle; Renewal Period; Sales Agreement Status; Renew Action.

Standard Account Forecasting in Manufacturing Cloud calculates forecasts by consolidating business information from Orders, Opportunities, and Sales Agreements. Salesforce states that when a product is associated with any of these sources for an account, Account Forecasting can calculate quantity and revenue forecasts for that product. This allows manufacturers to combine committed run-rate business, pipeline business, and actual/order-driven demand into one account-level forecast.

Sales Agreements represent recurring or negotiated long-term business and provide planned quantities and revenues. Opportunities represent potential new business and pipeline demand. Orders provide transactional information related to customer purchases. Forecast formulas determine how those sources contribute to calculated forecast values for each period.

This is an important distinction from Advanced Account Forecasting, which supports a significantly broader data model. Advanced Account Forecasting can use Orders, Opportunities, Sales Agreements, historical Orders, custom objects, custom measures, and external business information. Salesforce currently recommends Advanced Account Forecasting for new implementations while existing standard Account Forecasting implementations should plan migration where appropriate.

Study Guide references/topics: Configure and Build — Account Forecasting; Forecast Data Sources; Orders; Opportunities; Sales Agreements.

Because the Sales Agreements use Product as the product level and calculate actuals Automatically from Direct Orders, the historical migration must include the records needed to establish customer, product, and order relationships.

Accounts identify the customers associated with the Sales Agreements. Products identify the items represented in the product-level agreements. Orders and Order Lines provide the historical transactional quantities from which Sales Agreement actuals can be calculated after the records are correctly associated. Salesforce's Manufacturing data model places Sales Agreement, Product, Order, and Order Product information within the Sales Agreement actuals architecture.

Salesforce explicitly states that with Automatically from direct orders, actual quantities are derived from active Orders that reference the relevant Sales Agreement.

Invoices are not the source used by the standard Direct Orders actuals mode. They may be relevant to financial systems or custom actuals processing, but they are not required by this configuration.

Opportunities represent prospective sales pipeline and likewise are not required for the direct-order actuals calculation.

Therefore, the historical data design must account for Accounts, Products, Orders, and Order Lines before activating the Sales Agreements.

Study Guide references/topics: Validate and Deploy — Historical Data Migration; Sales Agreements; Direct Orders; Accounts; Products; Order Products; Actuals Calculation.

The Account Forecast Formula Builder supports formulas that apply to defined period ranges. Each formula specifies a Start Period and End Period, allowing different calculation logic to be applied to different portions of the rolling forecast horizon.

For a 13-month planning horizon, the established configuration pattern is to create one formula covering periods 1–12 and a separate formula for period 13. This maintains a clear distinction between the standard 12-month planning horizon and the additional trailing period while avoiding unnecessary duplication of formulas for every individual month.

Salesforce's Formula Builder permits either one formula across a range or multiple formulas across separate ranges. Formula expressions can incorporate Orders, Opportunities, Sales Agreements, account metrics, mathematical operators, and functions. The forecast display itself can extend across multiple periods according to the configured display duration.

Validation rules and approval processes do not calculate Account Forecast values, so options A and D do not address the requirement. Creating 13 individual formulas is unnecessarily granular when the same logic applies across the first 12 periods.

Therefore, separate formula ranges for periods 1–12 and 13 provide the appropriate configuration.

Study Guide references/topics: Configure and Build — Account Forecast Formula Builder; Period Ranges; Rolling Forecasts; Forecast Calculation Logic.