n: When planning a global rollout of Manufacturing Cloud, some key considerations are:

• Manufacturers may have one or many versions of core systems like an Enterprise Resource Planning (ERP) that will require integrations and design considerations that vary. Manufacturing Cloud can integrate with existing ERP systems and Order Management Systems (OMS) by using APIs, the MuleSoft Accelerator for Manufacturing, or other middleware solutions1. However, different versions of ERP systems may have different data models, business processes, and security requirements that need to be taken into account when designing and implementing the integrations2.
• There are language requirements, legal variation by geography, and cultural differences. Manufacturing Cloud supports multiple languages and currencies, but it also needs to comply with the local laws and regulations of each country or region where it operates1. For example, there may be different tax rules, privacy policies, or data protection standards that affect how Manufacturing Cloud handles and stores customer data3. Additionally, there may be cultural differences in how customers and partners communicate, negotiate, and collaborate, which may require adjustments in the user interface, workflows, and analytics of Manufacturing Cloud4. References: Considerations for Working with Manufacturing, What Is Manufacturing Cloud?, Salesforce Blog: Manufacturing Cloud, Salesforce Manufacturing Cloud: enabling customer centricity for manufacturers

Sales agreement cloning is a feature that allows users to create a new sales agreement by copying the details from an existing one. This can save time and effort when creating similar sales agreements for different accounts or time periods. When cloning a sales agreement, the product details, such as product name, quantity, price, and discount, are copied over from the original sales agreement. The new sales agreement is created in draft status, which means it can be edited and submitted for approval. The default start date of the new sales agreement is the current date, not the start date of the original sales agreement. The agreement term details, such as metrics, actuals, and forecasts, are not copied over from the original sales agreement, as they are specific to each sales agreement and time period. References: Clone a Sales Agreement, Sales Agreement Cloning

 Account Manager Targets is a feature of Manufacturing Cloud that allows you to set up and manage sales goals and track performance for your account managers and their teams. To use this feature, you need to enable it in Setup and define some settings that affect how targets are created, assigned, and distributed. The three options that can be defined by an admin in the Setup area in Account Manager Targets are:

• Target Measure Type: This is the unit of measurement for the targets, such as revenue, volume, or any custom measure. You can define up to three target measure types for your org and assign them to different target types. For example, you can have a target type for revenue and another one for volume, and use different target measure types for each one.
• Team Member Hierarchy: This is the hierarchy that determines how targets are rolled up from individual account managers to their managers and so on. You can use the standard User Role hierarchy or a custom hierarchy based on a custom object. The hierarchy affects how targets are distributed, aggregated, and reported.
• Distribution Frequency: This is the frequency at which targets are distributed from parent targets to child targets. You can choose from monthly, quarterly, or yearly distribution. The distribution frequency affects how targets are calculated and displayed for different time periods.

References: Account Manager Targets in Manufacturing Cloud | Salesforce Trailhead Module, Enable Account Manager Targets - Salesforce, Define Account Forecast Settings Unit | Salesforce Trailhead Module

Account forecasts are long-term projections of revenue and volume for accounts based on sales agreements, opportunity products, and account manager targets. Account forecasts can be generated and displayed monthly or quarterly, depending on the business needs. The forecast frequency can be changed in the account forecast settings by an administrator. However, changing the forecast frequency has some consequences that the administrator needs to be aware of. First, a full regeneration of all the eligible account forecasts will be carried out, meaning that all the existing account forecasts will be recalculated based on the new frequency. This may take some time and consume system resources. Second, all the previously active account forecasts will expire, meaning that they will no longer be available for viewing or editing. This is to avoid confusion and inconsistency in the forecast data. Therefore, the administrator should carefully consider the impact of changing the forecast frequency and communicate the change to the account managers and other stakeholders. References: Define Account Forecast Settings, Salesforce Manufacturing Cloud Flashcards, Configure Forecast Generation and Display Settings

Account Based Forecasting allows the account owner to set the account growth and market growth values for each account. These values are used to calculate the forecast quantity and revenue based on the historical orders, sales agreements, and opportunities. The account growth represents the expected growth of the account relative to the market, while the market growth represents the expected growth of the market for the products sold by the account. If Universal Containers expects a 5% increase in the market but has a target growth of 10%, the account owner should set the account growth to 5%, which means the account is expected to grow 5% faster than the market. This will increase the forecast quantity and revenue by 5% compared to the baseline forecast. Updating the account forecast to 10% or the market growth to 10% will not achieve the same result, as they will affect the forecast calculations differently. References: Create Accurate Account Forecasts, Considerations for Working with Manufacturing

 A sales agreement in Manufacturing Cloud represents a long-term agreement between a buyer and a seller to negotiate price and volume of products1. It provides a consolidated view of all the terms of the agreement, including the duration, products, price, planned quantities, and actual quantities2. A sales agreement can be created from an external source, such as a quote, opportunity, or custom object3. A sales agreement can also be used to create accurate account forecasts based on the planned and actual quantities4. References: Sales Agreements and Forecasting in Manufacturing Cloud, Get Started with Sales Agreements, SalesAgreement, Sales Agreement

