Manufacturing-Cloud-Professional Manufacturing Cloud Accredited Professional Exam (WI24) Questions and Answers

The Mobile User permission is required for users to access Salesforce features on their mobile devices, such as the Salesforce app. This permission enables users to log in to the app and sync data between their devices and Salesforce. Therefore, when preparing and conducting testing for Manufacturing Cloud for mobile, it is important to assign the Mobile User permission to the test users, so that they can view and approve sales agreements on their mobile devices. References: [Salesforce Mobile App Basics], [Assign the Mobile User Permission]

A sales agreement can have a maximum of 1500 products or product categories. If you want to increase the limit, you need to contact Salesforce Customer Support. Note that having a large number of products or categories and schedules can affect system performance. References: Considerations for Working with Manufacturing

Sales agreements are the core objects of Manufacturing Cloud for Sales. They represent the negotiated terms and conditions between a manufacturer and a customer or partner for run-rate or long-term business. Sales agreements have an out-of-the-box Submit for Approval quick action that allows users to initiate an approval process for the sales agreement record. This quick action can be customized to fit different approval scenarios and workflows.

 Adjusting the forecast formula to reflect opportunity probability will trigger the regeneration of all forecasts. This is because changing the forecast formula will affect the existing forecasts and require them to be deleted and recreated based on the new formula. The regeneration process may take some time depending on the number of accounts and products involved2. The regeneration will apply to all forecasts, regardless of their status, because the forecast formula is not specific to a particular status. Therefore, both active and inactive forecasts will be regenerated3. References: Change the Forecast Formula, Account Forecast Status

To make the support process easier for the service agents, the consultant should recommend enabling the Service Console for Manufacturing app. This is a prebuilt Lightning app that provides a unified view of all the information related to contacts and accounts, such as cases, assets, warranties, and claims. The app also includes components and tools that help the service agents to manage and resolve issues faster and more efficiently. The app can be customized and configured to meet the specific needs of the service agents and the business. References: Set Up and Configure Service Console for Manufacturing, Use Service Console for Manufacturing

The ‘Delete sales agreement’ profile permission allows users to delete sales agreements that are not active. Only users with this permission will see the ‘Delete’ option on the sales agreement record header. Account owners or other users without this permission cannot delete sales agreements, regardless of their status. Sales agreements with any status, including active ones, can be deleted by users with this permission, unless they have associated products. References:

• Set Up and Configure Sales Agreements
• Delete a Sales Agreement

Customers Health dashboard allows a user to analyze revenue realization, length of relationship, and customer lifetime value across accounts. Customers Health dashboard is part of the Actionable Relationship Center (ARC) feature in Manufacturing Cloud, which provides a 360-degree view of customer health and engagement. Customers Health dashboard shows key metrics such as revenue realization rate, average length of relationship, average customer lifetime value, and customer churn rate. It also allows the user to filter the accounts by various dimensions, such as industry, region, product family, and account owner. Customers Health dashboard helps the user to identify the most valuable and loyal customers, as well as the customers who are at risk of attrition or dissatisfaction. References:

• Actionable Relationship Center, Salesforce Help Docs
• Customers Health Dashboard, Salesforce Help Docs
• Calculating Customer Lifetime Value (CLV) With Salesforce, Salesforce Ben Blog
• Data Cloud for Marketing, Salesforce Website

The start period is the number of periods before the current period that the forecast should include. In this case, the current period is Feb 2024, and the organization wants to start forecasting from Jan 2024, which is one period before. Therefore, the start period value should be 2. References: Advanced Account Forecasting with Manufacturing Cloud, Set Up Dimensions and Period Groups

