Loading
Manufacturing Cloud
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Considerations for Sales Agreements

          Considerations for Sales Agreements

          Keep the following considerations in mind while setting up and using Sales Agreements in Manufacturing Cloud.

          Required Editions

          Available in: Enterprise, Unlimited, and Developer Editions

          Sales Agreement Setup and Configuration

          • Sales Agreements features are supported only on desktop devices.
          • When your org gets upgraded during a release, make sure you check the cloned permission sets for Manufacturing Sales Agreements and Manufacturing Sales Agreements For Community. The Mass Update for Sales Agreements system permission gets automatically deselected in existing cloned permission sets during a release upgrade. You can reassign this permission in the cloned permission sets if required. There’s no impact when you clone a permission set after a release upgrade.
          • We recommend not changing the API names of custom fields in use in custom metrics in the Sales Agreement Product and Sales Agreement Product Schedule objects. Remove the mapping between the custom fields before changing their API names.
          • The fields on sales agreements objects are of type double Number (18,0) with no precision defined at the API level. The data display is up to 2 decimal places as defined by the platform at the UI level.
          • We recommend not creating record types for the Sales Agreement Product and Sales Agreement Product Schedule objects. If you add record types to the Sales Agreement Product object, you won’t be able to add products to a sales agreement from the sales agreement record page.

          Sales Agreement Terms

          • 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 performance.
          • Order products with negative quantities and unit prices are considered when actuals are calculated for sales agreements. Sales teams create orders with negative quantities to represent order returns or recalls. Negative quantities and unit prices for order products are reflected in the Actual Amount and Actual Quantity metrics in the Agreement Terms tab for a sales agreement record. To ensure that actuals for order returns are calculated accurately, sales teams must create order products with negative quantities to represent order returns. If both the quantity and the unit price are negative for an order product, the actuals calculated will be positive. To let your sales team create order products with negative quantities, enable negative quantities in Setup. To learn more, see Enable Negative Quantities for Order Products.
          • For sales agreements with Product Level as Category, the Mass Update action may not work if you’re trying to increase or decrease the Initial Planned Quantity for specific schedules. The Planned Amount field is a derived field where Planned Amount = IF((PlannedAmount > 0),PlannedAmount,PlannedQuantity * SalesPrice * (1 - DiscountPercentage )). If you update the value once more, the value changes.
          • If you update the number of products and schedules in a sales agreement, you can experience a delay in saving the agreement terms.
          • The edit history isn’t saved when you edit a forecast quantity, forecast amount, or any custom forecast metrics for a sales agreement or use the Mass Update option to update the forecast values. And there’s no indicator that the forecast metric value in that cell is modified.
          • You can’t add a product to a sales agreement if the product already exists in the sales agreement.
          • The autogenerated name of a sales agreement product schedule is determined by its start date. For example, in a monthly sales agreement, if a schedule’s start date is August 31, 2023 and end date is September 30, 2023, the schedule’s name will be Aug '23. Or, in a yearly sales agreement, if a schedule’s start date is December 31, 2023 and end date is December 30, 2024, the schedule’s name will be 2023. You can change the autogenerated name of a schedule by editing the Name field of a Sales Agreement Product Schedule record.
          • Based on the method of specifying the sales prices of products in sales agreements, you can specify sales prices with different numbers of decimal places.
            • When you add products to a sales agreement, in the Edit Selected Sales Agreement Products window, you can specify sales prices with up to two decimal places. To store sales prices with up to five decimal places in the Edit Selected Sales Agreement Products window, ask Salesforce Customer Support to enable the More Decimals on Price option for your org. See Product Price 'More Decimals on Price' feature.
            • When you edit values in the sales agreements table, you can specify sales prices with up to 18 digits, including digits before the decimal place, digits after the decimal place, and the decimal point. The table shows sales prices with only the first five decimal places.
            • When you perform mass updates for sales prices, you can specify values with up to five decimal places.
            • You can specify sales prices with up to 18 digits, including digits before the decimal place, digits after the decimal place, and the decimal point, in the sales agreement product schedule record page. The record page shows sales prices with only the first two decimal places. To learn more, see View Agreement Values

          Sales Agreement Lifecycle

          • If you add custom statuses for Sales Agreement, make sure you use the Reorder action to arrange the multiple statuses related to the Activated Status Category. Move the custom status after the default Activated status value. When the sales agreement reaches the start date, and its status is Approved, the record automatically changes to the Activated status (default value). Then, you can manually change the status to the custom value that’s related to the Activated status category.
          • When you clone an existing sales agreement, it's created in Draft state with the same start date as the original sales agreement. The cloned sales agreement, however, doesn’t contain the products and schedules of the original sales agreement.
          • If you get an error when simultaneously converting more than 100 quotes, opportunities, or custom objects to sales agreements using the new Sales Agreements Connect REST API, try converting with fewer objects at a time.

          Sales Agreement Actuals Calculation

          • If you manually recalculate actuals for a sales agreement on a certain day, the sales agreement isn’t considered in the nightly actuals calculation job on that day.
          • For a category level sales agreement, if you want an ordered product to be considered for actuals calculation, ensure that you specify its primary category in the sales agreement.

          Sales Agreement Decimal Metrics

          • While creating a sales agreement using Apex code or flows, specify parameters such as the decimal scale, start date of the sales agreement, and actual calculation mode. We recommend performing the insert and update operations in different transactions.
          • The decimal scale for a specific sales agreement can be updated only if the sales agreement is in Draft status and there are no products added to it.
          • We recommend using the decimal fields for quantity metrics.
          • When you add a product to the Sales Agreement Products, you can enable the Quantity in Decimals checkbox to add quantity metrics with a decimal value. If this checkbox is not selected, you can only add quantity metrics with an integer value.
          • Decimal fields for quantity metrics are supported only for Advanced Account Forecasting. Account Forecasting doesn’t support decimal fields.
          • The Quote to Sales Agreement feature don’t support decimal fields. To use decimal fields, map the quote metrics to the new sales agreement metrics.
          • For an existing Salesforce org, you can continue to use the default integer fields. No updates to the page layout are required. For a new Salesforce org, the decimal fields are added by default.
          • For an existing sales agreement, if you’re adding decimal fields to your page layout, you can remove the integer fields. If you retain both the integer and their corresponding decimal fields for the same quantity metrics, only values entered in the decimal fields are considered.

          Revenue Management Features for Sales Agreements

          Bundled Products aren't supported with the revenue management features for sales agreements. You can't add bundled products to sales agreements.

          Einstein Summary for Sales Agreements

          When you use the Einstein Summary component on record pages to summarize sales agreements, the component displays only the top three products and up to five schedules per product. These limits are part of the default configuration and are designed to manage the context window constraints of large language models (LLMs), ensuring summary quality while staying within processing limits.

           
          Loading
          Salesforce Help | Article