Manufacturing-Cloud-Professional Sample Questions Answers

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

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

To maintain data integrity in Manufacturing Cloud, the administrator should limit the mass update capability for Sales Agreements to only System Administrators. This will prevent accidental or malicious changes to the Sales Agreement data by other users. To do this, the administrator can clone the standard Manufacturing Sales Agreements permission set, which grants access to the Sales Agreement object and related fields. Then, the administrator can deselect the mass update for Sales Agreements permission in the cloned permission set, and assign it to all non-System Administrator users. This way, only System Administrators can perform mass updates on Sales Agreements, while other users can still view and edit individual records. References: Sales Agreement Permissions, Mass Update Sales Agreements

To accommodate Universal Chemicals' requirement to show agreed and delivered volume on each schedule and in actual figures for their liquid chemicals, a Manufacturing Cloud consultant should recommend creating custom fields for volume and total volume on the sales agreement objects. Additionally, a before save flow can be used to calculate the total volume based on these fields. Metric Mapping can then be utilized to display these metrics on the sales agreements, allowing for a comprehensive view of agreed, ordered, and delivered volumes, which is essential for accurate forecasting and management of liquid chemicals in various tank sizes .

 A sales agreement is a long-term agreement between a buyer and a seller to negotiate price and volume of products. To create a sales agreement in Salesforce Manufacturing Cloud, you need to have an account object that represents the buyer. The account object stores the information about the customer, such as name, address, contact, industry, and so on. You can also associate a contact object with the account to specify the person who is responsible for the sales agreement. Other objects that are related to the sales agreement are sales agreement product, sales agreement product schedule, sales agreement line item, and sales agreement forecast. References: SalesAgreement | Manufacturing Cloud Developer Guide | Salesforce Developers, Sales Agreements and Forecasting in Manufacturing Cloud | Salesforce Module, Convert Opportunity to Sales Agreements in Salesforce Manufacturing Cloud

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

 Rebate Management allows businesses to create and manage rebate programs that reward their partners for meeting sales targets. A rebate program consists of a rebate type, which defines the incentive structure, and a rebate agreement, which specifies the eligible partners and products. A rebate type benefit is a component of a rebate type that defines the thresholds of an incentive and how payouts are scaled for varying quantities and amounts. A benefit tier is a subcomponent of a rebate type benefit that specifies a range of sales targets and applicable benefit values. The minimum and maximum range values of a benefit tier must be positive integers and must not overlap with other benefit tiers in the same benefit. Therefore, the sequence of 0 to 100 is valid, while the other sequences are not. References: Rebate Management, Create and Manage Rebate Programs, Rebate Management Workflow

n: When planning a global rollout of Manufacturing Cloud, some key considerations are:

Manufacturers may have one or many versions of core systems like an Enterprise Resource Planning (ERP) that will require integrations and design considerations that vary. Manufacturing Cloud can integrate with existing ERP systems and Order Management Systems (OMS) by using APIs, the MuleSoft Accelerator for Manufacturing, or other middleware solutions1. However, different versions of ERP systems may have different data models, business processes, and security requirements that need to be taken into account when designing and implementing the integrations2.

There are language requirements, legal variation by geography, and cultural differences. Manufacturing Cloud supports multiple languages and currencies, but it also needs to comply with the local laws and regulations of each country or region where it operates1. For example, there may be different tax rules, privacy policies, or data protection standards that affect how Manufacturing Cloud handles and stores customer data3. Additionally, there may be cultural differences in how customers and partners communicate, negotiate, and collaborate, which may require adjustments in the user interface, workflows, and analytics of Manufacturing Cloud4. References: Considerations for Working with Manufacturing, What Is Manufacturing Cloud?, Salesforce Blog: Manufacturing Cloud, Salesforce Manufacturing Cloud: enabling customer centricity for manufacturers

 Account Manager Targets is a feature of Manufacturing Cloud that allows you to set up and manage sales goals and track performance for your account managers and their teams. To use this feature, you need to enable it in Setup and define some settings that affect how targets are created, assigned, and distributed. The three options that can be defined by an admin in the Setup area in Account Manager Targets are:

Target Measure Type: This is the unit of measurement for the targets, such as revenue, volume, or any custom measure. You can define up to three target measure types for your org and assign them to different target types. For example, you can have a target type for revenue and another one for volume, and use different target measure types for each one.

Team Member Hierarchy: This is the hierarchy that determines how targets are rolled up from individual account managers to their managers and so on. You can use the standard User Role hierarchy or a custom hierarchy based on a custom object. The hierarchy affects how targets are distributed, aggregated, and reported.

