Manufacturing-Cloud-Professional Manufacturing Cloud Accredited Professional Exam (WI25) Question and Answers

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

To address the issue of the Claims page not showing when the warranty for the asset ends, the consultant should recommend registering the asset by creating the Asset record and the Asset Warranty Terms record. This ensures that all relevant warranty information, including the end date, is captured and displayed as part of the claims processing workflow, thus providing warranty claim adjudicators with the complete data needed for effective claims management.

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

1blob:https://www.bing.com/e583e63c-ea5e-4ca3-b55e-96efd816d75b

help.salesforce.com2blob:https://www.bing.com/e583e63c-ea5e-4ca3-b55e-96efd816d75b

help.salesforce.com3blob:https://www.bing.com/3959af30-c1da-43a0-b081-817eccbfaa8d

trailhead.salesforce.com4blob:https://www.bing.com/3959af30-c1da-43a0-b081-817eccbfaa8d

trailhead.salesforce.com

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

 A consultant should use an external object to access account order information from an ERP system. An external object is similar to a custom object, but the record data is stored outside the Salesforce organization. By using external objects, the consultant can access the order data in real time via web service callouts, without replicating the data in Salesforce. This way, the sales teams can view the current state of the order information related to an account, without wasting storage and resources keeping data in sync1. A standard Order object or a custom object would require copying the order data from the ERP system to the Salesforce organization, which is not the desired solution for UC. References: 1: External Objects2

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

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

Account Forecasting is a prerequisite feature for using the Advanced Account Forecasting Analytics for Manufacturing app. This app allows users to create holistic forecasts across multiple dimensions and horizons, and analyze their forecast data using dashboards. To enable Account Forecasting, users need to have the Manufacturing Cloud permission set license and the Manufacturing Cloud permission set assigned to them. The other options are not relevant for this requirement. Sales Agreements and Orders are not required for creating and sharing the app, although they can be used as data sources for the forecasts. References: Create Holistic Forecasts with Advanced Account Forecasting, Set Up Users and Permissions for Manufacturing Cloud, Use Advanced Account Forecasting Analytics for Manufacturing

 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

In setting account manager targets, the combination of measures that creates these targets includes the Time period, Accounts, and Products. This approach allows sales managers to allocate target details appropriately by considering the specific time frame, the accounts managed by each account manager, and the products involved. This multi-dimensional approach to target setting enables a more nuanced and effective allocation of sales targets, catering to the diverse aspects of sales operations.

n: Sales Agreements are the standard feature in Manufacturing Cloud that allow users to track and manage their run-rate or long-term negotiated business. Sales Agreements unify the data from ERP and order management systems with the contract terms, including planned volumes and revenues, so that both operations and account teams can have a 360-degree view of the customer. Sales Agreements also enable users to forecast their run-rate business more accurately and efficiently by using account-based forecasting. Opportunities are used to track new business or one-off business, not run-rate business. Opportunity or Sales Agreements is not a valid option, as they are two different features. References: What Is Manufacturing Cloud?, Forecast Your Run-Rate and New Business with Account-Based Forecasting, Salesforce Launches Manufacturing Cloud—Aligning Sales and Operations to Deliver More Transparent and Predictable Business Outcomes, Salesforce Blog: Manufacturing Cloud

The Accounts Health dashboard allows a user to analyze revenue realization, length of relationship, and customer lifetime value across accounts. Revenue realization is the actual revenue as a percentage of planned revenue. Length of relationship is the duration between today and the start date of the first sales agreement with an account. Customer lifetime value is the total of revenue generated to date and revenue anticipated from the account. These metrics help the user to assess the performance and potential of each account and identify opportunities for growth or retention. References: Calculate Key Performance Indicators Using CRM Analytics, Calculating Customer Lifetime Value (CLV) With Salesforce, How to calculate customer lifetime value

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 forecast at the product hierarchy level, the system administrator needs to create a flow that modifies the Advanced Account Forecasting to include the product category as a custom dimension. The product category is a field on the product object that defines the hierarchy of products. By adding the product category as a custom dimension, the system administrator can enable the regional sales manager to view and adjust forecasts based on different product categories. The flow should use the Data Processing Engine to aggregate data from orders, opportunities, sales agreements, and other custom objects by product category, and then use the Calculate Advanced Account Forecast and Update Advanced Account Forecast Set Partner invocable actions to generate the forecasts. The flow should also assign the appropriate forecast set to the regional sales manager based on their role and region. References: Create Holistic Forecasts with Advanced Account Forecasting, Example: Generate Forecasts Across Multiple Regions with Advanced Account Forecasting, Calculate Account Forecasts Using Flows

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

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

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

