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

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

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

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

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

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

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

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

Manufacturing Cloud Overview

Manufacturing Cloud Developer Guide

To establish clarity between new business and run-rate business, Universal Containers should adopt a differentiated approach where new businesses use Opportunities and Collaborative Forecasting, while run-rate business utilizes Sales Agreements and Account-Based Forecasting. This strategy leverages the strengths of Salesforce Manufacturing Cloud's forecasting and agreement features to align with the distinct nature of new and run-rate business, ensuring accurate forecasting and effective management of business operations.

 Manufacturing Cloud comes with a predefined manufacturing partner template that can help manufacturers collaborate efficiently with their channel partners on sales agreements, forecasts, leads, and opportunities. The manufacturing partner template is a responsive portal that provides partners with access to knowledge articles, dashboards, and reports. Partners can also update products, prices, quantities, and adjustments on sales agreements, as well as view and edit account forecasts. The manufacturing experience cloud template is built on Experience Cloud, which allows you to customize the site with branding, themes, components, and pages. You can also assign user permissions and roles for the site to control the access and visibility of your partners. References: Engage with Your Partners, What Is Manufacturing Cloud?, Manufacturing - Salesforce.com, Simplify Partner Engagement: A Guide for Manufacturers

The Analytics for Manufacturing app is a prebuilt app that provides dashboards and insights for manufacturing account managers. The app has three modules: Sales Agreements, Account Based Forecasts, and Account Manager Targets. Each module has its own dataflow, template, and dashboard. The administrator can choose any combination of modules based on the business need and data availability. For example, if the administrator only wants to analyze sales agreements and account forecasts, they can select only those two modules and exclude the account manager targets module. The app creation process will only include the dataflows and templates for the selected modules. The administrator can also add or remove modules later by editing the app1. References: Create and Share an App from the Analytics for Manufacturing Template

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

To create a custom metric for display on Agreement Terms, you need to create custom fields on the Sales Agreement Product and Sales Agreement Product Schedule objects, and map them using the Data.com Administration tool. The custom fields must have the same data type as the default fields, and only number, currency, and formula field types are available for mapping. Therefore, the correct answer is C. Only number, currency, and formula field types are available for mapping. References: Customize Salesforce Field Mappings, Create Custom Fields for Sales Agreement Products and Schedules

 A sales agreement is a long-term contract that defines the terms and conditions for the products and services that you sell to your customers. You can perform various actions on a sales agreement to manage its lifecycle, such as approving, activating, expiring, or deleting it. Two of the out-of-the-box actions that you can perform on a sales agreement are:

Recalculate Actuals: This action updates the actuals for the sales agreement based on the invoices and orders associated with it. You can recalculate actuals manually or schedule it to run automatically at a specified frequency. Recalculating actuals helps you track the progress and performance of the sales agreement over time.

Update Products: This action allows you to add, remove, or modify the products and categories in the sales agreement. You can update products manually or use the mass update feature to apply changes to multiple products at once. Updating products helps you adjust the sales agreement to reflect the changing needs and preferences of your customers.

References: Sales Agreements and Forecasting in Manufacturing Cloud, Sales Agreement, Get Started with Manufacturing Cloud for Sales, Create and Work with Sales Agreements, Manufacturing Cloud

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

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

 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

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.

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

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

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

One of the methods to calculate Actuals for sales agreements is to automatically derive them from direct orders. A direct order is an order that is created from the related list of a sales agreement record. A daily automated process calculates the product quantity fulfilled in each activated order, and then updates that quantity in the sales agreement. This method allows you to track the actual performance of your sales agreements based on the orders placed by your customers or partners. You can also use other methods to calculate Actuals, such as importing quantities from external sources, or using orders associated with contracts. References: Create Orders to Calculate Sales Agreement Actuals, How Are Sales Agreement Actuals Calculated?

To load data into Manufacturing Cloud, you need to follow a specific order of operations to ensure data integrity and avoid errors1.

The order of operations is based on the dependencies and relationships between the objects in Manufacturing Cloud1.

The recommended order of operations is as follows1:

Load Accounts, Contacts, and Products first, as they are the base objects that other objects depend on.

Load Sales Agreements next, as they reference Accounts, Contacts, and Products, and are used to track run-rate or long-term negotiated business.

Load Orders last, as they reference Sales Agreements, Accounts, Contacts, and Products, and are used to track actual business transactions.