Distribution Frequency: This is the frequency at which targets are distributed from parent targets to child targets. You can choose from monthly, quarterly, or yearly distribution. The distribution frequency affects how targets are calculated and displayed for different time periods.

 Account Manager Targets in Manufacturing Cloud | Salesforce Trailhead Module, Enable Account Manager Targets - Salesforce, Define Account Forecast Settings Unit | Salesforce Trailhead Module

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]

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

 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

A potential blocker to Universal Containers' current business processes, given their operation across multiple countries with different currencies, is the limitation that currency exchange rates can only be updated if Advanced Currency Management (ACM) is enabled in Salesforce. This feature is crucial for businesses like UC that deal with multiple currencies, as it allows for more precise and dynamic management of currency exchange rates. Without ACM, UC may face challenges in accurately updating and managing currency exchange rates, which is essential for indexing prices annually and introducing new products throughout the year. This limitation can significantly impact the company's ability to maintain accurate pricing and discount thresholds for their customers categorized as Silver, Gold, or Platinum, potentially affecting sales agreements and overall business operations.

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 .

 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

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

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

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

ERP and Salesforce: Everything Manufacturers Need To Know

Integrate Salesforce.com with Oracle Integration Cloud

Oracle Cloud Using the Salesforce Adapter with Oracle Integration Cloud

All About Integrating Oracle ERP and Salesforce CRM-rSTAR Technologies

What Is Manufacturing Cloud? - Salesforce

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

Program Rebate Type Benefit is a Rebate Management object that supports custom fields for rebate program(s) analysis. It is used to define the benefit tiers for a rebate type, such as the percentage or amount of rebate that is paid out based on the achievement of a certain threshold. Program Rebate Type Benefit can have custom fields that specify the criteria by which the benefits vary, such as product category, region, or industry segment. These custom fields can be used in the Analytics for manufacturing app in Tableau CRM for Manufacturing to create dashboards and reports that show the performance and impact of rebate programs. References: Rebate Management Standard Objects - Salesforce Developers, Deploy and Use Rebate Analytics - Salesforce, Salesforce Manufacturing Cloud Flashcards

 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

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

 A sales agreement in Manufacturing Cloud represents a long-term agreement between a buyer and a seller to negotiate price and volume of products1. It provides a consolidated view of all the terms of the agreement, including the duration, products, price, planned quantities, and actual quantities2. A sales agreement can be created from an external source, such as a quote, opportunity, or custom object3. A sales agreement can also be used to create accurate account forecasts based on the planned and actual quantities4. References: Sales Agreements and Forecasting in Manufacturing Cloud, Get Started with Sales Agreements, SalesAgreement, Sales Agreement

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

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

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

if Sales Agreement List View is not selected in the Account Forecast Calculation Settings, no sales agreements will be considered when calculating the sales agreement metric values of account forecasts. This means that the account forecasts will only reflect the opportunity metric values, and not the sales agreement metric values. To include the sales agreement metric values in the account forecasts, you need to select a sales agreement list view that defines which sales agreements to use for the calculations. References: 1: Configure Account Forecast Calculation Settings - Salesforce

A rebate type benefit defines the thresholds of an incentive and how payouts are scaled for varying quantities and amounts. The minimum and maximum range values specify the sales targets for each benefit tier. The range values must be continuous and non-overlapping, meaning that the minimum value of one tier must be equal to the maximum value of the previous tier, and there should be no gaps or overlaps between the tiers. Therefore, option A is the only valid sequence of minimum and maximum range values for a rebate type benefit. References: Rebate Management Workflow, Create and Manage Rebate Programs

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

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 create sales agreements from historical data for a Manufacturing Cloud solution, a consultant must consider the following data items: Accounts, Orders, Order Lines, and Products. These are the core objects that are used to create and manage sales agreements in Manufacturing Cloud. Accounts represent the customers or partners that have sales agreements with the organization. Orders and Order Lines represent the actual sales transactions that are associated with the sales agreements. Products represent the items or services that are sold or purchased through the sales agreements. Invoices and Opportunities are not required for creating sales agreements from historical data, as they are not part of the sales agreement object model. Invoices are used to track the billing and payment status of the orders, while Opportunities are used to track the potential sales deals that may or may not result in orders. References: Sales Agreement Object Model, Create a Sales Agreement, Sales Agreement Fields

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

 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

 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

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

Upon the installation of the Analytics app, the default dashboards on the Account page include "Accounts agreement performance" and "Forecast analytics for the selected account." These dashboards provide a comprehensive overview of an account's performance in terms of sales agreements and forecast accuracy, allowing for in-depth analysis and strategic planning based on historical and current data.