Loading
Feature degradation | Gmail Email delivery failureRead More
Get Started with Communications, Media, and Energy & Utilities (CME)...
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
          Asset-Based Ordering

          Asset-Based Ordering

          An asset is a standard Salesforce object that represents an item of commercial value, such as a product or service sold by your company or a competitor, that an account or contact owns. Salesforce Industries extensions to the Asset object support special features such as discounts, bundle pricing, cancellation fees, and customer preferences.

          Asset-based ordering is based on a customer's existing products and services. Assets are subscribed to services and products.

          Assets are created during the CPQ order management process. Whether an asset is created right away depends on the product or service.

          The asset provisioning status indicates the current state of the product or service:

          • New: The order has been placed, but it has not been provisioned or activated.

          • Active: The customer currently enjoys the asset. Until a service starts, an asset is not active.

          • Deleted: The product or service is no longer available to the customer.

          Many customer orders impact the products and services that the customer has already purchased. A customer may want to modify their assets by:

          • Adding a service, such as enabling international roaming from a smartphone.

          • Adding a product, such as adding another smartphone to a family phone plan.

          • Updating a service, such as changing the Internet speed for their residential broadband service.

          • Disconnect a service, such as canceling a cable service.

          Opportunities become Quotes, which become Orders, which become Assets. In addition, Assets can go back to being Quotes or Orders.

          You can create quotes and orders against a set of customer assets. In the first stage of order capture, an opportunity moves to a quote and then to an order. With the completion of the order, the order becomes an asset. If the customer wants to change the asset, revert the asset back to order status.

          With versioned products, the available versions depend on the reference date. The reference date is mapped to new order items from the asset. The structure of the bundle is resolved based on the line item's reference date, not the header's date. Any added child item in a bundle uses that rootLineItem’s reference date. Adding the same bundle as a new line item from the product list uses the header's reference date. See Versioning Reference Dates.

          You change an existing asset by moving it to either:

          • A quote, and once the quote is complete, move the quote to an order, and then an asset

          • An order, and once the order is complete, move the order to an asset.

          You can work across line items (XLI). Using Field Mapper, you map fields in the Opportunity, Order, Quote, and Asset objects. For more information, see Map Fields for Asset-Based Ordering.

          Using Object Mapper, you can move data to and from any object. For more information, see Map Objects for Asset-Based Ordering.

          • Move, Add, Change, Delete (MACD)
            Changing an asset to an order or a quote initiates a guided process that moves one or more assets between service locations.
          • Preserve Asset Status During Metadata Updates
            Optimize your Move, Add, Change, Delete (MACD) processes by preventing unnecessary status changes on asset line items. You can now configure Industries CPQ to preserve the Existing status when MACD rules update attribute properties without altering the actual values.
          • Selecting the Asset-Based Ordering Implementation
            Asset-based ordering uses Vlocity interfaces and implementations.
          • Asset Viewer in Industries CPQ
            Industries CPQ has an Asset viewer in LWC from which you can view, filter, and modify assets for an account. From this viewer, you can convert assets to orders or quotes with the Cart in LWC, and you can change the assets.
          • Configure Asset Viewer
            Asset Viewer is a powerful, configurable component built that use Flexcards and Integration Procedures. Add this component to your Account page to provide a comprehensive, interactive view of all assets. It shows records for both the primary account and all associated child accounts in a single location.
          • Submitting an Order and Creating Assets
            Submitting an order calls the asset-based ordering interface implementation, which creates assets from the order.
          • Convert an Asset to a Quote or an Order
            Create quotes and orders against a set of one or more customer assets.
          • Fields for Asset-Based Orders
            The following table lists the details required for asset-based orders. The fields listed below exist on the Asset sObject.
          • Handle Cost Components in Assets
            When you retrieve Assets to present to an Energy customer, typically for tariff details, it's a best practice to ensure that parent Assets and cost components nest properly.
          • Asset-Based Ordering Visualforce Pages
            There are three standard Visualforce pages and six Visualforce pages based on the Vlocity Cards framework.
          • Mapping Objects for Asset-Based Ordering
            Using Object Mapper, you can move items, such as line item attachments and custom child objects throughout the asset-based ordering cycle.
          • Asset Reference IDs
            CME uses the asset reference ID and the provisioning status to track the asset across objects in the asset-based ordering (ABO) life cycle.
           
          Loading
          Salesforce Help | Article