To access the Rebate analytics functionality in Tableau CRM for Manufacturing, a user needs two licenses: Manufacturing Analytics Plus and Rebates Management Add on. Manufacturing Analytics Plus is an add-on license that enables the user to access the CRM Analytics for Manufacturing app, which includes prebuilt dashboards and datasets for manufacturing use cases, such as account forecasting, sales agreement performance, and rebate management. Rebates Management Add on is another add-on license that enables the user to access the Rebate Management functionality, which allows the user to create, manage, and analyze incentive programs for channel partners. The Rebate analytics functionality is an independent module in CRM Analytics for Manufacturing that requires both licenses, as it provides AI-powered insights into rebate program performance and ROI. The other options are not correct, as they either refer to different licenses that are not specific to manufacturing or analytics, or they do not exist as licenses. References: Deploy and Use Rebate Analytics, Who Can Use Rebate Management?

When loading data into Sales Agreement, the recommended sequence is to load the Sales Agreement object first, then the Sales Agreement Product object, and finally the Sales Agreement Product Schedule object. This sequence ensures that the data is loaded correctly and the relationships between the objects are maintained. References: Salesforce Help: Load Data into Sales Agreement, Salesforce Trailhead: Create Sales Agreements

Rebate programs are used to define the terms and conditions of a rebate agreement between a manufacturer and an account. A rebate program can be applied to one or more accounts by adding them to the members related list on the rebate program. This way, the manufacturer can track the performance and payouts of each account under the same rebate program. References: Rebate Programs, Rebate Program Members

The forecast settings page is where the admin can configure the account forecast generation criteria, such as the forecast start period, the forecast formula, the forecast frequency, and the forecast display duration. The forecast start period is the first period for which the forecast is generated. The forecast formula is the expression that calculates the forecast value based on the sales agreement data. The forecast frequency is the time interval for which the forecast is generated, such as monthly, quarterly, or yearly. The forecast display duration is the number of periods for which the forecast is displayed on the account forecast component. Any changes to these settings will affect the forecast generation process and the forecast data. However, only three of these settings will trigger the regeneration of all the eligible accounts that satisfy the forecast generation criteria: the forecast start period, the forecast formula, and the forecast frequency. These settings are critical for determining which accounts, products, and periods are included in the forecast, and how the forecast value is calculated. Therefore, any changes to these settings will require the system to regenerate the forecast for all the accounts that meet the criteria, to ensure the accuracy and consistency of the forecast data. The other settings, such as the forecast adjustment period and the forecast display duration, will not trigger the regeneration of all the accounts, as they only affect the forecast adjustments and the forecast display, not the forecast generation. The forecast adjustment period is the period for which the user can make manual adjustments to the forecast value. The forecast display duration is the number of periods for which the forecast is displayed on the account forecast component. These settings can be changed without affecting the forecast generation process or the forecast data, as they only affect the user interface and the user input. References: [Configure Account Forecasts], [Account Forecast Settings]

To upload sales agreement data into Manufacturing Cloud, the administrator needs to follow a specific order of operations to ensure data integrity and avoid errors. The order of operations is based on the dependencies and relationships among the objects involved in sales agreements. The objects are:

• Sales Agreement: This object represents the negotiated business transaction between an account and a manufacturer. It contains information such as the account, the product level, the actuals calculation mode, the start and end dates, the status, and the approval process.
• Sales Agreement Product: This object represents the product that is part of the sales agreement. It contains information such as the product, the quantity, the revenue, and the metrics.
• Sales Agreement Product Schedule: This object represents the planned quantity and revenue for each product in each period of the sales agreement. It contains information such as the product, the period, the quantity, the revenue, and the metrics.

The administrator needs to insert the sales agreement records first, as they are the parent records of the sales agreement products and schedules. The administrator also needs to insert the sales agreement products before the sales agreement product schedules, as the schedules are the child records of the products. The administrator can use the Data Loader tool or the API to insert the data in batches. The administrator can also use the Mass Update Sales Agreement action to update the sales agreement data in bulk1.