When you change the forecast formula, the existing forecasts are deleted and new forecasts are generated using the updated formula. This applies to all forecasts, regardless of their status. Therefore, the correct answer is C. Regeneration of all forecast(s). References: Build Formulas to Calculate Forecast, Configure Forecast Metrics and Formulas

 These three user types can be selected to receive credit for an order in the Tableau CRM configuration wizard when calculating actuals against account manager targets. The configuration wizard guides users through the creation of an app from the Analytics for Manufacturing template and allows them to customize the data and settings for the app. One of the settings is to choose who gets credit for the orders, which determines how the actual revenue is attributed to the account managers. The user can select one of the following options:

• Account Owner: This option credits all orders to the account owner’s actual revenue, regardless of who owns the order. This is useful when the account owner is responsible for the overall relationship and revenue of the account.
• Order Owner: This option credits all orders to the order owner’s actual revenue, regardless of who owns the account. This is useful when the order owner is responsible for the individual order and revenue of the order.
• Other User: This option credits all orders to a custom user’s actual revenue, based on a custom lookup field for a user on the account. This is useful when there is a different user, such as a sales engineer or a partner, who is responsible for the order and revenue of the order.

References: = Create and Share an App from the Analytics for Manufacturing Template, Salesforce Authentication - Tableau, The Configuration Wizard - Salesforce Developers

The time series projection feature in Tableau CRM for manufacturing is a predictive modeling function that allows you to forecast future values based on historical data. It provides data insights by showing you how your products, accounts, and margins are expected to perform over time, and how they compare to your goals and benchmarks. You can use the time series projection feature to answer questions such as:

• How will my product sales grow or decline in the next quarter or year?
• How will my account revenue change over time and how does it align with my targets?
• How will my product margins vary across different regions and segments and how can I optimize them?

The time series projection feature uses an algorithm called exponential smoothing, which assigns more weight to recent data and less weight to older data, to create a smooth curve that fits the historical data and extends into the future. You can adjust the projection parameters, such as the confidence interval, the seasonality, and the trend, to customize the forecast according to your business needs and assumptions. You can also compare different scenarios and what-if analyses using the projection feature. References: = Predictive Modeling Functions in Time Series Visualizations, Time Series Forecasting: Definition & Examples, Time Series Analysis: Definition, Types & Techniques

n: To enable a phased rollout of the Sales Agreements functionality, a consultant should deploy the new functionality and assign the permission set to the designated users. The permission set grants access to the Sales Agreements object and related actions, such as creating, editing, approving, and activating sales agreements. By assigning the permission set to the designated users, the consultant can control who can use the new functionality and monitor the adoption. The consultant does not need to make the Sales Agreements tab visible for the designated users, as the tab is automatically visible once the permission set is assigned. The consultant also does not need to assign the Manufacturing licenses to all of the users, as the licenses are only required for users who need access to the Manufacturing Cloud features, such as account forecasting and data processing engine. References: Get Started with Manufacturing Cloud for Sales, Assign the Manufacturing Permission Sets to Users

o help the executive team make decisions quickly, an administrator should implement Product Categories functionality. Product Categories are a way of grouping products based on common characteristics, such as type, brand, flavor, or package12. By using Product Categories, the executive team can easily filter, sort, and analyze the large number of SKUs in their business. They can also use Product Categories to create sales agreements and forecasts at different levels of granularity1. References: Manage Products and Categories in a Sales Agreement, Configure Product Hierarchies Unit

Universal Containers does not want to bring actual orders data into Salesforce, but still wants to use the actual orders data to analyze the effectiveness of their sales agreements, they must select the Manually Using actual orders API option in the sales agreement setup. This option allows them to use an API to upload actual order data from an external system into Salesforce and associate it with the sales agreements. This way, they can compare the planned and actual quantities and revenues of each product or product category in the sales agreement. The other options require either creating orders in Salesforce or linking contracts to orders in Salesforce, which Universal Containers does not want to do. References: Choose How Sales Agreement Actuals Are Calculated, Create Orders to Calculate Sales Agreement Actuals

