Salesforce Manufacturing-Cloud-Professional Manufacturing Cloud Accredited Professional Exam Exam Practice Test

To export Account Based Forecast data, the user needs to add the fields that capture the forecasting quantity data, including any sales team adjustments. The ‘Adjusted Forecast Quantity’ field shows the forecast quantity after applying the adjustment percentage for each account product forecast. The ‘Total Adjusted Forecasted Quantity’ field shows the sum of the adjusted forecast quantity for all the account product forecasts in the same account forecast1. These fields are available in the standard report type of ‘Account Forecasts with Product Period Forecast’, so there is no need to create a custom report type. References: What Is Manufacturing Cloud?, Create Holistic Forecasts with Advanced Account Forecasting

 A sales agreement is a long-term agreement between a buyer and a seller to negotiate price and volume of products. To create a sales agreement in Salesforce Manufacturing Cloud, you need to have an account object that represents the buyer. The account object stores the information about the customer, such as name, address, contact, industry, and so on. You can also associate a contact object with the account to specify the person who is responsible for the sales agreement. Other objects that are related to the sales agreement are sales agreement product, sales agreement product schedule, sales agreement line item, and sales agreement forecast. References: SalesAgreement | Manufacturing Cloud Developer Guide | Salesforce Developers, Sales Agreements and Forecasting in Manufacturing Cloud | Salesforce Module, Convert Opportunity to Sales Agreements in Salesforce Manufacturing Cloud

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

 A sales agreement is a long-term contract that defines the terms and conditions for the products and services that you sell to your customers. You can perform various actions on a sales agreement to manage its lifecycle, such as approving, activating, expiring, or deleting it. Two of the out-of-the-box actions that you can perform on a sales agreement are:

• Recalculate Actuals: This action updates the actuals for the sales agreement based on the invoices and orders associated with it. You can recalculate actuals manually or schedule it to run automatically at a specified frequency. Recalculating actuals helps you track the progress and performance of the sales agreement over time.
• Update Products: This action allows you to add, remove, or modify the products and categories in the sales agreement. You can update products manually or use the mass update feature to apply changes to multiple products at once. Updating products helps you adjust the sales agreement to reflect the changing needs and preferences of your customers.

References: Sales Agreements and Forecasting in Manufacturing Cloud, Sales Agreement, Get Started with Manufacturing Cloud for Sales, Create and Work with Sales Agreements, Manufacturing Cloud

The account product period forecast record limit is the maximum number of records that can be stored in the Account Product Period Forecast object, which represents the quantity and revenue information of products for a particular time period of the forecast rolling period1. The default limit is 9 million records, but it can be changed by the admin2. If the org hits the limit, new products cannot be added to account forecasts, and new products are not added when recalculating a single account forecast or recalculating all account forecasts2. This means that the forecast data will not reflect the latest changes in the product portfolio and may affect the accuracy of the forecast. The add products option will still appear on the agreement terms tab, but it will not work if the limit is reached. New products added to account forecasts will be included in recalculations, as long as the limit is not exceeded. References: Considerations for Working with Manufacturing - Salesforce, Define Account Forecast Settings Unit | Salesforce Trailhead Module, Advanced Account Forecasting with Manufacturing Cloud | Salesforce, AccountProductPeriodForecast | Manufacturing Cloud Developer Guide | Salesforce Developers

Experience Builder is the tool that can be used to customize the site after selecting the manufacturing template in the community creation wizard. Experience Builder is a point-and-click tool that lets you create pixel-perfect, responsive, and dynamic digital experiences for your customers, partners, and employees. You can use Experience Builder to customize the layout, branding, navigation, components, pages, and permissions of your site. You can also preview and publish your changes, and monitor the performance and usage of your site. References: Create the Manufacturing Partner Template and Add Partner Users - Salesforce, Create an LWR Site in Experience Cloud - Salesforce Developers, Experience Builder - Salesforce Help

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