To enable a phased rollout scenario, the consultant can deploy the new functionality to the production org and assign the Manufacturing Cloud permission set to the users who are part of the rollout. This way, only the designated users can access the Sales Agreements tab and functionality. The other users can continue to use the standard Sales Cloud or Service Cloud features without any disruption. References: Salesforce Manufacturing Cloud Implementation Guide, page 25

Manufacturing Cloud can calculate Actuals for sales agreements automatically from direct orders, which are orders that are not associated with a contract or a quote. This method allows you to track the actual business performance of your sales agreements without relying on contracts or quotes. You can also use other methods to calculate Actuals, such as manually using API upload orautomatically from contracts through orders, but these are not the options given in the question. References: Salesforce Help: Calculate Actuals for Sales Agreements

The mass update feature allows the user to update multiple values of a single metric of a sales agreement terms tab at once. This can save time and effort when making changes to the sales agreement performance or forecast data. The user can select one or more periods and one metric, and then choose one of the following actions to apply to the selected values:

• Replace with: This action replaces the selected values with a new value that the user enters. For example, the user can replace the forecast quantity of 100 units with 120 units for the selected periods.
• Decrease by: This action decreases the selected values by a percentage or an absolute amount that the user enters. For example, the user can decrease the forecast quantity by 10% or by 20 units for the selected periods.
• Increase by: This action increases the selected values by a percentage or an absolute amount that the user enters. For example, the user can increase the forecast quantity by 15% or by 30 units for the selected periods. The other options are not valid actions for the massupdate feature. There is no action called Update with or Multiple by in the mass update feature. The user can only use the actions that are available in the dropdown menu of the mass update feature. References: [Mass Update Multiple Values of a Single Metric], [Sales Agreement Term Fields]

To create a CSAT target for account managers, the admin needs to add a picklist value on the Measure field of the Account Manager Target object. The Measure field determines the type of target value that the account manager needs to achieve, such as revenue, quantity, or customer satisfaction. The admin also needs to add a Measure Type of Other to indicate that the target is not currency-based. The other fields and objects mentioned in the options are not relevant for this requirement. References: : Create and Assign Targets Unit | Salesforce Trailhead : Set Up and Configure Account Manager Targets - Salesforce : Manufacturing Cloud Developer Guide - Salesforce Developers

According to the Manufacturing Cloud Developer Guide1, the following objects do not support triggers:

• Account Forecast (AF): Represents the rolling forecast record of a particular account. The forecast is prepared using data directly from sales agreements, orders, and opportunities. This object is available in API version 47.0 and later1.
• Account Product Forecast (APF): Represents the cumulative values for planned quantities, opportunities, and orders of a sales agreement for a given product across all periods in that rolling time period. This object is available in API version 47.0 and later1.

References: 1: Manufacturing Cloud Standard Objects

In Tableau CRM for Manufacturing, the user types that can be selected to receive credit for an order in the Tableau CRM configuration wizard when calculating actuals against account manager targets are:

• Opportunity Owner: The user who owns the opportunity that is associated with the order. This option is useful when you want to track the performance of the sales reps who closed the deals that resulted in the orders2.
• Custom Lookup Field for a user on Account: The user who is referenced by a custom lookup field on the account that is associated with the order. This option is useful when you want to track the performance of a specific role or function that is related to the account, such as a regional manager or a service agent2.
• Order Owner: The user who owns the order. This option is useful when you want to track the performance of the users who are responsible for fulfilling the orders2. References: Configure Tableau CRM for Manufacturing

To create and share the Advanced Account Forecasting Analytics for Manufacturing app, the administrator needs to enable Account Forecasting in the Manufacturing Cloud setup. Account Forecasting is a feature that allows users to generate and view forecasts based on various data sources and metrics. The Advanced Account Forecasting Analytics for Manufacturing app is a prebuilt Tableau CRM app that provides dashboards and insights into the account forecast data. If Account Forecasting is not enabled, the administrator cannot access the app or share it with other users. References: Set Up and Configure Account Forecasting, Use Advanced Account Forecasting Analytics for Manufacturing

