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 |
---|---|---|---|
02 JUN 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 |
|
||
Configurable Renewal Consolidation Rules based on Custom and Additional Standard Attributes |
||||||
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 use this feature 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.
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 into the future for subscriptions till a certain date into the future. 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.
Configurable Renewal Consolidation Rules based on Custom and Additional Standard Attributes
You can use Bill-to Customer and Ship-to Account in addition to the existing criteria for renewal consolidation. You can additionally have one or more subscription product level custom attributes as renewal consolidation criteria.
You can specify Bill-to Customer, Ship-to Account and any subscription product level custom attributes as additional renewal consolidation criteria in the renewal rules template. Please note that, for this criteria to take effect, 'Consolidate Subscriptions' check box should be checked for the renewal rules template.
Renewal Rules Template - Additional Consolidation Criteria
Gives more flexibility in deciding the renewal consolidation criteria
Steps to Enable
You don't need to do anything to enable this feature.
Specify Balance Type of Manual Credit Memo
You can now select the balance type of a manual credit memo. You can select a positive or a negative balance when you create a manual credit memo. Subscription management will automatically prefix the sign to the credit balance. This way, you can choose the correct sign of the credit memo based on your intent of creating the credit memo.
Credit Memo Popup
1. Users will be clear about the credit memo balance type to choose based on their intent.
Steps to Enable
You don't need to do anything to enable this feature.
Request for Approving Transaction from Invoice Workbench
You can now request for approval to complete the Invoice transaction from the Invoice Workbench. Based on the approval rules of your organization you may setup different rules for approval using the attributes of the subscription. Upon approval of the request the invoice transaction is marked as Complete.
You also withdraw the request for approval. You can also bypass the request for approval based on privilege assigned to you. The Invoice Workbench will show the status of the approval request. Upon rejection you can resubmit for approval.
When an invoice is requested for approval the Transaction Completion Approval Status is Pending Approval. It can be approved or rejected.
Invoice Workbench
1. You can request for approval of an invoice from Subscription Management.
2. You can setup approval rules based on subscription attributes.
3. You can request for approval in bulk.
4. You can withdraw request for approval in bulk.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- You should have the privilege Manage Invoice Workbench should be assigned to you is you have to access to the Invoice Workbench.
- You should have the privilege Complete Invoice Transaction assigned to you if you want to complete the invoice.
- You should set the profile option Complete Transaction Allowed to Yes for your user if you want to complete an invoice.
- Configure approval rules such that you always have an approver.
Update Subscription without Amendment
You can now update customer, billing and shipping information on a subscription without amending the subscription. You can update the bill-to-contact name, bill-to account, bill-to customer and bill-to site at subscription header. The ship-to party, bill-to account, bill-to customer, ship-to account, ship-to contact, bill-to contact, bill-to site and ship-to site can be updated in the subscription product line. These fields will be updatable when the subscription is in Under Amendment, Active, Expired and Closed status.
1. Update customer details without amending subscription thereby avoiding giving credit to customers during termination of subscription.
2. Use the new customer details in bill lines that are not interfaced to Oracle Accounts Receivables.
Steps to Enable
1. Navigate to Setup and Maintenance
2. Select task Manage Administrator Profile Values
3. Search for profile option Update Customer without Amendment Allowed.
4. Set the value of the profile option to 'Yes' and save the changes..
Tips And Considerations
The profile option Update Customer without Amendment Allowed should be set to 'Yes' if you want to update these fields in the subscription without amending the subscription.
Bill Total Charge Amount for One Time Charge
Define the total charge amount for the entire subscription term. You can specify the amount you want to bill for a given one time charge. Any difference between the total charge amount provided by you and what's billed by the application is reconciled by making a billing adjustment for the last billing period.
Total Charge Amount
For example, consider a 3-month subscription with a one time charge of $500 and a charge adjustment of type price override of $2500 with the following subscription product fields:
Product | Quantity | Start Date | End Date | Billing Frequency | Invoicing Rule | Billing Date | Period Start |
---|---|---|---|---|---|---|---|
Product1 | 1 | 17-Jan-23 | 16-Apr-23 | Month | Advance | Period Start | Service Start |
Pricing for the above product:
Charge | Enable Periodic Billing | List Price | Charge Adjustment | Value |
---|---|---|---|---|
Activation Fee | Y | $500 | Price Override | $2500 |
The billing summary for this product line would be generated as follows:
Period | Charge | Sequence | Interface Date | Bill-from Date | Bill-to Date | Amount |
---|---|---|---|---|---|---|
1 | Activation Fee | 1 | 17-Jan-23 | 17-Jan-23 |
16-Feb-23 | $833.33 |
2 | Activation Fee | 2 | 17-Feb-23 | 17-Feb-23 |
16-Mar-23 | $833.33 |
3 | Activation Fee | 3 | 17-Mar-23 | 17-Mar-23 |
16-Apr-23 | $833.33 |
Here, the total charge amount billed by the application is $2,499.99.
Let’s assume you want to charge only $2,500 for this subscription. You can pass 2500 as the Total Charge Amount for your Activation Fee and the billing summary will be generated as follows:
Period | Charge | Sequence | Interface Date | Bill-from Date | Bill-to Date | Amount |
---|---|---|---|---|---|---|
1 | Activation Fee | 1 | 17-Jan-23 | 17-Jan-23 |
16-Feb-23 | $833.33 |
2 | Activation Fee | 2 | 17-Feb-23 | 17-Feb-23 |
16-Mar-23 | $833.33 |
3 | Activation Fee | 3 | 17-Mar-23 | 17-Mar-23 |
16-Apr-23 | $833.34 |
The amount of the last billing period was adjusted to ensure that application bills a total charge amount of $2,500, as defined by you.
You can use this feature to ensure there's no difference between the subscription amounts quoted to your customers and the amount billed by Oracle Subscription Management.
Steps to Enable
You don't need to do anything to enable this feature.
Manage Allowances on Various Subscription Life Cycle Events
This feature enables the carrying forward of the entitlement plan and adjustment of allowances during various subscription lifecycle events such as renewal, amendment, close, suspend and resume.
For example, consider a 1 year subscription with an allowance of 100 GB every month with an rollover of 1month.
Product | Start Date | End Date | Charge Frequency | Charge Name |
---|---|---|---|---|
P1 | 01-Jan-23 | 31-Dec-23 | Monthly | Backup Service |
Allowance Details for the above product:
Balance Code | Allowance Quantity | Allowance Start Date | Allowance End Date | Rollover End Date |
---|---|---|---|---|
Backup Service |
100 | 01-Jan-23 |
31-Jan-23 |
28-Feb-23 |
Amendment:
We are amending the subscription on 15-Jan-23. The source line will be closed on 15-Jan-23 and the allowance will be prorated accordingly.
Product |
Start Date |
End Date |
Close Date | Charge Frequency |
Charge Name |
Amendment Date |
---|---|---|---|---|---|---|
P1 |
01-Jan-23 |
31-Dec-23 |
14-Jan-23 |
Monthly |
Backup Service |
15-Jan-23 |
Balance Code | Allowance Quantity | Allowance Start Date | Allowance End Date | Rollover End Date |
---|---|---|---|---|
Backup Service |
50 | 01-Jan-23 |
31-Jan-23 |
28-Feb-23 |
The amended line allowance starts from 16-Jan-23 and allowance quantity for this line is the remaining allowance quantity from the source line.
Product | Start Date | End Date | Charge Frequency | Charge Name |
---|---|---|---|---|
P1.1 | 16-Jan-23 | 31-Dec-23 | Monthly | Backup Service |
Balance Code | Allowance Quantity | Allowance Start Date | Allowance End Date | Rollover End Date |
---|---|---|---|---|
Backup Service |
50 | 16-Jan-23 |
31-Jan-23 |
28-Feb-23 |
Renewals:
We are renewing the subscription as on 15-Dec-23.
Product | Start Date | End Date | Charge Frequency | Charge Name |
---|---|---|---|---|
P1 | 01-Jan-23 | 31-Dec-23 | Monthly | Backup Service |
Balance Code | Allowance Quantity | Allowance Start Date | Allowance End Date | Rollover End Date |
---|---|---|---|---|
Backup Service |
100 | 01-Jan-23 |
31-Jan-23 |
28-Feb-23 |
The renewed subscription allowance will start from 01-Jan-24 and will follow the same allowance frequency as the source subscription.
Product | Start Date | End Date | Charge Frequency | Charge Name |
---|---|---|---|---|
P1 | 01-Jan-24 | 31-Dec-24 | Monthly | Backup Service |
Balance Code | Allowance Quantity | Allowance Start Date | Allowance End Date | Rollover End Date |
---|---|---|---|---|
Backup Service |
100 | 01-Jan-24 |
31-Jan-24 |
28-Feb-24 |
Suspend & Resume:
We are suspending the subscription on 15-Jan-23. The source line will be closed on 15-Jan-23 and the allowance will be prorated accordingly.
Product |
Start Date |
End Date |
Charge Frequency |
Charge Name |
Suspended Date |
---|---|---|---|---|---|
P1 |
01-Jan-23 |
31-Dec-23 |
Monthly |
Backup Service |
15-Jan-23 |
Balance Code | Allowance Quantity | Allowance Start Date | Allowance End Date | Rollover End Date |
---|---|---|---|---|
Backup Service |
100 | 01-Jan-23 |
31-Jan-23 |
28-Feb-23 |
We are resuming the suspended line on 16-Jan-23 and allowance quantity for this line is the remaining allowance quantity from the source line.
Product | Start Date | End Date | Charge Frequency | Charge Name |
---|---|---|---|---|
P1.1 | 16-Jan-23 | 31-Dec-23 | Monthly | Backup Service |
Balance Code | Allowance Quantity | Allowance Start Date | Allowance End Date | Rollover End Date |
---|---|---|---|---|
Backup Service |
50 | 16-Jan-23 |
31-Jan-23 |
28-Feb-23 |
Close:
We are closing the subscription on 15-Jan-23. The source line will be closed on 15-Jan-23 and the allowance will be prorated accordingly.
Product | Start Date | End Date | Charge Frequency | Charge Name | Close Date |
---|---|---|---|---|---|
P1 |
01-Jan-23 |
31-Dec-23 |
Monthly |
Backup Service |
15-Jan-23 |
Balance Code | Allowance Quantity | Allowance Start Date | Allowance End Date | Rollover End Date |
---|---|---|---|---|
Backup Service |
50 | 01-Jan-23 |
14-Jan-23 |
14-Feb-23 |
Allows tracking of quantity-based allowances and usages in a balance register, and rate the excess usage quantity to determine the usage charge for the usage event.also we can carryforward of the entitlement plan and adjustment of allowances during various subscription lifecycle events such as renewal, amendment, close, suspend and resume.
Steps to Enable
You don't need to do anything to enable this feature.