Minimum Inventory is a custom Sales Agreement metric. Salesforce requires corresponding custom fields on both the Sales Agreement Product and Sales Agreement Product Schedule objects when a metric must be displayed and managed through Agreement Terms.

Because the schedule-level Minimum Inventory field already exists, UC must create the corresponding custom field on Sales Agreement Product and map it to the Sales Agreement Product Schedule field. Salesforce allows Number, Currency, and Formula fields to participate in these mappings. After the mapping is configured, the metric must be added to a metric group so users can view and edit it in the Agreement Terms table.

The product-level field represents the metric at the Sales Agreement Product level, while the schedule field stores the metric for individual periods. If aggregated behavior is required, Salesforce also supports a Roll-Up Summary field on Sales Agreement Product for Number or Currency values stored on schedules.

Adding the field directly to Sales Agreement does not provide the required product-and-period metric structure. Creating only a product field without mapping it also leaves Manufacturing Cloud unable to treat the two fields as a unified Agreement Terms metric.

Study Guide references/topics: Configure and Build — Sales Agreement Custom Metrics; Field Mapping; Metric Groups; Agreement Terms.

Salesforce provides native Sales Agreement renewal configuration, so the administrator should use the standard renewal capability rather than build custom validation or automation. In Manufacturing Cloud Setup, the administrator navigates to Sales Agreements and specifies the number of Renewal Days in the Renewal Period Start configuration. The value determines how many days before an agreement's End Date its renewal period begins.

For a requirement of 180 days, the administrator configures the renewal period to begin 180 days before the Sales Agreement end date. Salesforce then uses that setting across Sales Agreements in the org. The renewal window ends on the agreement's End Date, and eligible users can renew qualifying agreements during that configured period.

A validation rule would only enforce record criteria and would not establish Manufacturing Cloud's native renewal lifecycle. Likewise, a Flow could send reminders or execute additional business automation but is unnecessary for defining when the standard Renew functionality becomes available.

The design principle is to use the platform's declarative Manufacturing Cloud configuration before introducing custom logic.

Study Guide references/topics: Configure and Build — Sales Agreement Foundations; Sales Agreement Lifecycle; Renewal Period; Manufacturing Cloud Setup.

Rebate Management uses Transaction Journal records as the transactional input for rebate eligibility, aggregation, and payout calculations. When the source transaction contains additional business attributes required for rebate processing—such as invoice status—Salesforce specifically supports creating custom fields on Transaction Journal to store that information. Salesforce explicitly lists invoice status/payment status as an example of information that can be added for rebate processing.

The administrator should therefore create a Transaction Journal field for the source Invoice Status and populate it when invoice transactions are converted or imported. The Rebate Type's eligibility criteria can then evaluate that field and include only transactions whose Invoice Status is Paid. Salesforce defines rebate eligibility criteria as filters evaluated against Transaction Journal fields and supports mappings from source objects into those fields.

This approach keeps the business rule within Rebate Management, where it can be maintained transparently as part of the rebate-program configuration.

Salesforce does not automatically assume that only Paid invoices qualify. Likewise, filtering upstream exclusively in ERP would move rebate eligibility logic outside the rebate solution. DPE filters can be customized for specialized processing, but a straightforward invoice-status eligibility rule is appropriately represented as Transaction Journal data plus Rebate Type eligibility criteria.

Study Guide references/topics: Configure and Build — Rebate Management; Transaction Journals; Eligibility Criteria; Custom Transaction Fields; Rebate Types.

A controlled Manufacturing Cloud migration should load only the data required by the target solution and preserve the relationships on which the imported records depend. Salesforce's Manufacturing CSV data-management capability is specifically designed to normalize information from external systems into a defined target structure, map source columns to Salesforce fields, and validate the resulting import.

For Order data, required related records must already be identifiable. An Order commonly depends on records such as Account and related commercial structures, while Order Products depend on Products and Price Book information. Salesforce migration guidance emphasizes loading records in dependency order and correctly remapping relationship identifiers so related records remain associated after migration.

A template containing only required fields minimizes unnecessary transformation, reduces validation errors, and prevents obsolete legacy information from being transferred simply because it existed in the source system. Automations or validation logic that would incorrectly interfere with controlled migration should also be identified and temporarily managed according to the deployment plan.

Importing a legacy extract “as-is” is inappropriate because source and Salesforce schemas rarely align directly. Option B is less precise because a migration template should deliberately contain the required target fields rather than unnecessary data.

Study Guide references/topics: Validate and Deploy — Data Migration; Data Templates; Data Mapping; Record Dependencies; Data Validation.

The Claim object stores the high-level information that defines a warranty claim. Salesforce explicitly identifies Claim Type, Claim Reason, and Account as information captured on the Claim record. Other fields include status, severity, claim amounts, usage type, related claim information, and finalization details.

The associated warranty claim objects serve more granular purposes. A Claim Item represents the defective asset and records information such as asset usage, repair date, and fault-related details. Claim Participant associates stakeholders—such as dealer representatives, customers, or service technicians—with the claim. Neither serves as the primary record for the overall type, reason, and account.

Manufacturing Experience Cloud can expose this warranty claims framework to partners and distributors, allowing them to create warranty claims and track their status. The complete data model can include Claim, Claim Item, Claim Coverage, Claim Coverage Payment Detail, and Claim Participant records, with Claim operating as the parent-level business record.

Using the Claim as the parent record also ensures consistent status tracking and consolidated reporting across all supporting claim details.

Study Guide references/topics: Configure and Build — Manufacturing Service Experience; Warranty Claims; Claims Data Model; Manufacturing Experience Cloud.