A sales agreement is a record that captures the terms and conditions of a long-term or run-rate business relationship between a manufacturer and a customer. It can include products, product categories, prices, volumes, schedules, and other details. A sales agreement can have a maximum of 1500 products or product categories and 72 schedules. Contact Salesforce support if you want to increase the limits. Note that having a large number of product or product categories and schedules can affect system performance1. References: Considerations for Working with Manufacturing

n: A sales agreement is a contract between a manufacturer and a customer that specifies the terms and conditions of a long-term sales relationship. A sales agreement consists of a sales agreement record and one or more sales agreement products. A sales agreement product is a line item that represents a product or a product category that the customer agrees to purchase over a period of time. A sales agreement product schedule is a subcomponent of a sales agreement product that defines the quantity and revenue expectations for each time period within the sales agreement term. To load data into sales agreements, you must follow the correct data load sequence to ensure data integrity and avoid errors. The data load sequence is as follows:

• First, load the sales agreement records, which contain the basic information about the sales agreement, such as name, account, start date, end date, status, and so on.
• Second, load the sales agreement products, which are related to the sales agreement records by the Sales Agreement ID field. Each sales agreement product must have a valid product or product category, name, initial planned quantity, and price book entry.
• Third, load the sales agreement product schedules, which are related to the sales agreement products by the Sales Agreement Product ID field. Each sales agreement product schedule must have a valid period, quantity, and revenue. References: Sales Agreement, Sales Agreement Product, Sales Agreement Product Schedule, Data Load Sequence for Manufacturing Cloud

o add products to an order that is on an active sales agreement, the order must be in Draft status. Once an order is in Draft status, you can add products from the sales agreement or from the product catalog. You can also edit the order details, such as quantity, price, and discount. After you add the products, you can submit the order for approval. The order status changes to Pending, and the order is locked for editing. The order must be approved before it can be activated. Once the order is activated, the order status changes to Active, and the order is synced with the sales agreement. The order actuals are reflected in the sales agreement actuals. References: Approve and Activate a Sales Agreement, Get Started with Salesforce Order Management

According to Salesforce Manufacturing Cloud documentation, there is no defined limit on the number of sales agreements that can be activated for the same period, containing the same products, and linked to the same account. However, it is recommended to use sales agreements judiciously and avoid creating duplicate or overlapping agreements that could cause confusion or errors in forecasting and reporting. Sales agreements are meant to capture the negotiated terms and conditions of the run-rate business with customers and partners, and they should reflect the actual demand and order realization data. References: Sales Agreements, Frequently Asked Questions for product keys. | Microsoft Learn, Salesforce Manufacturing Cloud Certification Flashcards | Quizlet.

 The first step in providing insights to the account reps is enabling metric groups. Metric groups are collections of metrics that are relevant for a specific business scenario or use case. They allow account managers to view and compare agreement terms for different metrics, such as revenue, volume, margin, and so on1. Enabling custom metrics and allowing account reps to add agreement terms are not the first steps, as they require metric groups to be enabled first23. References: 1: Create Metric Groups for Sales Agreements4, 2: Map Custom Fields of Sales Agreement Products and Schedules, 3: Select Metrics to Display in Agreement Terms.

The detailed technical design document is a document that describes the technical specifications and architecture of a solution. It is based on the functional and nonfunctional requirements that are captured in the business requirement document1. Therefore, the detailed technical design document should be completed after the business requirement document has been generated, and before the development and testing phases of the project. This ensures that the technical design aligns with the business needs and expectations, and provides a clear roadmap for the implementation team2. References: 1: Get Started with the Technical Project Documentation3, 2: Documentation and Implementation Diagrams1

 You can recalculate payouts for closed periods in two situations: when the member benefits change due to changed requirements, or when the member submits transactions after the payout period is closed, or there is an error in the payout calculation. In both cases, you need to modify the payout records and run the rebate flow again to recalculate the payouts. The first method is to recalculate payouts due to changed benefits, which means that the benefit structure and terms have changed after the payout was calculated for a period. The second method is to recalculate payouts with no charge in benefits, which means that the benefit structure and terms have not changed, but the transactions or the payout calculation have changed. References: Recalculate Payouts for Closed Periods, Rebate Management

 The Minimum Inventory field on the Sales Agreement Product Schedule object is used to store the minimum inventory quantity required for each product in a sales agreement. To make this field visible and editable on the Forecast grid, UC needs to add a custom Minimum Inventory field to the Sales Agreement Product object, which is the parent object of the Sales Agreement Product Schedule object. Then, UC needs to map the two fields using the Field Mapping tool in the Sales Agreement setup. This will ensure that the values entered in the Forecast grid are synced with the values in the Sales Agreement Product Schedule object. Finally, UC needs to add the Minimum Inventory field to the list of available metrics in the Sales Agreement setup. This will allow users to select the Minimum Inventory metric from the dropdown menu on the Forecast grid and see the values for each product and time period. References: Sales Agreement Product Schedule, Sales Agreement Product, Field Mapping, Forecast Grid

