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 |
|---|---|---|---|
| 18 MAR 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.
NOTE ABOUT DOCUMENTATION AVAILABILITY
Some of the documentation referenced in this article may not be available until after general availability of the release update on April 1. Check back after general availability for complete information.
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 |
|
||
Use Invoice Payment Status to Create On-Account Credit Memos |
||||||
Use Custom Attributes in Coverage Template to Filter Entitlements |
||||||
Update Warranty Effectivity Based on Asset Installation Date |
||||||
Define the total charge amount for the entire subscription term. You can specify the amount you want to bill for a given recurring 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 monthly charge of $1,000 with the following subscription product fields:
| Product | Quantity | Start Date | End Date | Billing Frequency | Invoicing Rule | Billing Date |
|---|---|---|---|---|---|---|
| Product 1 | 1 | 15 Jan 22 | 14 Apr 22 | Month | Advance | Period Start |
Pricing for the above product:
| Charge | Periodicity | List Price |
|---|---|---|
| Recurring Fee | Month | 1000 |
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 |
Recurring Fee |
1 |
15-Jan-21 |
15-Jan-21 |
31-Jan-21 |
$548.39 |
| 2 |
Recurring Fee |
2 |
1-Feb-21 |
1-Feb-21 |
28-Feb-21 |
$1,000.00 |
| 3 |
Recurring Fee |
3 |
1-Mar-21 |
1-Mar-21 |
31-Mar-21 |
$1,000.00 |
| 4 |
Recurring Fee |
4 |
1-Apr-21 |
1-Apr-21 |
14-Apr-21 |
$466.67 |
Here, the total charge amount billed by the application is $3,015.50.
Let’s assume you want to charge only $3,000 for this subscription. You can pass 3000 as the Total Charge Amount for your Recurring Fee and the billing summary will be generated as follows:
| Period |
Charge |
Sequence |
Interface Date |
Bill-from Date |
Bill-to-Date |
Amount |
| 1 |
Recurring Fee |
1 |
15-Jan-21 |
15-Jan-21 |
31-Jan-21 |
$548.39 |
| 2 |
Recurring Fee |
2 |
1-Feb-21 |
1-Feb-21 |
28-Feb-21 |
$1,000.00 |
| 3 |
Recurring Fee |
3 |
1-Mar-21 |
1-Mar-21 |
31-Mar-21 |
$1,000.00 |
| 4 |
Recurring Fee |
4 |
1-Apr-21 |
1-Apr-21 |
14-Apr-21 |
$451.62 |
The amount of the last billing period was adjusted to ensure that application bills a total charge amount of $3,000, 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.
Key Resources
- See the "Bill Total Charge Amount" topic in the "Subscription Pricing and Billing" chapter in the Using Oracle Subscription Management guide. This topic will be available on April 1 on Oracle Help Center.
Withhold Sending Billing Information to Oracle Receivables
Withhold sending billing information to Oracle Receivables based on custom conditions. You can set up these conditions in the Subscription Management and Oracle Receivables integration algorithm so that billing lines are not interfaced unless the custom conditions are met.
You can choose which bill lines are included in the invoice based on business requirements.
Steps to Enable
Here are the steps to be followed to enable this feature.
- Sign in as a setup user.
- Go to the Subscription Management work area.
- On the Subscriptions landing page, click the Subscription Configuration tab.
- Click Manage Algorithms.
- Select the Subscription Management and Accounts Receivables Integration algorithm row and click Actions > Create Version to create a new version of the base algorithm.
- Click on the latest version of the algorithm Subscription Management and Accounts Receivables Integration to edit it.
- On the Edit Algorithms: Subscription Management and Accounts Receivables Integration page, select the Variables tab.
- Change the default value of CustomizationFlag from false to true.
- Perform customizations as per business requirement, click Save and Close.
- From the Manage Algorithms page, click Actions > Publish.
Tips And Considerations
You can use any of the standard attributes or define your custom attributes in the subscription header, product, covered level or bill lines, map them in service mapper and define the custom logic in the Subscription Management and Accounts Receivables Integration algorithm to skip sending bill lines to accounts receivables.
Key Resources
- A use case on how to skip a selected bill line from interfacing to Account Receivables is explained in the whitepaper, "Customizing Subscriptions-Account Receivables Integration".
- For more information, see the "Create and Manage Account Receivables Service Mappings" topic in the "Configure Subscriptions" chapter in the Implementing Oracle Subscription Management guide.This topic will be available on April 1 on Oracle Help Center.
Use Invoice Payment Status to Create On-Account Credit Memos
You can now use the subscription profile attribute, Credit Memo Option, to automatically create on-account credit memos during closure or amendment of subscriptions. This new attribute has three values:
- On-Invoice: The application creates a credit memo with reference to the subscription bill line invoice, irrespective of whether invoice is paid or not.
- On-Account: The application creates an on-account credit memo irrespective of whether the invoice is paid or not.
- Mixed: The application creates a credit memo with reference to the subscription bill line invoice if the invoice isn't paid. It creates an on-account credit memo if the invoice has been paid.
The application checks whether the invoice impacted by amendment or closure has been paid in full or not. It then creates a credit memo based on the Credit Memo Option field value.
This feature does not consider the Allow overapplication property of a transaction type defined in Accounts Receivable.
Customers can now issue on-account credit memos from Subscription Management based on the subscription profile. This way, customers can preferentially create on-account credit memos and credit memos against invoices based on whether or not an invoice is paid in full.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Invoices are considered paid when the balance amount of the invoice is zero. This means that partially paid invoices are considered unpaid invoices.
Key Resources
- See the "Create On-Account Credit Memos" topic in the "Create and Update Subscriptions" chapter in the Using Oracle Subscription Management guide. This topic will be available on April 1 on Oracle Help Center.
Use Custom Attributes in Coverage Template to Filter Entitlements
Choose the right coverage to be used for pricing and entitlements in B2B Service Cloud and Service Logistics.
You can enable custom attributes in the coverage template and write conditions in Groovy scripts using the custom attributes, according to your business requirements. This lets you conditionally discard certain coverages from the Entitlements payload.
By building code extensions, customers can now pick the right coverage template to be used for pricing the debrief lines. The coverage template exposes custom attributes that can be configured by customers, which can then be used to find the correct adjustment to be applied in pricing of charges in debrief lines.
You can now prevent the overapplication of pricing discounts by creating custom code in Groovy. You can implement any other business conditions to give precedence to particular coverages over other incase multiple coverages are eligible.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See the "Enable Entitlements Support for All Covered Levels" topic in the "Configure Subscriptions" chapter in the Implementing Oracle Subscription Management guide.
Update Warranty Effectivity Based on Asset Installation Date
Update warranty effectivity of an asset. You can update warranty effectivity automatically when you update the installed date of an asset and run the Reprocess Install Base Updates scheduled process. Keeping the duration constant, this updates warranty effectivity with the new installed date as the warranty start date.
You can use this feature if the shipment date of an asset is different from the installed date.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
After you update installed date of the asset, run the Reprocess Install Base Updates scheduled process to update the warranty effectivity.
Key Resources
- See the "Update Warranty Effectivity Based on Asset Install Date" topic in the "Coverage Services" chapter in the Implementing Oracle Subscription Management guide. This topic will be available on April 1 on Oracle Help Center.
Use Daily Rates to Prorate Billing for Partial Periods
Calculate billing amounts for partial periods by prorating by day. You can use a daily rate to compute prorated billing amounts for partial periods greater than a month by enabling the Prorate by day field. You can enable this new field in the subscription profile or for a given subscription product.
Prorate by Day in Subscription Profile Page
Prorate by Day in Subscription Product
When Prorate by day is enabled, billing amounts for partial periods are computed using daily rates. A partial period is a billing period for a given billing summary line which is of lesser duration than the periodicity of your charge.
Let's consider the example of a subscription product with a quarterly charge of $4,000 with the following fields:
| Product |
Quantity |
Start Date |
End Date |
Duration |
Period |
Align Billing From |
Bill Frequency |
Period Start |
Period Type |
Prorate by day |
| Product1 |
1 |
28-Jan-20 |
27-Jan-21 |
1 |
Year |
1-Jan-20 |
Quarter |
Service Start |
Actual |
Yes |
The billing summary for this subscription product will be generated as follows:
| Period |
Charge |
Sequence |
Interface Date |
Bill-from Date |
Bill-to-Date |
Amount |
End of Full Period |
Days in Partial Period |
Total Days in the Period |
Amount Calculation |
| 1 |
Support Fee |
1 |
28-Jan-20 |
28-Jan-20 |
31-Mar-20 |
2813.19 |
4/27/20 |
64 |
91 |
64/91*4000 |
| 2 |
Support Fee |
2 |
1-Apr-20 |
1-Apr-20 |
30-Jun-20 |
4000.00 |
||||
| 3 |
Support Fee |
3 |
1-Jul-20 |
1-Jul-20 |
30-Sep-20 |
4000.00 |
||||
| 4 |
Support Fee |
4 |
1-Oct-20 |
1-Oct-20 |
31-Dec-20 |
4000.00 |
||||
| 5 |
Support Fee |
5 |
1-Jan-21 |
1-Jan-21 |
27-Jan-21 |
1200.00 |
3/31/21 |
27 |
90 |
27/90*4000 |
In the billing summary above, we see two bill lines with partial periods of 28-Jan-20 to 31-Mar-20 and 1-Jan-21 to 27-Jan-21. For these bill lines, we compute the number of days had this been a full charge period and we compute the number of days in the actual billing period. We compute the billing amount using the following formula:
Amount = (Number of days in Actual Billing Period / Number of days in Full Charge Period) * by the Charge Price.
NOTE: The number of days in the full charge period will be calculated based on your Period Type selection of Actual vs Fixed.
You have additional flexibility to bill your customers for partial periods based on the rules defined by your business teams.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
You can only enable the Prorate by day field for subscription-type of products.
Key Resources
- See the "Partial Period Billing" topic in the "Subscription Pricing and Billing" chapter in the Using Oracle Subscription Management guide.