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 |
|---|---|---|---|
| 05 APR 2023 | Subscription Management | Retain Subscription Number During Renewal | Updated document. Delivered new feature in update 22D. |
| 15 SEP 2022 | 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 |
|
||
Edit Standard Coverage of Subscriptions with Included Warranty |
||||||
Retain Subscription Number During Renewal
Use the Renewed Subscription Number and Number Separator attributes when you create or edit a renewal rules template, to create the subscription number of the renewed subscription.
Renewal Template
Note: Renewed Subscription Number and Number Separator attributes will not be displayed if the consolidate subscription checkbox is checked.
The new subscription number includes the combination of the retained subscription number, the number separator value, and a running number sequence.
Steps to Enable
You don't need to do anything to enable this feature.
Edit Standard Coverage of Subscriptions with Included Warranty
Convert a standard coverage template from the Coverage tab of a subscription with included warranty. When you edit a standard coverage template, the application converts it into a nonstandard template.
Asset Lifecycle Management
You can now customize the standard coverage of a subscription with included warranty. You can modify customer specific entitlements.
Steps to Enable
You don't need to do anything to enable this feature.
Use Milestones to Bill Subscriptions and Recognize Revenue
Use mutually agreed upon milestones to bill your customers and recognize revenue based on milestones prescribed by your finance team. You can define milestones according to your business needs while configuring subscriptions. This lets you associate a milestone template with a one-time charge for a subscription product, which is billed when you and your customer both agree that the milestone has been reached. You can define revenue recognition milestones and capture their completion dates when the milestones are reached. You can track these milestones through the lifecycle of a subscription using Import Management, REST APIs, or from the UI.
This feature does not enable integration with Oracle Fusion Cloud Project Management and the milestones defined in Oracle Subscription Management are not shared with Oracle Fusion Cloud Project Management.
The milestones are defined using a Billing and Revenue Recognition Milestone Template under Subscription configuration.
Billing and Revenue Recognition Milestone Template
In a subscription, the template be can selected for a one-time charge. The template can be specific to the subscription, thereby creating a template instance.
Editing a Template in a Subscription
You can change the percentages and milestones for both billing and revenue recognition. On completion of a milestone, the Completion Date can be populated to set the Interface Date for billing. The Completion Date for Revenue milestone is considered as the satisfaction event date, since each milestone is a satisfaction event in Oracle Revenue Management Cloud.
You can now bill your customers based on completion of agreed milestones.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
If you want to bill your customers based on milestones, it's recommended that you create separate subscription products for each milestone-based charge.
Select Charge Adjustment Reason from a List
Capture a reason for a charge adjustment from a finite list of options.
With the reason description, it's not possible to summarize why the charge adjustments were given. Capturing a coded reason helps with reporting and analysis.
Coded Adjustment Reason
Capturing a coded reason helps with the reporting and analysis.
Steps to Enable
You don't need to do anything to enable this feature.
Add Custom Subscription Validations
Add custom subscription validations that cater to your individual business needs using the object functions in Application Composer.
For example, you could create validations that specify:
- The application enables a custom field if the product is x
- A line can't be pending activation if its Bill Immediately is enabled
This enhancement gives you the flexibility to create and use custom subscription validations.
Steps to Enable
Leverage Application Composer to expose and adjust page layout and attributes. To learn more about extending your application using Application Composer, visit Oracle Help Center > your apps service area of interest > Books > Configuration and Extension.
Here's how to create custom subscription validations:
- From the Application Composer, pick the Subscriptions object and create an object function with the name customSubscriptionValidations.
- Write Groovy scripts for each of the custom validations intended. For these custom validations, use the addCustomValidationResults or addBulkCustomValidationResults function, depending upon the volume of the data considered for validation.
- Invoke the custom validations within the object function customSubscriptionValidations.
Capture Reason Description for Cancel and Close
Capture a reason description that explains why a subscription, a subscription product, or a covered level is being closed or cancelled. This additional description can be useful for future reviews.
Close Subscription
Close Product
Close Covered Level
Mass Update - Close
Cancel Subscription
Cancel Product
Cancel Covered Level
Mass Update - Cancel
This enhancement lets you enter detailed justification or notes for why you're canceling or closing a subscription, a subscription product, or a covered level.
Steps to Enable
You don't need to do anything to enable this feature.
Apply Price Adjustments to Multiple Subscriptions
Apply price adjustments to recurring, one-time, or usage charges for multiple subscriptions. Additionally, you can also specify subscription products that should be included or excluded from the update. The price adjustments can be performed on subscriptions in Draft and Active status. All the adjustments on Active subscriptions are considered as subscription amendments. Any price adjustments applied will also be applicable for the covered levels in case of coverage subscription products. All changes are recorded for audit reporting.
Mass Price Change
It is common that subscription prices are periodically adjusted due to inflation, deflation or consumer price index changes. You can save time by using the feature to mass change prices across multiple subscription instead of individually amending every subscription.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- Ensure that you choose the right conditions so that you get the correct of subscriptions to be updated.
-
Charge adjustments are not applied to one-time charge if it has a Milestone Billing template.
-
Filter conditions of same type are matched using OR operator.
-
Filter conditions using different types are matched using AND operator.
Retrieve Additional Credit Card Details
You can retrieve information such as card holder name, expiration date, and card billing address about the credit card used as the payment method for a subscription. You can also use the Add to Billing Account field in REST to add a new credit card as a payment instrument for the billing account of a product instead of the billing site.
Currently, all credit card records captured during the subscription ordering process are always created as a payment method at the customer site level. Using this feature, you can choose to create the customer payment method either at the customer account level or the customer account site level.
Steps to Enable
You don't need to do anything to enable this feature.