This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Feature | Notes |
|---|---|---|
| 12 JUL 2019 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
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.
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.
| New Features Delivered Ready to Use 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. |
New Features That Customer Must Take Action to Use (Delivered Disabled) 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 |
|
||
Use Revenue Management Cloud Integration for Ad-Hoc Bill Adjustments and Charges |
||||||
Extend Integration with ERP Financials Cloud
Extend the supplied Oracle Subscription Management Cloud integration with Oracle ERP Financials Cloud. You can dynamically map subscription entities (such as the subscription header, lines, bill lines, and charges) to Financials Cloud Receivables entities. For example, you can map charge adjustments to Receivables invoice flexfields.
Extend Integration with Financials Cloud
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
You can find instructions for setting up custom Oracle ERP Cloud Financials service mappings in the Oracle Subscription Management Cloud Implementing Subscription Management guide.
For more information on Oracle Financials Cloud, see the Oracle Financials Cloud Getting Started with Your Financials Implementation guide and the Using Financials guide for your area.
These guides are available on Oracle Help Center.
Use Revenue Management Cloud Integration for Ad-Hoc Bill Adjustments and Charges
Subscription specialists often need to make ad-hoc adjustments during a subscription term, for example, where usage readings need to be corrected, penalties charged, or reimbursement given for loss of service. These billing adjustments impact the total contract value and recognizable revenue. You can use the supplied integration with Oracle Financials Cloud Revenue Management to automatically revise revenue contracts after these ad-hoc adjustments.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
See these Oracle Subscription Management Cloud guides on Oracle Help Center:
- Using Subscription Management
- Implementing Subscription Management
Search Based on Subscription Covered Levels
Search for subscriptions based on what's covered under the subscription. For example, you can search for subscriptions using the serial number of the asset that's covered.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
There are no required setup steps to enable this feature, but you can add additional search criteria and save and personalize your searches.
Key Resources
See these guides on Oracle Help Center:
- Oracle Engagement Cloud Implementing Sales
- Oracle Engagement Cloud Using Sales
- Oracle Subscription Management Cloud Using Subscription Management
Download the latest data model XML file using the mainline attribute information about a subscription and its child entities. You can then use the XML file in BI Publisher to create a new layout template for previewing or printing the subscription contract.
The XML file includes all standard and custom attributes. Standard child entities are included, as well as custom child entities created for a subscription through Application Composer.
Generate Data Model XML
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
You need to download the the BI Publisher Word Add-in if you have not yet edited your layout template.
Key Resources
See the Oracle Subscription Cloud Implementing Subscription Management guide available on Oracle Help Center.
Use Mass Update in Subscriptions
Update one or more fields for multiple subscription product lines and covered assets within a subscription at once. Renewal reps can select the rows to update and edit updatable fields for subscription products and covered assets in real time.
Mass Update Subscription Products
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Limit the number of records that can be updated. Since this is a synchronous operation, avoid updating more than 150 subscription products and covered assets at one time.
Key Resources
See the Oracle Subscription Management Cloud guides on Oracle Help Center:
- Implementing Subscription Management
- Using Subscription Management