To maintain data integrity in Manufacturing Cloud, the administrator should limit the mass update capability for Sales Agreements to only System Administrators. This will prevent accidental or malicious changes to the Sales Agreement data by other users. To do this, the administrator can clone the standard Manufacturing Sales Agreements permission set, which grants access to the Sales Agreement object and related fields. Then, the administrator can deselect the mass update for Sales Agreements permission in the cloned permission set, and assign it to all non-System Administrator users. This way, only System Administrators can perform mass updates on Sales Agreements, while other users can still view and edit individual records. References: Sales Agreement Permissions, Mass Update Sales Agreements

 Account and market growth percentages are values that account managers can enter to indicate the expected growth of their account and the market for their products in the upcoming period. These values are used in the forecast formula to calculate the forecast quantity and revenue for future periods. The new values are used in forecasting the future periods only when the account and market growth percentages are part of the forecast formula. If the forecast formula does not include these values, then editing them will not affect the forecast calculation. References: Create Accurate Account Forecasts, Configure Forecast Metrics and Formulas

 The recommended method for an administrator to enable the full functionality of the Service Console for Manufacturing app is to grant the Service Agents the Service Console for Manufacturing and Industry Service Excellence permission sets. These permission sets provide access to the Service Console for Manufacturing app and the components within it, such as the Customer 360 Timeline, the Asset Performance Monitor, and the Warranty Claims Manager1. Adding the Service Console for Manufacturing component to the Service Console Lightning Page Layout or creating a custom permission set are not necessary steps to enable the app functionality2. References: Set Up Users and Permissions for Manufacturing Cloud, Learn About Service Console for Manufacturing

 A sales agreement can be renewed only when it is in the renewal period, which is defined by the number of days before the end date of the agreement. A sales agreement that is expired or approved can be renewed if it is within the renewal period. However, a sales agreement that is activated cannot be renewed, because it means that the agreement is currently active and has not reached its end date or renewal period. References: Define Renewal Period for Sales Agreements, Renew a Sales Agreement.

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

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

The standard object that captures Type, Reason, and Account information for warranty claims is Claim. A Claim record represents a request made by a partner, dealer, or distributor to the manufacturer to repair, replace, or provide a refund for a defective asset1. The Claim object has fields such as Claim Type, Claim Reason, and Account Name that store this information2. References: How Warranty Claim Information Is Represented in Manufacturing Cloud, Claim Fields in Manufacturing Cloud

Question no 95

During the discovery phase, sales leadership at Universal Containers says that their run rate business is hard to forecast because their customer constantly orders more or fewer engine control units than contractually agreed upon. Which Manufacturing Cloud capability should a consultant recommend for managers to discuss these variances with sales reps and for sales reps to monitor their customers?

A. Leverage a Data Processing Engine (DPE) job to calculate the forecast deviation.

B. Use a formula field on the Sales Agreement Product Schedule object to calculate the forecast deviation.

C. Set up the CRM Analytics template app and leverage embedded dashboards for forecast deviation on the Account page.

Answer:B

The Sales Agreement Product Schedule object is used to track the planned and actual quantities of products that are part of a sales agreement. A formula field on this object can be used to calculate the forecast deviation, which is the difference between the planned and actual quantities. This can help managers and sales reps to monitor the performance of their run rate business and identify any variances from the contractual terms. The formula field can also be used to create reports and dashboards that show the forecast deviation by product, customer, or any other dimension. References: Sales Agreement Product Schedule, Forecast Deviation

One of the methods to calculate Actuals for sales agreements is to automatically derive them from direct orders. A direct order is an order that is created from the related list of a sales agreement record. A daily automated process calculates the product quantity fulfilled in each activated order, and then updates that quantity in the sales agreement. This method allows you to track the actual performance of your sales agreements based on the orders placed by your customers or partners. You can also use other methods to calculate Actuals, such as importing quantities from external sources, or using orders associated with contracts. References: Create Orders to Calculate Sales Agreement Actuals, How Are Sales Agreement Actuals Calculated?

