Manufacturing-Cloud-Professional Manufacturing Cloud Accredited Professional Exam Questions and Answers

 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

According to the Salesforce Manufacturing Cloud documentation, to apply a rebate program to more than one account, you need to add each account to the members related list on the rebate program. This way, you can enroll multiple accounts as members of the same rebate program and track their transactions and payouts. You can add one account at a time, or use an existing Accounts list view to enroll multiple members. You can also enroll an account in multiple rebate programs if needed1. References: 1: Enroll Members to a Rebate Program

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

 According to the Salesforce Manufacturing Cloud documentation1, the Account Forecast Adjustments (AFA) and Account Forecast (AF) objects do not support triggers. These objects are used to store the manual adjustments and the rolling forecast records of a particular account, respectively. The other two objects, Account Product Period Forecast (APPF) and Account Product Forecast (APF), do support triggers. These objects are used to store the quantity and revenue information of a product in a particular time period and the cumulative values for a product across all periods, respectively. References: Manufacturing Cloud Standard Objects

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?

A security predicate is a filter that restricts access to data based on user attributes. In Tableau CRM for manufacturing, you can use the Manager Hierarchy security predicate to limit data access based on the user’s manager. For example, if you want to show only the sales agreements that belong to the user or their direct reports, you can use the Manager Hierarchy security predicate with the ManagerId field. This way, each user can see only the data that is relevant to them and their team. References: Add Row-Level Security with a Security Predicate, Developing and Managing Tableau CRM Assets in Production

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

 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

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

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

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

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

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

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

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

Manufacturing Cloud provides some default automation actions that can be used in flows and process builders to streamline the forecasting process. These actions are1:

• Calculate Advanced Account Forecasts: This action calculates the forecast values for the advanced account forecast records based on the forecast set, forecast type, and time period. It can be used to generate forecasts for product categories or key revenue measures.
• Recalculate Forecasts Actions: This action recalculates the forecast values for the account forecast records based on the forecast set, forecast type, and time period. It can be used to update forecasts for run-rate or new business.
• Recalculate Account Manager Targets: This action recalculates the target values for the account manager target records based on the forecast set, forecast type, and time period. It can be used to update targets for account managers based on their assigned accounts and products.

The other options are not default automation actions provided by Manufacturing Cloud. They are either custom actions or features that require manual configuration. References: 1: Flow Builder and Process Builder Actions for Manufacturing Cloud2

• 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

 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

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

The organization should leverage Partner Visit Management functionality to fill the gap. Partner Visit Management is a feature of Salesforce Manufacturing Cloud that enables manufacturers to collaborate with their channel partners on sales and service activities. With Partner Visit Management, manufacturers can create and assign visit plans to their partners, track their progress and performance, and provide feedback and coaching. Partners can access the visit plans through the Manufacturing partner site, which is a predefined template for Experience Cloud sites. The Manufacturing partner site also allows partners to view and update sales agreements, forecasts, and account information, as well as access resources and training materials. By using Partner Visit Management and the Manufacturing partner site, the organization can support its channel partners by providing functionality, insights, and data, as well as working closely with them to plan their work. References:

• Engage with Your Partners - Salesforce
• What Is Manufacturing Cloud? - Salesforce
• Elevate Partner Management - Salesforce
• Simplify Partner Engagement: A Guide for Manufacturers - Salesforce

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

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

 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

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

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

 The Forecast Analysis dashboard in Tableau CRM for Manufacturing is a tool that helps business analysts evaluate the accuracy and quality of the account forecasts generated by the Manufacturing Cloud. It allows them to compare the actual revenue with the forecasted revenue, as well as the planned revenue, for each account, product, and product category. It also shows the mean absolute percentage error (MAPE) in the forecast, which is a measure of how close the forecast is to the actual revenue. The lower the MAPE, the better the forecast. The dashboard also provides other metrics, such as forecast bias, forecast coverage, and forecast attainment, to help analysts identify areas of improvement and optimize the forecasting process1. References: Protect and Grow Your Business Unit, Forecast Analysis Dashboard, How Forecasting Works in Tableau

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

When designing a Manufacturing Cloud implementation, it is important to consider the data sources and quality of the existing third-party systems that will be integrated with Manufacturing Cloud. One of the key considerations is to determine the system of record for each data category required by the business, such as customer information, product data, order history, inventory levels, and so on. The system of record is the authoritative source of data that is trusted and maintained by the business. By identifying the system of record for each data category, you can ensure data consistency, accuracy, and integrity across the integrated systems. You can also avoid data duplication, conflicts, and errors that may arise from having multiple sources of data for the same category. References: What Is Manufacturing Cloud?, Data Integration

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

 To collaborate with channel partners in Manufacturing Cloud, it is recommended to use external apps and Experience Cloud. External apps are applications that run outside of Salesforce but can integrate with Salesforce data and functionality. They can provide custom solutions for specific business needs and extend the capabilities of Manufacturing Cloud. For example, external apps can enable partners to access inventory levels, order status, product catalogs, and pricing information from Salesforce. Experience Cloud, formerly known as Community Cloud, is a platform that allows you to create branded digital experiences for your customers, partners, and employees. It can help you engage with your channel partners and provide them with self-service tools, collaboration features, and personalized content. For example, Experience Cloud can enable partners to view and update sales agreements, account forecasts, rebates, and targets from Salesforce. It can also help you train and onboard your partners, monitor their performance, and reward them for their achievements. References: Engage with Your Partners, Re-Imagining Partner Relationships with Manufacturing Cloud, Manufacturing Cloud

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

 To set up Tableau CRM for Manufacturing, an Admin needs to have the Manufacturing Einstein Admin permission set and the Manufacturing Analytics Admin permission set. The Manufacturing Einstein Admin permission set grants access to the Manufacturing Einstein features, such as Account Forecasting and Account Manager Targets. The Manufacturing Analytics Admin permission set grants access to the Manufacturing Analytics app and its dashboards, such as Sales Agreement Performance and Account Health1. The other permission sets are not specific to Manufacturing Cloud and do not provide the necessary access to set up Tableau CRM for Manufacturing. References: 1: Set Up Users and Permissions for Manufacturing Cloud2

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

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