Account Based Forecasting allows you to forecast your revenue based on the market growth and the account growth. The market growth is the expected increase or decrease in the market demand for your products or services. The account growth is the expected increase or decrease in your share of the market. To achieve a target growth of 10% when the market growth is 5%, you need to set the account growth to 5%, which means you expect to gain 5% more market share. Updating the account forecast or the market growth will not reflect the correct scenario. References: Account Based Forecasting, Forecast Revenue with Account Based Forecasting

Tableau CRM for Manufacturing is a set of prebuilt dashboards and datasets that provide insights into sales performance, account health, and sales agreement compliance. To ensure that users only see the data they are authorized to access, Tableau CRM for Manufacturing uses security predicates to filter the data based on the user’s profile and permissions. One of these security predicates is:

• Use Manager Hierarchy: This predicate filters the data based on the user’s position in the manager hierarchy. Users can only see the data for themselves and the users below them in the hierarchy. This predicate uses the ManagerId field on the User object to determine the hierarchy.

References: : [Tableau CRM for Manufacturing Security Predicates]

Loading data into Manufacturing Cloud requires following a specific order of operations to ensure data integrity and avoid errors. The order of operations is based on the dependencies and relationships among the objects involved in Manufacturing Cloud. Accounts, Contacts, and Products are the basic objects that need to be loaded first, as they are referenced by other objects. Sales Agreements and Orders are the objects that represent the planned and actual business transactions, respectively. Sales Agreements need to be loaded before Orders, as Orders can be associated with Sales Agreements. Orders also need to be loaded after Products, as Orders contain Order Products that reference Products. References: What Is Manufacturing Cloud?, Importing Order Data

A System Integration Testing (SIT) environment is used as an environment to perform system-to-system testing. System-to-system testing is the process of verifying that different systems can communicate and exchange data correctly and reliably. For example, in Manufacturing Cloud, system-to-system testing can be used to check the integration of Salesforce with other systems, such as ERP, CRM, or PLM, using tools like MuleSoft. System-to-system testing can help to identify and resolve any issues or errors in the integration, such as data quality, security, performance, or functionality. A SIT environment is not used as a backup and archive of production configuration and data, nor as a development environment to configure and build new applications. References: : [Manufacturing Cloud Implementation Guide - Salesforce] : [System Integration Testing - Salesforce]

When an org hits the account product period forecast record limit, new products cannot be added to account forecasts automatically. This means that when a user recalculates a single account forecast or all account forecasts, the new products are not added to the forecast. Also, if a user manually adds a new product to an account forecast, the product will not be included in the forecast calculations. The user will see a warning message indicating that the product is not calculated. To resolve this issue, the user can contact Salesforce Customer Support to request an increase in the limit. References: Salesforce Help: View the Data Volume Usage, Defined Limits, and the Percentage of Limit Used for Account Forecasts, Salesforce Help: Considerations for Working with Manufacturing

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 choose from three actions when using this function:

• Increase By: This action increases the selected values by a specified amount or percentage. For example, you can increase the planned quantity of a product by 10% or by 100 units1.
• Decrease By: This action decreases the selected values by a specified amount or percentage. For example, you can decrease the price of a product by 5% or by $0.501.
• Replace With: This action replaces the selected values with a new value. For example, you can replace the status of a term with Approved or Expired1. References: Mass Update Values in Sales Agreement Terms