To create sales agreements from historical data for a Manufacturing Cloud solution, a consultant must consider the following data items: Accounts, Orders, Order Lines, and Products. These are the core objects that are used to create and manage sales agreements in Manufacturing Cloud. Accounts represent the customers or partners that have sales agreements with the organization. Orders and Order Lines represent the actual sales transactions that are associated with the sales agreements. Products represent the items or services that are sold or purchased through the sales agreements. Invoices and Opportunities are not required for creating sales agreements from historical data, as they are not part of the sales agreement object model. Invoices are used to track the billing and payment status of the orders, while Opportunities are used to track the potential sales deals that may or may not result in orders. References: Sales Agreement Object Model, Create a Sales Agreement, Sales Agreement Fields

 The Analytics for Manufacturing App is a prebuilt app that includes dashboards to visualize and analyze data from various Manufacturing Cloud objects, such as sales agreements, account forecasts, account manager targets, and rebates. Before you can create the app, you need to ensure that your data meets some specific requirements, otherwise the app creation fails. One of the requirements is that at least one record must exist in each of the Manufacturing Cloud objects to be analyzed, such as Order, Sales Agreement, Account Forecast, and so on. This ensures that the app has some data to work with and can generate meaningful insights. The other requirements are related to record types, permissions, and field-level security1. References: Data Required to Create the Analytics for Manufacturing App, Set Up Analytics for Manufacturing, Deploy CRM Analytics for Manufacturing.

 Industry Service Excellence and Warranty Lifecycle Management Psl are the permission set licenses that the claims adjudicators need for this requirement. Industry Service Excellence gives users access to the Service Console app, which provides a unified view of all the claim-related data on a single page. Warranty Lifecycle Management Psl gives users access to the Warranty Lifecycle Management features, which enable users to manage warranty contracts, claims, and entitlements. The other options are not sufficient for this requirement. Service Console for Manufacturing does not include the Warranty Lifecycle Management features. Warranty Lifecycle Management Psl and Claims Management Foundation do not include the Service Console app. References: Permission Set Licenses, Set Up Users and Permissions for Manufacturing Cloud, Assign the Manufacturing Permission Sets to Users, Assign Users Permission Sets for Service Lifecycle Features in Manufacturing Cloud

A consultant should prepare a template with the requirements and their associated priority, and work with the client to evaluate each item. This is the best way to advance to the next step of the project, because it helps the consultant and the client to align on the scope, objectives, and expectations of the project. It also allows the consultant to understand the client’s business needs, challenges, and opportunities, and to prioritize the requirements based on their value and feasibility. By working collaboratively with the client, the consultant can also build trust and rapport, and ensure that the client is engaged and satisfied with the project outcome. References:

• Manufacturing Cloud - Salesforce
• Considerations for Working with Manufacturing - Salesforce

 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

 The first step for Manufacturing Cloud implementation is to enable Manufacturing Cloud features in Setup. This step allows you to access the Manufacturing Cloud objects, fields, tabs, and components in your org. You can enable Manufacturing Cloud features for Sales, Service, or both, depending on your business needs. To enable Manufacturing Cloud features, you need to have the Customize Application permission and the Manufacturing Cloud license assigned to you1. References: Enable Manufacturing Cloud Features

To conduct proper testing of Manufacturing Cloud, the end users need the following items:

• Sandbox access: A sandbox is a copy of the production environment that allows users to test changes and features without affecting the live data. Manufacturing Cloud offers different types of sandboxes for different testing purposes, such as learning, pre-release, and base12.
• Test data: Test data is a set of realistic and representative data that is used to simulate the actual business scenarios and workflows in Manufacturing Cloud. Test data can be created manually, imported from external sources, or copied from the production environment34.
• Process scripts: Process scripts are step-by-step instructions that guide the users through the testing scenarios and expected outcomes. Process scripts help to ensure that the testing is consistent, comprehensive, and aligned with the business requirements . References: Create a Manufacturing Cloud Trial Org, Try Manufacturing Cloud for Free, Create Test Data for Your Full Sandbox, Import Data into Your Org, [Create a Test Plan for Your Salesforce Implementation], [Test Your Salesforce Implementation].

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

 Data Processing Engine (DPE) Templates are used to customize the data model and calculations for account-based forecasting in Manufacturing Cloud. DPE Templates allow users to define the dimensions, metrics, and formulas for their forecasts based on their business needs. In this case, UC needs to customize the DPE Template to include the product category as a dimension, and the ordered quantity, revenue, shipped quantity, and revenue as metrics. UC also needs to specify the custom fiscal year and the weekly forecast frequency in the DPE Template. The other options are not relevant for this requirement. Sales Agreement Metrics are used to track the performance of sales agreements, not forecasts. Advanced Account Forecast Fact object is a standard object that stores the forecast data, not a customization option. References: Customize Data Processing Engine (DPE) Templates, Account-Based Forecasting in Manufacturing Cloud

