This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Module | Feature | Notes |
|---|---|---|---|
| 08 SEP 2023 | Created initial document. |
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.
DISCLAIMER
The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
Manage Amount based Allowances for Consumption based Subscription Models |
||||||
Managing Recurring and Top-Up Allowance Grants for a Consumption-Based Subscription Model |
||||||
Support Daily Rates Proration, Periodic Billing and Periodic Revenue Recognition for Coverage Subscriptions
Support Daily Rates Proration, Periodic Billing and Periodic Revenue Recognition for Coverage Subscriptions. You can now prorate the one-time charge at the covered level at the time of closing the subscription. You can prorate by daily rates for closure of coverage service subscription products. You can also enable periodic billing of one-time charges and periodic revenue recognition of one-time charges for the coverage service subscription products at the covered level. Except for the proration using daily rates, the other 3 fields are available only when you enable detailed level of billing in coverage services.
- Coverage service subscription products are now at par with subscription only products.
- One-time charge can be prorated at the time of closure of a coverage service product.
- One-time charges can be billed on a periodic basis for coverage service product.
- One-time charges can be recognized as period satisfied in Revenue Management Cloud.
- Daily rates can be used to calculate the prorated credit amount for coverage service products upon closure.
Steps to Enable
You don't need to do anything to enable this feature.
Manage Amount based Allowances for Consumption based Subscription Models
Balance Management feature allows the tracking of amount-based allowances and usages in a balance register. Users have the flexibility to configure balance codes and associate a condition to decide what usage events or allowances are considered while tracking the given balance. They can configure balance profiles to define the rule for pooling of allowances and usages, and to track all the related balances in a balance register. Allowances are tracked with effectivity dates and can optionally add a rollover period to extend the validity of allowances. During the usage rating process, it will draw-down the allowances from the respective balance register, and rate the excess usage quantity to determine the usage charge for that event.
Manage Balance Codes
Manage Balance Profile
Manage Entitlement Plan
Manage Entitlement Plan Assignment
1. Allows tracking of amount-based allowances and usages in a balance register, and rate the excess usage quantity to determine the usage charge for the usage event.
2. Pooling of allowances and usages with effectivity dates, and can optionally add a rollover period to extend the validity of allowance.
Steps to Enable
You don't need to do anything to enable this feature.
Managing Recurring and Top-Up Allowance Grants for a Consumption-Based Subscription Model
This feature enables the creation of entitlement plans with allowances against recurring or one-time charges, in addition to usage charges. Users can implement their recurring or top-up allowance grant use case by adding allowances in the entitlement plan against recurring charges or one-time charges. All recurring and top-up allowance grants will be tracked and consumed in a balance register, similar to the way allowance grants created from usage charges are tracked and consumed. The balance profile has also been enhanced to include one-time and recurring charges, facilitating the creation of a balance register period and allowance grants from these charges as well.
Manage Balance Code
Manage Balance Profile
1. Allows tracking of quantity/amount-based allowances on recurring/one time charges and usages in a balance register, and rate the excess usage quantity to determine the usage charge for the usage event.
2. Pooling of allowances and usages with effectivity dates, and can optionally add a rollover period to extend the validity of allowance.
Steps to Enable
You don't need to do anything to enable this feature.
Copy Align Billing From during Subscription Renewal
This feature copies the Align Billing From date over from the source subscriptions to the renewed subscriptions on subscription renewal based on a checkbox setting in the renewal rules template.
Renewal Rules Template - Copy align billing from
The 'Copy align billing from' checkbox is unchecked by default for the existing renewal rules templates. When the 'Copy align billing from' checkbox is checked, the renewed subscriptions will have the 'Align Billing From' date copied over automatically from the source subscriptions.
Saves the trouble of manually adjusting the align billing from date of the renewed subscriptions post the subscription renewal.
Steps to Enable
You don't need to do anything to enable this feature.
Enable Audit on Product Status
This feature lets you view the audit history of the subscription product status changes that take place during the subscription life cycle.
Easier traceability and reporting
Steps to Enable
You don't need to do anything to enable this feature.
Streamlined Subscription Attributes
Some of the attributes that belong to the Subscription, Subscription Product, Subscription Associated Assets, Subscription Bill Lines, Subscription Charges are streamlined to avoid inadvertent use by the users. This streamlining process includes 1. Obsoleting some unused attributes 2. Making some attributes read-only post creation, and 3. Making some attributes editable conditionally.
If any of the existing business logic is based on the above attribute categories, you must reconsider alternate ways of handling the same.
Robust subscription objects and attributes that avoid inadvertent use.
Steps to Enable
You don't need to do anything to enable this feature.