Access to Standard Asset-Based Ordering

Oracle CPQ 25D supports the new Oracle CPQ platform-based implementation of Asset-Based Ordering (ABO), referred to as Standard ABO. With Standard ABO, ABO-specific package updates are no longer required to enable new features. New ABO-related features are included within the Oracle CPQ Update. Beginning with Oracle CPQ 25D, all new ABO implementations will be using Standard ABO.

Oracle CPQ 25C and earlier ABO implementations required package upgrades for new ABO feature support. These implementations are referred to as Package ABO implementations. All existing Package ABO customers can continue to use and leverage their existing ABO implementation. However beginning in Oracle CPQ 25D, we will no longer provide new ABO features via migration package.

Standard ABO provides the following new feature enhancements:

  • Seamless tracking of partial fulfillment of an asset on an order for customer environment’s integration with Oracle Fusion applications such as Oracle Order Management and Oracle Subscription Management.
  • Better visibility into asset order status with a new Pending status. The Pending status indicates the order is successfully submitted and the asset is not yet Fulfilled.
  • Less administrator overhead to incorporate ABO features into the Oracle CPQ application. Standard ABO incorporates all new ABO features into the Oracle CPQ platform. With Package ABO, new features were decoupled from the Oracle CPQ platform updates.
  • Easy-to-use user interface for mapping your custom asset attributes to your transaction attributes and transaction to asset attributes.
  • Support of Renewal and Termination actions for orders that have both subscriptions and goods.
  • Ability to track coverage-type products with their associated asset. For example, a new laptop with a 3-year warranty.

Steps to Enable

Beginning with Oracle CPQ 25D, all new ABO implementations will be deployed using Standard ABO. For new Standard ABO implementations a Commerce Setting, Enable Standard ABO, is available and is set to No by default. Administrators will need to change the Enable Standard ABO setting to Yes to begin using the Standard ABO features.

Asset Settings for Standard ABO

All existing Package ABO customers can continue to use and leverage their existing ABO implementation.

Customer who have implemented Package ABO prior to Oracle CPQ 25D may want consider moving to the Standard Quote Process and leveraging Standard ABO for their business. When planning for the transition from Package ABO to Standard ABO, the following tasks need to be taken into account:

  1. Implement the Standard Quote Process. Refer to Commerce Standard Process for more information.
  2. Enable the Standard ABO Process.
  1. Log a Service Request (SR) on My Oracle Support to gain visibility to the new 25D Asset Options in the Commerce Settings page. Once visible, the Enable Standard ABO setting will be default be set to No.
  2. Click Yes for Enable Standard ABO Commerce setting.
  3. Click Save.
  1. Re-implement all existing functionality and customizations to the Standard Quote Process with Standard ABO.

Note: Assets that were created in the Package ABO implementation will not work in the Standard ABO implementation.

  1. Disable the Package ABO.
  2. Thoroughly test the Standard Quote Process with Standard ABO on a non-production environment.
  3. Once testing is complete, migrate from your non-production environment to your production environment.

Tips And Considerations

Existing Package ABO customers who want to move to Standard ABO will need to be on the Standard Commerce Process. This may involve moving transactions from the existing Commerce process to the Standard Commerce Process.