Program Based Business is specifically designed for manufacturing scenarios in which a supplier's products become components of another manufacturer's finished product. Salesforce uses the example of a component supplier deriving forecasts from an Original Equipment Manufacturer's program demand, which directly mirrors the scenario described here.

Program Based Business enables manufacturers to define their own products alongside customers' products, establish relationships between those products, build programs and program variants, create component forecasts, import external forecast information, and transform forecasted component demand into future opportunities. This is particularly important when multiple distributors, contract manufacturers, or approved suppliers participate in fulfillment because the manufacturer must understand the underlying brand or program demand independently of individual channel orders.

Advanced Account Forecasting is an important underlying forecasting capability, but by itself it does not provide the complete program-centric commercial model required for OEM-driven component demand. Sales Agreements primarily represent committed run-rate relationships with direct trading partners.

Program Based Business therefore provides the correct abstraction for preserving end-customer or phone-brand demand while using downstream channel activity to support opportunity planning.

Study Guide references/topics: Design — Program Based Business; Manufacturing Programs; Component Forecasts; Program Forecast Sets; Business Transformations; Future Opportunity Planning.

The detailed technical design document converts approved business requirements and business design into the specific technical architecture and implementation approach that the delivery team will build.

The current Agentforce Manufacturing Professional exam guide explicitly requires a consultant to develop a detailed technical design document that outlines the proposed solution's architecture, components, interfaces, data flows, and system interactions, while ensuring alignment with business requirements and Salesforce best practices.

In practical Manufacturing Cloud terms, the document can define how Sales Agreements are configured, how forecast dimensions and measures are modeled, what DPE definitions are required, how security is implemented, which integrations connect ERP or other systems, what data is migrated, and how custom automation is designed.

A Statement of Work serves a different purpose. It establishes commercial scope, responsibilities, assumptions, schedule, and potentially cost.

Personas and user stories belong primarily to discovery and business-design activities. They explain what users need to accomplish but do not provide the detailed configuration and technical implementation specifications required by developers and administrators.

Therefore, the detailed technical design document defines how the agreed Manufacturing Cloud functionality will technically be configured and implemented.

Study Guide references/topics: Design — Detailed Technical Design; Architecture; Components; Interfaces; Data Flows; Solution Configuration.

A global Manufacturing Cloud rollout must account for differences in the organization's existing technical landscape. Large manufacturers frequently operate multiple ERP instances, sometimes involving different ERP products, releases, data models, integration technologies, regional processes, and master-data structures.

The current Agentforce Manufacturing Professional exam guide explicitly requires consultants to analyze existing technical architecture, data governance, system limitations, and dependencies and to develop a comprehensive rollout strategy for multi-country deployments.

ERP variation is especially significant because Manufacturing Cloud implementations commonly depend on external systems for orders, products, inventory, invoicing, and other operational information. A rollout architecture that works with one country's ERP instance cannot automatically be assumed to work unchanged with another region's platform. Integration mappings, authentication, middleware, source-system ownership, process timing, and data-quality rules may all require regional analysis.

Localization, regulatory, and cultural factors are also relevant to global implementations, but among the listed choices, the varying ERP and integration landscape represents a direct Manufacturing Cloud architecture and dependency consideration emphasized by the exam's Discovery objectives.

Option C is incorrect because Manufacturing Cloud does not impose a universal requirement that global deployments must always be phased country by country.

Study Guide references/topics: Discovery — Global Rollout Strategy; Technical Architecture; Third-Party Systems; ERP Integration; Dependencies; Data Governance.

Manufacturing Cloud uses a configurable renewal period to control when users can begin renewing Sales Agreements. The administrator defines the number of Renewal Days before the agreement's End Date. Salesforce then calculates the beginning of the renewal window from that value.

For example, if a Sales Agreement ends on December 31 and Renewal Days is configured as 30, the renewal period begins on December 1. Salesforce explicitly states that users can renew Sales Agreements during their configured renewal period.

When a Sales Agreement is renewed, Salesforce creates another Sales Agreement representing the continuing customer commitment. Renewal functionality preserves the commercial relationship while providing a new agreement record for the subsequent term. Salesforce also supports renewal for agreements in applicable lifecycle states and carries relevant product and planning information into the renewed agreement.

Fiscal-period rollover, actuals recalculation, and forecast regeneration are unrelated processes and do not determine when a Sales Agreement becomes eligible for renewal.

The important trigger is therefore the start of the configured renewal period, which occurs a specified number of days before the current Sales Agreement's End Date.

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

Discovery should begin with an understanding of the organization's broader business landscape before requirements are translated into Salesforce features. Starting at the business level helps the consultant identify strategic objectives, pain points, process boundaries, stakeholders, dependencies, handoffs between teams, and areas where meaningful improvement can occur.

The Agentforce Manufacturing Professional exam guide explicitly requires a consultant to conduct a comprehensive analysis of existing business processes and workflows to identify blockers and improvement opportunities. It also requires analysis of performance metrics, third-party integrations, inefficiencies, and technical dependencies before detailed design begins.

This prevents a common implementation failure: treating every stated request as a Manufacturing Cloud configuration requirement without first establishing whether the underlying problem is organizational, operational, integration-related, or technology-related.

Understanding the “big picture” allows requirements to be evaluated in the context of the complete customer lifecycle rather than in isolated departmental silos. It also helps identify opportunities that span multiple teams even when the eventual solution is not entirely within Manufacturing Cloud.

The purpose is not to expand the project indiscriminately. Scope should remain governed by business value, priorities, constraints, and agreed outcomes.

Study Guide references/topics: Discovery — Business Landscape Analysis; Business Processes and Workflows; Pain Points; Cross-Functional Dependencies; Opportunity Identification.