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

 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

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

The account product period forecast record limit is the maximum number of records that can be stored in the Account Product Period Forecast object, which represents the quantity and revenue information of products for a particular time period of the forecast rolling period1. The default limit is 9 million records, but it can be changed by the admin2. If the org hits the limit, new products cannot be added to account forecasts, and new products are not added when recalculating a single account forecast or recalculating all account forecasts2. This means that the forecast data will not reflect the latest changes in the product portfolio and may affect the accuracy of the forecast. The add products option will still appear on the agreement terms tab, but it will not work if the limit is reached. New products added to account forecasts will be included in recalculations, as long as the limit is not exceeded. References: Considerations for Working with Manufacturing - Salesforce, Define Account Forecast Settings Unit | Salesforce Trailhead Module, Advanced Account Forecasting with Manufacturing Cloud | Salesforce, AccountProductPeriodForecast | Manufacturing Cloud Developer Guide | Salesforce Developers

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

Account Based Forecasting and Sales Agreements are two Manufacturing Cloud functions that should be configured to have a complete picture of both run-rate and net-new business. Account Based Forecasting allows you to forecast your sales revenue based on the account level, rather than the opportunity level. This gives you more visibility into the demand from your existing customers, as well as the potential from new customers. Sales Agreements allow you to manage the sales lifecycle of your long-term contracts with customers, including pricing, volumes, and order realization. This helps you to track and fulfill your run-rate business, as well as to identify and capture new business opportunities within your agreements. References: Forecast Your Run-Rate and New Business with Account-Based Forecasting - Salesforce Help, [Create and Work with Sales Agreements - Salesforce Help]

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

 A consultant should use an external object to access account order information from an ERP system. An external object is similar to a custom object, but the record data is stored outside the Salesforce organization. By using external objects, the consultant can access the order data in real time via web service callouts, without replicating the data in Salesforce. This way, the sales teams can view the current state of the order information related to an account, without wasting storage and resources keeping data in sync1. A standard Order object or a custom object would require copying the order data from the ERP system to the Salesforce organization, which is not the desired solution for UC. References: 1: External Objects2

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

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

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

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

In setting account manager targets, the combination of measures that creates these targets includes the Time period, Accounts, and Products. This approach allows sales managers to allocate target details appropriately by considering the specific time frame, the accounts managed by each account manager, and the products involved. This multi-dimensional approach to target setting enables a more nuanced and effective allocation of sales targets, catering to the diverse aspects of sales operations.

According to the Salesforce Manufacturing Cloud documentation, to create a new custom metric on the Account product period forecast component, you need to create a custom field on the Account Product Period Forecast object and another custom field on the Account Product Forecast object. Then, you need to map both of these fields in the Account Forecast setting page. This will allow you to add the custom metric to the Forecast tab of an account and track it along with the standard metrics1. References: 1: Create Custom Fields for Account Product Forecast and Account Product Period Forecast Objects

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 .

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

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

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

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 .

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

 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

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

 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

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

The administrator would configure Field-Level Security for the Advanced Account Forecast Partner and Advanced Account Forecast Fact objects to provide users with separate levels of visibility to forecast data. The Advanced Account Forecast Partner object stores the partner information for each account forecast record, such as the partner name, partner type, and partner role. The Advanced Account Forecast Fact object stores the forecast values for each account forecast record, such as the forecast amount, forecast quantity, and forecast margin. By setting the Field-Level Security for these objects, the administrator can control which users can view, edit, or delete the partner and fact data for each account forecast record. This way, the administrator can ensure that the users only see the relevant forecast data for their role and business unit12. References: 1: Set Field-Level Security for Fact and Partner Object in Advanced Account Forecasting3, 2: Forecast Fact Object Included with Advanced Account Forecasting4

The 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

To meet the requirements of UC, a Manufacturing Cloud consultant should recommend the following features: Partner Visit Management, Action Plans, and Generic Visit Key Performance Indicators. Partner Visit Management helps sales managers schedule visits to dealer and distributor locations, monitor performance, follow up on sales agreements, and capture key metrics1. Action Plans allow sales managers to create lists of tasks and associated assessment indicators that are commonly repeated across multiple visits2. Generic Visit Key Performance Indicators enable sales managers to compare the expected metrics versus the actual metrics for the key performance indicators they defined and then take necessary actions3. These features help UC to standardize the tasks to be performed during visits, understand how effective these visits are in getting partners to renew, and report on this data in Salesforce. The other features are not relevant for the given scenario. Advanced Account Forecasting is used to create holistic forecasts based on sales agreements, orders, opportunities, and account metrics4. CRM Analytics for Manufacturing is used to gain insights into sales performance, pipeline health, and customer satisfaction. Experience Cloud is used to create branded digital experiences for customers, partners, and employees. Service Console for Manufacturing is used to provide customer service and support across multiple channels. References: Partner Visit Management Workflow, Build Distributor Relationships with Partner Visit Management, Strengthen Relationships with Partners, Create Holistic Forecasts with Advanced Account Forecasting, [CRM Analytics for Manufacturing], [Experience Cloud], [Service Console for Manufacturing]

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

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

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

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.

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