Sales agreements are a standard feature of Manufacturing Cloud that serves as a starting point to manage run-rate business. Run-rate business refers to the recurring revenue and volume generated from long-term contracts or agreements with customers. Sales agreements allow account managers to create and manage the terms and conditions of these agreements, such as the products, prices, discounts, and quantities. Sales agreements also provide visibility into the planned and actual order volumes and revenues, and enable account managers to make adjustments based on changing customer demand or market conditions. Sales agreements can also be used to generate forecasts for the run-rate business and compare them with the new business from opportunities. References: Sales Agreements, Get Started with Manufacturing Cloud

 Partner Visit Management is a Manufacturing Cloud feature that helps users to plan, execute, and track their visits to channel partners, such as dealers and distributors. Users can create visit plans that define the objectives, agenda, and tasks for each visit, and assign them to partner account teams. Users can also log visit reports that capture the outcomes, feedback, and follow-up actions from each visit. This can help users to work closely with their partners, monitor their performance, provide support, and drive partner engagement

List views for account forecasts are used to filter the accounts that are included in the forecast calculations. By default, only the accounts that are owned by the user or are shared with the user are considered for the forecast. However, an admin can create and share list views with a group of users, such as account managers, to allow them to generate forecasts based on the accounts in the list view. This way, the admin can control which accounts are relevant for the forecast and which users can access them. The other options are not valid for account forecasts, as they either make the list view visible to all users, which defeats the purpose of filtering, or they limit the visibility to account owners or users above the hierarchy, which may exclude some users who need to see the forecast. References: Configure Account Forecasts, [Work with List Views in Lightning Experience]

The Program Rebate Type Benefit object supports custom fields for rebate program(s) analysis in Tableau CRM for Manufacturing. This object stores the benefit tiers for each rebate type in a rebate program. You can create custom fields on this object to capture additional criteria or attributes for the benefits, such as product category, region, or industry segment. You can then use these custom fields to filter, group, or aggregate the rebate data in the Analytics for manufacturing app1. References: Rebate Management Standard Objects

Manufacturing Cloud supports two types of Experience Clouds: Customer and Partner. Customer Experience Cloud allows you to create branded, personalized, and connected digital experiences for your customers across web, mobile, and social channels. Partner Experience Cloud allows you to create a self-service portal for your channel partners, such as dealers, distributors, reps, and resellers, where they can collaborate with you on leads, sales agreements, forecasts, and more. Both types of Experience Clouds help you to increase customer and partner satisfaction, loyalty, and retention.

Manufacturing Cloud provides a predefined manufacturing partner template that can be used to set up a secure site for collaboration with channel partners. The template includes features such as leads, sales agreements, forecasts, and dashboards that partners can use to work with the manufacturer. The template also allows the manufacturer to control the access and permissions of the partners based on their roles and profiles. References: : Engage with Your Partners Unit | Salesforce Trailhead : What Is Manufacturing Cloud? - Salesforce

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 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

 According to the Salesforce Manufacturing Cloud documentation, to display the current sales agreement data in tableau CRM for manufacturing, you need to add the sales agreement object to the data flow and update the data flow. The data flow is a set of instructions that defines how data is extracted, transformed, and loaded into the app. If you do not add the sales agreement object to the data flow, the app will not have access to the sales agreement data. If you do not update the data flow, the app will not reflect the latest changes in the sales agreement data1. References: 1: Set Up the CRM Analytics App for Manufacturing Cloud

Learn more

1blob:https://www.bing.com/75924f7d-ce10-4904-b3d2-4996b3dcdca7

developer.salesforce.com2blob:https://www.bing.com/c30db82f-7512-4b86-8ad0-68f8704ae728

trailhead.salesforce.com

• Account Manager Targets allow UC to set and track quantity and revenue targets at the manager level, and distribute them to their team members and accounts1.
• Sales Agreements allow UC to manage run-rate or long-term negotiated business with their customers, and track the order realization against the agreed terms1.
• Advanced Account Forecasting allow UC to forecast their sales on a rolling 12-month basis using data from opportunities, sales agreements, past orders, and market data1.
• CRM Analytics for Manufacturing App is a prebuilt app that provides insights into sales performance, account health, and customer satisfaction, but it does not address the requirements of UC2.
• Account Based Forecasting is a feature that allows UC to forecast their sales based on account hierarchy, but it does not use data from sales agreements or market data3.