To delete a sales agreement, the user must have the Delete Sales Agreements permission, which is included in the Manufacturing Sales Agreement Manager permission set. This permission allows the user to delete an active, approved, canceled, or expired sales agreement, as long as it does not have any active orders associated with it. Giving the user the Delete Sales Agreements profile or the Remove Sales Agreement permission will not enable them to delete sales agreements, as these are not valid options in Salesforce Manufacturing Cloud. References: Delete a Sales Agreement, Assign the Manufacturing Permission Sets to Users.

 Rebate Management allows businesses to create and manage rebate programs that reward their partners for meeting sales targets. A rebate program consists of a rebate type, which defines the incentive structure, and a rebate agreement, which specifies the eligible partners and products. A rebate type benefit is a component of a rebate type that defines the thresholds of an incentive and how payouts are scaled for varying quantities and amounts. A benefit tier is a subcomponent of a rebate type benefit that specifies a range of sales targets and applicable benefit values. The minimum and maximum range values of a benefit tier must be positive integers and must not overlap with other benefit tiers in the same benefit. Therefore, the sequence of 0 to 100 is valid, while the other sequences are not. References: Rebate Management, Create and Manage Rebate Programs, Rebate Management Workflow

To meet the business requirements of UC, the administrator should add a custom Material dimension to the Forecast Fact and Forecast Set objects. This will allow UC to group and filter the forecast data by the material attribute of the products. The administrator should also clone and use the standard DPE definitions to populate the new custom metrics for the Material dimension. The standard DPE definitions are templates that can be used to aggregate data from various sources, such as sales agreements, orders, opportunities, and custom objects. By cloning and using the standard DPE definitions, the administrator can save time and effort in creating the formulas and filters for the new custom metrics. The administrator does not need to configure a custom Forecast Context or create new DPE definitions from scratch, as these options are more complex and require more customization. References: Create Holistic Forecasts with Advanced Account Forecasting, Set Up Dimensions and Period Groups, Streamline Forecast Calculations with Data Processing Engine Definitions

 The Mass Update function allows you to update multiple values of a single metric of a sales agreement in the Sales Agreement Terms tab. You can use this function to quickly adjust the planned quantity, revenue, or margin of multiple products and periods with a single action. The available actions are Decrease By, Increase By, and Replace With. These actions let you specify a percentage or an absolute value to decrease, increase, or replace the existing values. For example, you can use the Decrease By action to reduce the planned quantity of all products by 10% for the next quarter. You can also add a note to explain the reason for the mass update. References: Mass Update Sales Agreement Action, Update Multiple Values of Sales Agreements

 Email notifications are an out-of-the-box Manufacturing Cloud function that can be used to notify users if automated processes fail. Automated processes are workflows, processes, or Apex triggers that update records based on certain criteria or events. If an automated process fails, Salesforce sends an email to either the admin who last modified the associated flow or the Apex exception email recipients. The email includes the data that’s involved in the process or flow, including user-entered data, and the error message that caused the failure. You can configure the email recipients and the email content in the Process Automation Settings page in Setup. References: = Select Flow and Process Error Email Recipients, Troubleshoot Flow Errors

A rebate type benefit defines the thresholds of an incentive and how payouts are scaled for varying quantities and amounts. The minimum and maximum range values specify the sales targets for each benefit tier. The range values must be continuous and non-overlapping, meaning that the minimum value of one tier must be equal to the maximum value of the previous tier, and there should be no gaps or overlaps between the tiers. Therefore, option A is the only valid sequence of minimum and maximum range values for a rebate type benefit. References: Rebate Management Workflow, Create and Manage Rebate Programs

