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

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.

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

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

Sales agreement cloning is a feature that allows users to create a new sales agreement by copying the details from an existing one. This can save time and effort when creating similar sales agreements for different accounts or time periods. When cloning a sales agreement, the product details, such as product name, quantity, price, and discount, are copied over from the original sales agreement. The new sales agreement is created in draft status, which means it can be edited and submitted for approval. The default start date of the new sales agreement is the current date, not the start date of the original sales agreement. The agreement term details, such as metrics, actuals, and forecasts, are not copied over from the original sales agreement, as they are specific to each sales agreement and time period. References: Clone a Sales Agreement, Sales Agreement Cloning

To 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

 Invalid target assignments are team assignments that are no longer valid due to changes in the target or the team member. For example, if a team member leaves the company or is reassigned to another target, their existing assignments become invalid. Invalid target assignments are shown in the Invalid Team Assignments section of the Assignments tab in the target’s record. This section displays the invalid assignments for all team members who have access to the target, regardless of the ownership. Invalid target assignments can also be seen in the Invalid Target Assignments report, which is a standard report provided by Manufacturing Cloud. This report shows all the invalid assignments for the current user and their subordinates, along with the reason for the invalidity. The report can be filtered by target name, team member name, or invalidity reason. References: Distribute Targets and Manage Invalid Targets Unit, Manage Invalid Team Assignments

 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

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

Before you create the analytics for manufacturing App, you need to ensure that your data meets some specific requirements. One of these requirements is that at least one record must exist in each of the Manufacturing cloud objects to be analyzed, such as sales agreements, account forecasts, account manager targets, and rebates. Otherwise, the data fails the CRM Analytics check and you see an error message. Having records in these objects ensures that the app can import and display relevant data for your business1. References: Data Required to Create the Analytics for Manufacturing App

The standard Manufacturing Experience Cloud Template includes functionalities such as Sales Agreements and Account Manager Targets among its offerings. Sales Agreements help manage and track the terms of sales between a business and its customers, while Account Manager Targets facilitate setting and tracking sales targets for account managers. These functionalities are integral to streamlining sales operations and enhancing the management of customer relationships within the Manufacturing Cloud .

Salesforce Manufacturing Cloud allows users to define the renewal period for sales agreements in their org. The renewal period is the number of days before the end date of a sales agreement from when users can renew the agreement. Users can renew a sales agreement only when the renewal period starts. The other options are not related to the renewal of sales agreements. References: Define Renewal Period for Sales Agreements

o help the executive team make decisions quickly, an administrator should implement Product Categories functionality. Product Categories are a way of grouping products based on common characteristics, such as type, brand, flavor, or package12. By using Product Categories, the executive team can easily filter, sort, and analyze the large number of SKUs in their business. They can also use Product Categories to create sales agreements and forecasts at different levels of granularity1. References: Manage Products and Categories in a Sales Agreement, Configure Product Hierarchies Unit

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

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

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

Validating the functionality against business process flows is a key step in the implementation or system update of Salesforce Manufacturing Cloud. It helps to ensure that the system meets the business requirements and expectations of the stakeholders, and that it can handle the various scenarios and use cases that may arise in the manufacturing industry. By validating the functionality, you can also identify and resolve any issues or gaps that may affect the system performance, usability, or security. Additionally, validating the functionality can help you to document and communicate the system changes and benefits to the end users and other parties involved in the project. References: Implementation Guide, System Updates

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

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

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

 = These two actions can be taken to give the Account Managers ‘Read’ access to the new custom field on the APF Table. The first action involves cloning the existing permission set that already grants access to the APF Table and its standard fields, and then modifying the cloned permission set to include the new custom field. The second action involves editing the existing permission set directly to add the new custom field. Both actions require the same license type, which is Manufacturing Forecast Psl, to access the APF Table. The other two actions are not valid because they use a different license type, which is Salesforce, that does not support the APF Table. References: = Assign the Permission Set for Advanced Account Forecast Product Category, Create Custom Fields for Account Product Forecast and Account Product Period Forecast Objects, Permission Sets and Licenses for Manufacturing Cloud

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

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

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

 You can recalculate payouts for closed periods in two situations: when the member benefits change due to changed requirements, or when the member submits transactions after the payout period is closed, or there is an error in the payout calculation. In both cases, you need to modify the payout records and run the rebate flow again to recalculate the payouts. The first method is to recalculate payouts due to changed benefits, which means that the benefit structure and terms have changed after the payout was calculated for a period. The second method is to recalculate payouts with no charge in benefits, which means that the benefit structure and terms have not changed, but the transactions or the payout calculation have changed. References: Recalculate Payouts for Closed Periods, Rebate Management

