Support Subscription Products for Asset-Based Ordering

Asset Lifecycle Management can create assets and sold-as asset groups for eligible subscription products, preparing them for asset-based ordering (ABO). This gives subscription products a traceable installed-base representation that supports amendments, renewals, terminations, and coverage-related transactions.

The process supports serialized and non-serialized subscription scenarios, including eligible standalone subscriptions and warranty coverage. Asset and subscription information remains linked throughout the lifecycle.

Prerequisites

  • In Product Information Management, configure the relevant subscription item and any associated physical item as Full Lifecycle or Customer Asset. Additionally, you may set the item as serialized or non-serialized.
  • Ensure the item is classified with an eligible subscription sales product type, such as Subscription, Extended Warranty, Software Maintenance, Service Level Agreement, or Preventive Maintenance.
  • Assign users the security needed to run the Create Subscription Product Assets and Asset Groups process.

If you already have subscriptions created and want to enable them for the ABO process then run the Create Subscription Product Assets and Asset Groups scheduled process to create the required ALM assets and sold-as asset groups. However, ensure that the subscription items in PIM are asset tracked.

  1. Enables asset-based ordering for eligible subscription products.
  2. Preserves asset, fulfillment, and subscription traceability across lifecycle changes.
  3. Supports serialized assets for precise partial amendments and terminations.
  4. Keeps covered goods and their subscription coverage relationships available for service and sales processes.
  5. Helps prevent direct changes to subscription-managed assets outside the intended lifecycle flow.

Steps to enable and configure

Asset Bases Ordering opt-in should be enabled in Order Management features.

Tips and considerations

  1. Subscription-managed assets are maintained through the subscription and fulfillment lifecycle; direct updates in Asset Lifecycle Management are not the supported path.
  2. Serialized subscriptions require the specific asset or serial identities for partial amendments, coverage changes, and returns.
  3. For nonserialized quantity changes, downstream transactions should explicitly identify the retained quantity to avoid unintentionally ending the remaining subscription.
  4. Future-dated renewals and amendments are treated as in-progress transactions; complete or cancel the in-progress transaction before starting another ABO action for the same subscription.
  5. Eligible bundle scenarios retain their asset hierarchy and fulfillment relationships. The source notes that included warranties are not created as ALM assets in the stated scope.
  6. Assets are created when the underlying fulfillment and subscription data is available; draft subscriptions that have not been fulfilled may not yet have an ALM asset.