Feature Summary

Features Delivered Disabled: Customer Action Required for Use

This table provides a summary of the features that require customer action before they can be used by end users. These features are delivered in a disabled state, and you can choose if and when to enable them.

Examples of such features include:

• New or expanded BI subject areas that need to be incorporated into reports
• Integration required to utilize new web services
• Features that must be assigned to user roles before they can be accessed

These features are non-disruptive since they remain inactive until you take action. You can selectively enable them, allowing you to set your own testing and rollout schedule.

Subscription Management

Feature	Action Required
Enable Prospective Accounting for Price Changes, Renewals, Amendments and Terminations	Service Request Required

Features Delivered Enabled: Ready for Use by End Users

This table provides a summary of the features included in the document that are ready to be used by end users.

The impact of these features can be categorized as follows:

• Larger Scale UI or Process-Based: These features have a higher potential impact on users due to their complex designs. Focus your acceptance testing on these features.
• Small Scale UI or Process-Based: These features have minimal impact on users and typically involve minor changes to fields, validations, or programs.
• Report: These features have minimal impact on users and include new or modified, Oracle-delivered, ready-to-run reports.

Subscription Management

Feature	Impact
Update Completion Date of Billing Milestones	Small scale
Skip Renewal Consolidation of Subscriptions	Small scale
Manage True-up of Usage Estimates and Commitments	Larger scale
Update Total Usage Charges for Subscription and Subscription Product	Small scale
Update Billing and Billing Interface Offsets from Mass Update UI	Small scale
Sell Coverage for Existing Assets from Order Management	Small scale
Renew Subscriptions from Order Management	Small scale