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 |
|---|---|---|---|
| 14 DEC 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.
This section gives you information to help you plan, deploy, and validate your update. We make frequent additions to this document, so don’t forget to check back and get the latest information before your update starts.
Use the following resources to prepare for, deploy, and validate your update:
- Read Prepare for your Quarterly Update (Doc ID 2445338.1) on My Oracle Support to learn how to prepare for and validate your quarterly update.
- Publish or delete any in-progress sandboxes. Read the Overview of Sandboxes topic in the Configuring and Extending Applications guide for more information.
- Review the latest Known Issues and Update Documents for this release (Doc ID 1603154.1) on My Oracle Support.
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 |
|
||
Renew End-Dated Subscription Lines to Open-Ended Subscription Lines |
||||||
Close Suspended Subscriptions and Close Renewals of Suspended Subscriptions |
||||||
Renew End-Dated Subscription Lines to Open-Ended Subscription Lines
You can choose to renew subscription products that contain expiration dates to change them to subscription products that aren't restricted to specific end dates or times. By selecting a simple option, you can renew subscriptions without having to amend or edit the subscription details.
Subscription Renewal Settings
Edit Subscription Product Page
This feature can dramatically simplify the interactions between you and your customers by eliminating the need to manage a renewal process, in addition to reducing your customer churn.
Steps to Enable
You don't need to do anything to enable this feature.
Role And Privileges
There are no new roles required to access this check box.
Close Suspended Subscriptions and Close Renewals of Suspended Subscriptions
You can now close subscriptions that are in a suspended status, thus eliminating unnecessary revenue contract creation and closure. In addition, if you've renewed a subscription that you then later suspend, you can cancel or close the new product line that was created from the renewal. This means you can automatically cancel or close the subscription products created after a renewal, if the parent subscription is suspended.
You can automatically cancel or close the subscription products created after a renewal, if the parent subscription is suspended. Suspended subscriptions can be directly closed without having to resume them and close.
Steps to Enable
You don't need to do anything to enable this feature.
Generate Future Bill Lines for Evergreen Subscriptions
You can now generate bill lines into the future for evergreen subscriptions and termed subscriptions with a pricing term. A new ESS job Generate Bill Lines for Evergreen Subscriptions and Subscriptions with Pricing Terms will enable you to create bill lines for future periods till a certain date. Parameters in the ESS job will help you select specific subscriptions. So, now you can invoice your customers for future billing periods and apply payments to them.
1. Generate bill lines till a specific future date for evergreen subscriptions and termed subscriptions with pricing term.
2. Accept payment and apply them against the bill lines interfaced to Fusion Receivables.
Steps to Enable
You don't need to do anything to enable this feature.
Enable Minimum Commit for Asset based Meters
You can specify minimum amount, minimum quantity and estimation fields for a usage charge that is associated with an asset based meter.
Reading Minimum Value and Reading Maximum Value attributes which are defined in the meter template will not have any impact on minimum quantity and minimum amount attributes on the charge line.
Pricing Information
The precedence to apply minimum amount on a usage charge has been changed when there is an charge adjustment applied.
The logic is as follows (List Price - Discount) is less than minimum amount then minimum amount will be charged.
Minimum Commit Calculation
You can specify minimum amount, minimum quantity and estimation fields for a usage charge that is associated with an asset based meter.
Steps to Enable
You don't need to do anything to enable this feature.