The Time Period filter on a sales agreement record page allows you to view the sales agreement terms and schedules for different time periods. You can choose from three options: Range, Set Periods, and Current Period. Range lets you specify a start and end date for the filter. Set Periods lets you select up to eight periods from a list of predefined periods, such as quarters, months, or weeks. Current Period shows the current period based on the sales agreement’s period type and start date. Custom and Fiscal Year are not available options for the Time Period filter. References: = Filter Sales Agreement Schedules by Time Period, Filter Sales Agreement Terms by Products or Categories

Manufacturing Cloud provides three permission sets related to Sales Agreements, Account Forecasting, and Account Manager Targets. These permission sets give users access to the features and data models that are specific to the manufacturing industry. The permission sets are:

Manufacturing Account Forecast: This permission set lets users track account forecasts for quantity and revenue metrics of products. Users can view and edit the Account Product Forecast and Account Product Period Forecast objects, as well as the related objects such as Account, Product, and Sales Agreement.

Manufacturing Sales Agreements: This permission set gives users access to sales agreements that work with orders, contracts, and more. Users can view and edit the Sales Agreement and Sales Agreement Line Item objects, as well as the related objects such as Account, Product, and Order.

Manufacturing Account Manager Target: This permission set gives users access to Account Manager Target features that include creating, assigning, and distributing targets. Users can view and edit the Account Manager Target and Account Manager Target Line Item objects, as well as the related objects such as Account, Product, and Sales Agreement.

References: Assign the Manufacturing Permission Sets to Users, Set Up Users and Permissions for Manufacturing Cloud

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

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 manager targets are long-term goals that account managers set for themselves and their team members. They can be based on revenue, volume, margin, or any other metric that is relevant for the business. The team member hierarchy type determines the users that account managers can assign targets to. It can be either the manager hierarchy or the forecasts hierarchy, which are defined in the Roles and Forecasts Hierarchy pages in Setup, respectively. If the team member hierarchy type is changed in account manager targets, all the existing targets are made read-only, as a warning message indicates. This is to prevent any inconsistency or confusion in the target assignments and approvals. To edit the existing targets, account managers have to clone them and make the necessary changes. References: Choose Team Member Hierarchy for Account Manager Targets, Set Up and Configure Account Manager Targets, Set Up Targets for Account Managers Unit | Salesforce Trailhead, Assign an Account Manager Target

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 correct approach for importing order data into Manufacturing Cloud involves providing the client with a comprehensive data template file that reflects the data mapping, including the identification of related records such as accounts and sales agreements. It is also crucial to disable any irrelevant automations or rules that might interfere with the data import process. This ensures a smooth transition and accurate reflection of order data within the Manufacturing Cloud environment

To ensure that the 100 new products appear in sales agreements, they must be marked as active and added to the standard price book. This is necessary for managing products and categories within a sales agreement and allows for the addition of new product lines or categories to activated sales agreements .

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

To ensure data consistency following the migration of sales agreements, the administrator should verify the migration file and compare randomly selected lines with the legacy system. This method allows for a focused and manageable approach to validating the accuracy of the migrated data, ensuring that no data was lost or incorrectly migrated during the process. It's a practical approach that balances thoroughness with efficiency, particularly when dealing with large datasets.

A System Integration Testing (SIT) environment is used as an environment to perform system-to-system testing. This means that the SIT environment is used to test the integration of different systems or components that are part of the Salesforce Manufacturing Cloud solution. The SIT environment allows the verification of the functionality, performance, and reliability of the integrated systems, as well as the identification and resolution of any defects or issues that may arise during the integration process. The SIT environment is typically a replica of the production environment, but with a smaller data set and lower security requirements. The SIT environment is also used to validate the data migration and synchronization between the source and target systems, as well as the compatibility and interoperability of the APIs and web services that are used for the integration. References:

Manufacturing Cloud - Salesforce

How to Perform Automated Integration Testing in Salesforce

Automate and Test During Integration

The Service Console for Manufacturing app is a prebuilt app that provides a unified console for customer service representatives (CSRs) to view and manage information related to contacts and accounts, such as Cases, Assets, Warranties, and Claims1.

The app also provides features such as a timeline of interactions, contextual alerts, relevant actions, and knowledge articles to help CSRs resolve customer issues and provide proactive service1.

The app is designed specifically for the manufacturing industry and integrates with other Manufacturing Cloud features such as Sales Agreements and Account Forecasting2.

The other options are incorrect because they do not provide the same level of functionality and integration as the Service Console for Manufacturing app. Option A would only customize the layout of the Case object, but not the other related objects. Option B would enable the generic Service Console app, which does not have the manufacturing-specific components and data sources.

References:

Service Console for Manufacturing - Salesforce

Get Started with Manufacturing Cloud for Service - Salesforce