Manufacturing-Cloud-Professional Questions and Answers

 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

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]

You can use apex triggers to populate a custom metric on the forecast grid. A custom metric is a field that you can add to the Account Product Forecast (APF) or Account Product Period Forecast (APPF) objects to display additional information on the forecast grid. For example, you can create a custom metric to show the profit margin or the cost of goods sold for each product. To populate a custom metric, you need to write an apex trigger on the APF or APPF object that calculates the value of the custom metric based on the data in the record. You can use the standard or custom fields in the APF or APPF object as inputs for the calculation. For example, you can use the Planned Quantity, Planned Revenue, and Product Cost fields to calculate the profit margin. You can also use the fields from the related objects, such as the Account, Product, or Sales Agreement, by using the relationship queries. For example, you can use the Account Name or the Sales Agreement Status fields to filter the records for the calculation. After writing the apex trigger, you need to deploy it to your org and activate it. Then, you can add the custom metric field to the forecast grid layout and see the values populated on the grid. References: Create Custom Metrics for Account Forecasts, Apex Developer Guide, Relationship Queries

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 access the Rebate analytics functionality in Tableau CRM for Manufacturing, you need two licenses: Manufacturing Analytics Plus and Rebates Management Add on. Manufacturing Analytics Plus is a license that enables you to use the Analytics for Manufacturing app, which provides out-of-the-box dashboards and reports for sales agreements, forecasts, targets, and rebates. Rebates Management Add on is a license that enables you to use the Rebate Management feature, which allows you to create and manage custom rebate programs, automate payouts, and review processes. Together, these licenses allow you to perform what-if analysis, monitor program performance, and collaborate with channel partners using Tableau CRM for Manufacturing. References: Rebate Management - Salesforce Help, Salesforce Manufacturing Cloud Rebates What-If | Tableau Exchange, Streamline Channel Sales with an Intelligent Rebate Strategy - Salesforce

Manufacturing Cloud is a solution that enables manufacturers to align their sales and operations teams, improve account-based forecasting, and drive business outcomes. One of the main challenges that Manufacturing Cloud addresses is the volatility of the manufacturing industry, which makes it difficult to plan and execute production and distribution efficiently. By gaining visibility into the entire value chain, manufacturers can improve their forecast accuracy, collaborate with their stakeholders, and respond to changing customer needs and market conditions. References: What Is Manufacturing Cloud?, Inside Salesforce’s New Trends in Manufacturing Report

 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

 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

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

https://www.salesforce.com/products/manufacturing-cloud/overview/

Actuals are the quantities of products that have been fulfilled or shipped to the customer as part of a sales agreement1. Manufacturing Cloud calculates actuals based on orders that are associated with a sales agreement2. For an order to be included in the actuals calculation process, the following three conditions need to be fulfilled23:

The order needs to have Status = Activated. Only activated orders are considered for actuals calculation. Draft orders are not included.

The date in the Order Date field should be in the past. Only orders with a start date that is on or before the current date are considered for actuals calculation. Future orders are not included.

The Sales Agreement field needs to be populated on the order. Only orders that have a reference to a sales agreement record are considered for actuals calculation. Orders that are not linked to a sales agreement are not included.

https://help.salesforce.com/s/articleView?id=sf.sa_admin_actualscalc_task.htm &language=en_us&type=5

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

For integrating order data from an ERP system into Sales Agreements in Salesforce, the best practice is to create specific permission sets and possibly permission set groups that grant the necessary permissions, including write access to custom objects. These permission sets should then be assigned to the integration user account. This approach ensures that the integration user has precisely the access needed without the broad permissions that would come with using a Salesforce administrator account. It also allows for more granular control and security by limiting permissions to only those necessary for the integration's functionality.

Benefit mappings are used to define the product dimensions for a rebate benefit. Product dimensions are the criteria that determine which products are eligible for a rebate benefit. For example, you can create a product dimension based on product family, product line, or product category. You can also create custom product dimensions to suit your business needs1. To create a product dimension for a rebate benefit, you need to add a benefit mapping related list to the benefit record and specify the dimension type and values2. References: 1: Define Product Dimensions for Rebate Benefits | Salesforce Help3, 2: Create Benefits and Activate a Program Unit | Salesforce Trailhead4

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 facing a deployment error indicating that the Sales Agreement object does not exist in the target environment, the first step the administrator should take is to ensure that Sales Agreements are enabled in the production organization. This is a crucial prerequisite for deploying Sales Agreements-related changes and functionalities from a development sandbox to a production environment, as the absence of enabled Sales Agreements in the target environment can lead to deployment failures .

 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

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

 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 ensure key account managers can generate forecasts using list views for account forecasts, it's crucial that either "All users can see this list view" or "Share list view with groups of users" is selected for the list views. This setting allows for the appropriate visibility and access required for generating accurate and comprehensive forecasts. This is essential for maintaining the integrity and effectiveness of the forecasting process within Salesforce Manufacturing Cloud .

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

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 .

 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

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

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

Salesforce Manufacturing Cloud can be integrated with Oracle ERP orders data using two options:

Use an AppExchange ISV solution: This option allows you to leverage existing solutions from independent software vendors (ISVs) that are available on the Salesforce AppExchange platform. These solutions are designed to simplify and automate the integration process between Salesforce and Oracle ERP systems. Some examples of AppExchange ISV solutions are rSTAR, DBSync, and Jitterbit.

Use API integration with custom logic: This option allows you to use the Salesforce APIs and the Oracle ERP APIs to create custom logic for integrating the orders data between the two systems. You can use any programming language or tool that supports REST or SOAP web services to build the integration logic. You can also use the MuleSoft Accelerator for Manufacturing, which is a prebuilt integration solution that connects Salesforce Manufacturing Cloud with Oracle ERP Cloud1.

References:

ERP and Salesforce: Everything Manufacturers Need To Know

Integrate Salesforce.com with Oracle Integration Cloud

Oracle Cloud Using the Salesforce Adapter with Oracle Integration Cloud

All About Integrating Oracle ERP and Salesforce CRM-rSTAR Technologies

What Is Manufacturing Cloud? - Salesforce

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

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

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

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

 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

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 allow the Service Agents to access the latest updates to a sales agreement when navigating from the customer interaction related to the account, the Manufacturing Cloud consultant should recommend adding the Sales Agreement related list to the Account record page in Lightning App Builder. This way, the Service Agents can see the sales agreements associated with the account and view their status, terms, and schedules. The Sales Agreement related list is available for the Account object by default and can be added to the Account page layout using the Lightning App Builder. References: Sales Agreements Overview, Customize Record Pages with the Lightning App Builder

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

 The admin at badger power can set up an eligibility criteria for this rebate type with activity Date >= Jan1 and <= Jan31. This option allows the admin to specify the date range for which the rebate type applies to the transactions. The other options are either not possible or not sufficient to achieve the desired result. For example, setting up a new rebate program with a single payout period for Jan does not ensure that the rebate type is valid only for transactions completed in January. Setting the rebate type to active on Jan1 and inactive on Jan31 does not prevent the rebate type from being applied to transactions that occurred before or after January. Using the effective date on rebate type does not specify the end date for the rebate type validity. References: Eligible and Applied Rebate Types on a Transactional Object, Common Rebate Types