Salesforce Manufacturing Cloud allows users to define the renewal period for sales agreements in their org. The renewal period is the number of days before the end date of a sales agreement from when users can renew the agreement. Users can renew a sales agreement only when the renewal period starts. The other options are not related to the renewal of sales agreements. References: Define Renewal Period for Sales Agreements

 Invalid target assignments are team assignments that are no longer valid due to changes in the target or the team member. For example, if a team member leaves the company or is reassigned to another target, their existing assignments become invalid. Invalid target assignments are shown in the Invalid Team Assignments section of the Assignments tab in the target’s record. This section displays the invalid assignments for all team members who have access to the target, regardless of the ownership. Invalid target assignments can also be seen in the Invalid Target Assignments report, which is a standard report provided by Manufacturing Cloud. This report shows all the invalid assignments for the current user and their subordinates, along with the reason for the invalidity. The report can be filtered by target name, team member name, or invalidity reason. References: Distribute Targets and Manage Invalid Targets Unit, Manage Invalid Team Assignments

According to the Salesforce Manufacturing Cloud documentation1, if you modify the forecast display settings, such as the forecast start period, the forecast frequency, or the forecast display duration, all active forecast records expire, and the regenerated records replace them. These actions trigger the regeneration of all the eligible accounts that satisfy the forecast generation criteria. Updating the forecast adjustment period or the forecast formula does not affect the forecast display settings, and therefore does not trigger the regeneration of account forecasts. References: Configure Forecast Generation and Display Settings

If an org hits the account product period forecast record limit, it means that the org has reached the maximum number of records allowed for the Account Product Period Forecast object, which is 9 million1. This limit affects the functionality of account forecasting in the following ways:

• New products are not added when recalculating a single account forecast or recalculating all account forecasts. This means that if a new product is added to a sales agreement or a contract after the limit is reached, it will not be reflected in the account forecast, even if the forecast is recalculated manually or automatically. The only way to add new products to the account forecast is to delete some existing records from the Account Product Period Forecast object to free up some space2.
• The add products option will no longer appear on the agreement terms tab. This means that users will not be able to add new products to an existing sales agreement or a contract from the agreement terms tab. The only way to add new products to an agreement is to create a new agreement with the new products, or to edit the agreement in the related list of the account forecast2.

References: View the Defined Limits, Percentage of Limit Used, and Usage Details for Account Forecasts, Define Account Forecast Settings Unit | Salesforce Trailhead

When an administrator changes the team member hierarchy type for account manager targets, the existing targets are affected by this change. The status of all existing targets becomes read-only, which means that they cannot be edited or deleted. This is to prevent any inconsistency or data loss due to the change in hierarchy. The new hierarchy type will apply only to the new targets that are created after the change. References: Choose Team Member Hierarchy for Account Manager Targets

To migrate data from a legacy system to Manufacturing Cloud, the administrator should follow the recommended order of data import. This order ensures that the data dependencies and relationships are maintained and that the data integrity is preserved. The recommended order of data import is as follows1:

• Accounts: This is the first object to import, as it represents the customers and their details. Accounts are related to Sales Agreements and Orders, so they must be imported before them.
• Sales Agreements: This is the second object to import, as it represents the contractual agreements between the customers and the manufacturer. Sales Agreements are related to Sales Agreement Products and Sales Agreement Schedules, so they must be imported before them.
• Sales Agreement Products: This is the third object to import, as it represents the products that are included in the Sales Agreements. Sales Agreement Products are related to Sales Agreement Product Schedules, so they must be imported before them.
• Sales Agreement Product Schedules: This is the fourth object to import, as it represents the forecasted quantities and prices of the Sales Agreement Products over time. Sales Agreement Product Schedules are related to Orders, so they must be imported before them.
• Orders: This is the fifth and final object to import, as it represents the actual orders placed by the customers. Orders are related to Order Products, which are automatically created when the Orders are imported.

Therefore, the correct answer is B. Accounts, Sales Agreements, Sales Agreements Schedules, Orders. References: Import Data into Manufacturing Cloud

The administrator would configure Field-Level Security for the Advanced Account Forecast Partner and Advanced Account Forecast Fact objects to provide users with separate levels of visibility to forecast data. The Advanced Account Forecast Partner object stores the partner information for each account forecast record, such as the partner name, partner type, and partner role. The Advanced Account Forecast Fact object stores the forecast values for each account forecast record, such as the forecast amount, forecast quantity, and forecast margin. By setting the Field-Level Security for these objects, the administrator can control which users can view, edit, or delete the partner and fact data for each account forecast record. This way, the administrator can ensure that the users only see the relevant forecast data for their role and business unit12. References: 1: Set Field-Level Security for Fact and Partner Object in Advanced Account Forecasting3, 2: Forecast Fact Object Included with Advanced Account Forecasting4