The renewal days for sales agreement is a setting that defines the number of days before the end date of a sales agreement to mark the beginning of the renewal period. Users can renew a sales agreement only when the renewal period starts. This helps to plan ahead and negotiate better terms for the next sales agreement1. References: 1: Define Renewal Period for Sales Agreements | Salesforce Help2

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

To use the actual orders data for its sales agreements without bringing the data into Manufacturing Cloud, UC must select the Actuals Calculation mode as Automatically from orders through contracts in the Sales Agreement setup. This mode allows UC to calculate the actual quantities from the orders that are associated with the contracts linked to the sales agreements. A daily automated process derives and calculates the sales agreement actuals from the orders through contracts and updates the sales agreement records. This way, UC can avoid importing or syncing the actual orders data into Manufacturing Cloud and still use it for its sales agreements. References: Choose How Sales Agreement Actuals Are Calculated, How Are Sales Agreement Actuals Calculated?

Learn more

1

help.salesforce.com2

help.salesforce.com3

trailhead.salesforce.com4

trailhead.salesforce.com

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 Sales Agreement List View is not selected in the Account Forecast Calculation Settings, no sales agreements will be considered when calculating the sales agreement metric values of account forecasts. This means that the account forecasts will only reflect the opportunity metric values, and not the sales agreement metric values. To include the sales agreement metric values in the account forecasts, you need to select a sales agreement list view that defines which sales agreements to use for the calculations. References: 1: Configure Account Forecast Calculation Settings - Salesforce

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.

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

 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

According to the Salesforce Manufacturing Cloud documentation, you can use the Formula Builder on the Account Forecasting page in Setup to create formulas for forecast calculations. You can define your own formulas for quantity and revenue based on sales agreements, orders, opportunities, and account metrics. You can create either a single formula for all periods, or multiple formulas for different period ranges. If the forecast display period is 12 months, you can create up to 12 formulas. However, if you want to calculate an account based forecast for the next 13 months, you need to create separate formulas for periods 1-12 and period 13, because the Formula Builder does not support more than 12 periods in a single formula. This way, you can ensure that the forecast calculations are accurate and consistent for each month. References: Build Formulas to Calculate Forecast, Configure Forecast Metrics and Formulas

 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 Account Manager Target object represents a target created by an account manager for a fiscal year, measure, and target value1. To measure the account managers on a CSAT target, the admin should add a picklist value on the Measure field with Label = CSAT and add Measure Type = Other, on the Account Manager Target object. This way, the account managers can create and assign targets for the CSAT measure to their direct reports2. The other options are incorrect because they either use the wrong object, field, or value for the CSAT target. References: Create and Assign Targets, Set Up and Configure Account Manager Targets, Discuss Salesforce Manufacturing-Cloud-Professional Exam Topic 1 Question 19, Manufacturing Cloud Developer Guide

To ensure that rebates are paid out only on invoices that have status paid, an admin can create a custom field in the Transaction Journal object, and copy the invoice status data from the source system into that field. Then, the admin can use that field as an eligibility condition in the Rebate Types, so that only transactions that match the criteria are included in the rebate calculation. This way, the admin can avoid paying rebates on invoices that are not yet paid, or that are canceled, refunded, or disputed. References: [Rebate Management - Salesforce Help], Create and Manage Rebate Types - Salesforce Help, Create and Manage Transaction Journals - Salesforce Help, Create and Manage Data Processing Engine Definitions - Salesforce Help, Rebate Management for Manufacturing Cloud - Salesforce Help