Standard ABO: Date Effectivity Support for Asset Reconfiguration

Oracle CPQ 26A introduces asset date effectivity support for a subscription. This feature allows you to amend (modify or terminate) a subscription product before the effectivity date of the next amendment to that subscription product.

For example, if a current  subscription is active from Dec 2025 through Oct 2027 and modification to the subscription has been entered to begin June 2026, this feature allows you to create a new modification to the subscription that takes effect between Dec 2025 and June 2026.

A subscription product can have more than one amendment before its close date.

Steps to Enable and Configure

A new Commerce Setting, Allow back-dated ‘Modify’ and ‘Terminate’ operations on subscriptions, is supported for Oracle CPQ 26A Standard ABO implementations. This setting is set to No by default. Administrators can change the Allow back-dated ‘Modify’ and ‘Terminate’ operations on subscriptions setting to Yes to allow amending a subscription product before the effectivity date of the next amendment to that subscription product.

When the Allow back-dated ‘Modify’ and ‘Terminate’ operations on subscriptions setting is set to No (default), the Action drop-down for the subscription line item in the ABO Workbench does not allow amend actions.

Example ABO Workbench with Setting Set to No (Default)

When the Allow back-dated ‘Modify’ and ‘Terminate’ operations on subscriptions setting is set to Yes, the Action drop-down for the subscription line item in the ABO Workbench supports Terminate and Modify Actions.

Example ABO Workbench with Setting Set to Yes

Tips And Considerations

This feature is supported for Oracle CPQ and Oracle Subscription Management integrations.