References:

• What Is Manufacturing Cloud? - Salesforce
• CRM Analytics for Manufacturing App - Salesforce
• Account Based Forecasting - Salesforce

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

The best way to reassure the client that the data has been accurately calculated is to launch the calculations of the Advanced Account Forecast and compare the values with the legacy system. This will ensure that the forecast metrics, such as planned revenue, actual revenue, forecast quantity, and forecast revenue, are consistent and correct. The administrator can use the Data Processing Engine templates to configure the calculations and run them manually or on a schedule1. The administrator can also view the forecast results in the Accounts Health dashboard or the Account Forecast tab2. Using Data Loader to generate a .csv file and manually compare it to import files is not a reliable method, as it may introduce errors or inconsistencies in the data format or values. Requesting the users to verify the Advanced Account Forecast values of their accounts is not a feasible method, as it may be time-consuming, impractical, or inaccurate, depending on the number and complexity of the accounts. References: Learn How Forecast Data Is Created, View and Adjust Forecasts

 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

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

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

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

According to the Salesforce Manufacturing Cloud documentation, the ‘Delete sales agreement’ profile permission allows users to delete an active, approved, canceled, or expired sales agreement. However, they can only delete a sales agreement if it doesn’t have any active orders associated with it. Only users with this permission will see the ‘Delete’ option on the sales agreement record header. Account owners or other users without this permission will not see the ‘Delete’ option. The status of the sales agreement does not affect the ability to delete it, as long as there are no active orders1. References: 1: Delete a Sales Agreement - Salesforce

 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

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.

you do not want to bring actual orders data into Salesforce, you can use the Actual Orders API to manually calculate the actual quantities for sales agreements. This option allows you to use external data sources to update the actuals in Salesforce without creating orders or contracts. You can also use the Actual Orders API to refresh the actuals calculations for sales agreements for current and future periods1. References: 1: Refresh Actuals Calculation Action | Manufacturing Cloud Developer Guide | Salesforce Developers2

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

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

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

The Advanced Account Forecast object is used to track the expected and actual order values for each account and product family. It allows field reps to compare the forecasted and actual order values for each account and product family, and update them as needed. The Advanced Account Forecast object also enables field reps to collaborate with their distributors and align on the sales agreements, orders, and brand-promotion campaigns12. References: Meet Manufacturing Cloud, Strengthen Relationships with Partners

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

Account Manager Targets are a feature of Manufacturing Cloud that allows you to set and track sales goals for your account managers based on product volume, revenue, or any other custom measure. You can assign targets to individual account managers or to teams, and monitor their progress and performance over time. Account Manager Targets are supported for both standard fiscal year and custom fiscal year, which means you can align your targets with your company’s fiscal calendar. You can also use Account Manager Targets with or without a forecast calendar, which is another feature of Manufacturing Cloud that helps you create and manage forecasts for your accounts and products. References: Account Manager Targets in Manufacturing Cloud, Enable Account Manager Targets, What Is Manufacturing Cloud?

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 upload sales agreement data into the system, the administrator needs to follow these steps in order:

• Insert Sales Agreements: This creates the sales agreement records with the basic information such as account, contact, start date, end date, and status.
• Insert Sales Agreement Products: This adds the products that are part of the sales agreement, along with the planned quantity and revenue for each product.
• Insert Sales Agreement Product Schedule: This specifies the schedule for each product, such as the frequency, start date, end date, and quantity for each period.

The other options are not correct because they involve updating the sales agreement data instead of inserting it. Updating the data requires the data to be already present in the system, which is not the case for a new implementation. Also, updating the sales agreement product schedule is not necessary if the schedule is inserted correctly in the first place. References: SalesAgreement | Manufacturing Cloud Developer Guide, SalesAgreementProduct | Manufacturing Cloud Developer Guide, SalesAgreementProductSchedule | Manufacturing Cloud Developer Guide, Import Data into Manufacturing Cloud

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

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

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