When multiple active sales agreements contain the same product for the same account and time period, you can use custom logic to determine which sales agreement to link the order to. You can use the Sales Agreement Order Linking Apex class to implement your custom logic and override the default behavior of linking the order to the sales agreement that was activated last1. References:

Sales Agreements and Forecasting in Manufacturing Cloud

Set Up and Configure Sales Agreements

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

 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

The purpose of a detailed technical design document when implementing Manufacturing Cloud is to define specific details regarding how functionalities will be configured. This includes setting up features like the Actionable Relationship Center, Events and Milestones, and Intelligent Document Reader, some of which may require integration with external systems .

For further details and best practices, refer to the official Salesforce Manufacturing Cloud documentation:

Manufacturing Cloud Overview

Manufacturing Cloud Developer Guide

To accommodate Universal Chemicals' requirement to show agreed and delivered volume on each schedule and in actual figures for their liquid chemicals, a Manufacturing Cloud consultant should recommend creating custom fields for volume and total volume on the sales agreement objects. Additionally, a before save flow can be used to calculate the total volume based on these fields. Metric Mapping can then be utilized to display these metrics on the sales agreements, allowing for a comprehensive view of agreed, ordered, and delivered volumes, which is essential for accurate forecasting and management of liquid chemicals in various tank sizes .

 When using the mass update multiple values of a single metric of a sales agreement terms tab, the three actions that are available are: replace with, decrease by, and increase by. These actions allow the user to update the values of a metric across multiple periods and products in a sales agreement. For example, the user can replace the forecasted quantity of a product with a new value, or increase the discount percentage of a product by a certain amount. The other options, update with and multiply by, are not valid actions for mass update. References: Mass Update Account Forecast Action, Update Multiple Values in Advanced Account Forecasts

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

When embedding the Manufacturing Agreement Performance and Manufacturing Product Performance dashboards in a lightning page, it is recommended to set the dashboard's height to 120 pixels to ensure optimal display. Additionally, these dashboards can be embedded on any manufacturing cloud page layout without the need for setting up filters, offering flexibility in dashboard placement and enhancing user accessibility to critical performance data across various manufacturing cloud components .

The account manager looking to analyze business performance across various units and create a sales forecast based on customer accounts, products, and business units should use Advanced Account Forecasting. This solution generates baseline 360-degree forecasts considering opportunities, orders, sales agreements, historical orders, and other custom measures, providing a holistic view of business aspects .

Manufacturing Cloud supports two types of Experience Clouds: Customer and Partner. Experience Cloud is a digital experience platform that enables you to create secure websites, portals, and apps with connected data. Customer Experience Cloud allows you to build self-service portals, help centers, and storefronts for your customers, where they can access their account information, order products, manage cases, and more. Partner Experience Cloud allows you to build partner portals, channel management solutions, and microsites for your partners, where they can collaborate with you, manage leads and opportunities, access marketing campaigns, and more. Manufacturing Cloud also provides a standard Manufacturing Experience Cloud Template that includes two key functionalities: Sales Agreements and Account Based Forecasts. References: Experience Cloud | Salesforce DXP, What Is Experience Cloud?, Manufacturing Experience Cloud Template.

 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

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

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

To automate the process of showing actual orders in sales agreements, the consultant should navigate to the Sales Agreement Setup page and select an option from the Actuals Calculation section. This setup allows for the automatic calculation and display of actual quantities for each schedule when a sales agreement is active, thereby streamlining the process and ensuring the accuracy of data presented in sales agreements .

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

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.

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

 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

 The error “System.CalloutException: Unauthorized endpoint” indicates that the external endpoint is not whitelisted in Salesforce. To allow Apex callouts to access an external endpoint, the administrator or the developer must register the URL in Remote Site Settings. This is a security feature that prevents unauthorized access to external resources from Apex code. Creating a connected app for the external system or ensuring that the integration user has the necessary permissions to perform the callout are not sufficient to fix this error, as they do not address the issue of whitelisting the endpoint12. References: Apex Developer Guide: Making HTTP Callouts, Apex Developer Guide: Remote Site Settings

n: A stepped calculation method calculates a benefit structure based on the quantity of units sold within a specified range. For example, if you sell 150 units, and the first 100 units earn $0 per unit and the next 50 units earn $10 per unit, the total benefit is $500. This is different from the other calculation methods, which are:

Specified: Calculates a benefit structure based on a fixed amount or percentage for each unit sold.

Elapsed: Calculates a benefit structure based on the time elapsed since the start of the sales agreement.

Aggregate: Calculates a benefit structure based on the total quantity of units sold across all products in the sales agreement. References: What Is Manufacturing Cloud?, [Create a Benefit Structure for Sales Agreements]