The other options are incorrect because they do not follow the recommended order of operations and may cause data integrity issues or errors.

References:

Load Data into Manufacturing Cloud - Salesforce

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

It is important to understand the landscape of the business before going into the details of requirements because it helps the consultant to ensure there’s an understanding of the big picture and where the real opportunity lies between teams agnostic of Manufacturing Cloud. By analyzing the current state of the business, the consultant can identify the pain points, challenges, goals, and opportunities of the organization and its stakeholders. The consultant can also map out the value chain, the customer journey, the key processes, and the systems and data involved in the business operations. This will help the consultant to align the requirements with the business objectives and priorities, and to design a solution that delivers value and impact across the organization. Understanding the business landscape also enables the consultant to communicate effectively with the client and to establish trust and credibility. References:

Manufacturing Cloud - Salesforce

Manufacturing - Salesforce.com

Meet Manufacturing Cloud Unit | Salesforce Trailhead

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

Universal Containers does not want to bring actual orders data into Salesforce, but still wants to use the actual orders data to analyze the effectiveness of their sales agreements, they must select the Manually Using actual orders API option in the sales agreement setup. This option allows them to use an API to upload actual order data from an external system into Salesforce and associate it with the sales agreements. This way, they can compare the planned and actual quantities and revenues of each product or product category in the sales agreement. The other options require either creating orders in Salesforce or linking contracts to orders in Salesforce, which Universal Containers does not want to do. References: Choose How Sales Agreement Actuals Are Calculated, Create Orders to Calculate Sales Agreement Actuals

create a sales agreement, you need to specify the account, the price book, and the product(s) that are part of the agreement. The account is the customer that you have a contractual relationship with. The price book is the list of products and prices that you offer to the account. The product(s) are the items that you agree to sell to the account for a certain quantity, price, and time period. You can also add other optional data elements to the sales agreement, such as start date, end date, schedule frequency, schedule count, and terms and conditions1. References:

Create a Sales Agreement

 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

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.

 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

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

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

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

Account Manager Targets is a feature in Manufacturing Cloud that allows businesses to set and track sales goals for their account managers based on product volume, revenue, or any other custom measure. Account managers can create, assign, and edit targets for their team members and monitor their performance against the targets. When a target is changed in Account Manager Targets, the change is not reflected immediately in the assignment values of the team members. To see the updated assignment values, you must perform the Refresh Assignments action on the Assignments tab of the target record. This action recalculates the assignment values based on the new target value and distributes the target among the team members according to the assignment rules. The other actions are not valid for Account Manager Targets. References: Account Manager Targets in Manufacturing Cloud, Learn About Account Manager Targets, Enable Account Manager Targets, Assign an Account Manager Target

For a manufacturer managing orders and contracts in an external system like SAP, the administrator should select the option to manually use API upload. This allows for the bulk upload of updated quantities at regular intervals through integration, which the Salesforce org picks up during a daily scheduled job to update sales agreements .

 Data Processing Engine (DPE) Templates are used to customize the data model and calculations for account-based forecasting in Manufacturing Cloud. DPE Templates allow users to define the dimensions, metrics, and formulas for their forecasts based on their business needs. In this case, UC needs to customize the DPE Template to include the product category as a dimension, and the ordered quantity, revenue, shipped quantity, and revenue as metrics. UC also needs to specify the custom fiscal year and the weekly forecast frequency in the DPE Template. The other options are not relevant for this requirement. Sales Agreement Metrics are used to track the performance of sales agreements, not forecasts. Advanced Account Forecast Fact object is a standard object that stores the forecast data, not a customization option. References: Customize Data Processing Engine (DPE) Templates, Account-Based Forecasting in Manufacturing Cloud

According to the Salesforce Manufacturing Cloud documentation, you can use the Formula Builder on the Account Forecasting page in Setup to create formulas for forecast calculations. You can define your own formulas for quantity and revenue based on sales agreements, orders, opportunities, and account metrics. You can create either a single formula for all periods, or multiple formulas for different period ranges. If the forecast display period is 12 months, you can create up to 12 formulas. However, if you want to calculate an account based forecast for the next 13 months, you need to create separate formulas for periods 1-12 and period 13, because the Formula Builder does not support more than 12 periods in a single formula. This way, you can ensure that the forecast calculations are accurate and consistent for each month. References: Build Formulas to Calculate Forecast, Configure Forecast Metrics and Formulas