The standard Manufacturing Experience Cloud Template is a preconfigured community template that provides a branded and personalized portal for your customers, partners, and distributors. It includes two key Manufacturing Cloud functionalities: Sales Agreements and Account Based Forecasts. Sales Agreements allow you to manage and track your run-rate business with your customers and partners, including pricing, volumes, and order realization. Account Based Forecasts enable you to create and update demand forecasts based on sales agreements, opportunities, and other inputs, and share them with your internal and external stakeholders. The standard Manufacturing Experience Cloud Template also includes other features, such as account and contact management, opportunity management, order management, case management, and reports and dashboards. References: Manufacturing Experience Cloud Template, Sales Agreements, Account Based Forecasts.

Learn more

1blob:https://www.bing.com/9145ca9c-9574-49a8-bd06-ffadfea02c49

salesforce.com2blob:https://www.bing.com/f3452c21-3ec3-44c7-aaa6-e2d93879a949

help.salesforce.com3blob:https://www.bing.com/ce0e6e36-cc65-4ae9-9e36-2539f6a982ba

cyntexa.com

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

• To configure forecasting in Manufacturing Cloud, UC needs to create and configure forecast sets, which are the primary building blocks for generating forecasts1.
• A forecast set contains information such as the forecast period, the forecast fact object, the forecast frequencies, the data processing engine definitions, the forecast dimensions, and the forecast measures1.
• UC has two different divisions with different forecasting needs, so they need to create two forecast sets, one for each division2.
• Each forecast set needs to have a different period group, which defines the time periods for forecasting. For the stock parts division, UC needs a monthly period group, and for the engineered-to-order parts division, UC needs a quarterly period group2.
• Each forecast set also needs to have two forecast metrics, which are the measures that UC wants to forecast. In this case, UC wants to forecast revenue and quantity for both divisions2.
• The other options are incorrect because they do not match the requirements of UC. Option B would create only one forecast set, which would not allow UC to differentiate between the two divisions. Option C would create only two forecast metrics, which would not allow UC to forecast both revenue and quantity.

References:

• Create and Configure Forecast Sets - Salesforce
• Configure Forecast Sets Unit | Salesforce Trailhead

To test Manufacturing Cloud features on mobile devices, the test users need to have the Mobile User permission assigned to them. This permission enables them to access the Salesforce mobile app and use the features that are available on mobile, such as viewing and approving sales agreements1. Sales Agreement features are available on mobile devices, and approvals can be done via the mobile app or email2. When testing Manufacturing Cloud for mobile, a Wi-Fi connection is not required, but it is recommended for better performance3. References: Automated Testing with the Salesforce Mobile App & Appium, Sales Agreement Management, Online Testing Cloud for Salesforce Websites

 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

 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

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

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.

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

Data Processing Engine (DPE) is a feature of Rebate Management that allows you to transform data that is available in your Salesforce org and write back the transformation results as new or updated records. You can use DPE to process data for standard and custom objects. Rebate Management has DPE templates that you can clone and customize to suit your business needs. The templates either help you to aggregate transactions by different criteria, or help you to manage other rebate processes. The out-of-the-box DPE jobs in Rebate Management use the templates to query, extract, filter and aggregate journal transactions based on the eligibility criteria and calculation definitions of the rebate types. The aggregated data is then stored in the Rebate Member Product Aggregate object, which is used to calculate the payouts for the program members. References: Data Processing Engine in Rebate Management | Salesforce Trailhead Module, Data Processing Engine Templates with Rebate Management - Salesforce, Data Processing Engine | Rebate Management Developer Guide | Salesforce Developers, Data Processing Engine, Batch Management, and Invocable Actions | Rebate Management Developer Guide | Salesforce Developers