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 |
|---|---|---|
| 09 JUN 2020 | Import Accounting Hub Reversal Transactions with User-Specified Reversal Date | Updated document. Revised Tips and Considerations section. |
| 06 MAR 2020 | 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.
Join Oracle Cloud Customer Connect
Please take a moment to join the Cloud Customer Connect forums for Financials Cloud. Oracle Cloud Customer Connect is a community gathering place for members to interact and collaborate on common goals and objectives. This is where you will find the latest release information, upcoming events, or answers to use-case questions. Joining takes just a few minutes. Join now!
https://cloud.oracle.com/community
Security and New Features
The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)
If you have created job roles, then you can use this information to add new privileges to those roles as needed.
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.
Optional Uptake of New Features (Opt In)
Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users by stepping through the following instructions:
Access the Opt In page from the New Features Work Area
- Click the Navigator, and then click New Features (under the My Enterprise heading)
- On the New Features page, select the offering that includes new features you’d like to review
- Click Go to Opt In for any feature you want to opt in
- On the Edit Features page, select the Enable option for the feature, and then click Done
Opt In Expiration
Occasionally, features delivered Disabled via Opt In may be enabled automatically in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially auto enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.
Column Definitions:
Features Delivered Enabled
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. |
Action is Needed 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 |
|
||
Import Accounting Hub Reversal Transactions with User-Specified Reversal Date |
||||||
Import Accounting Hub Reversal Transactions with User-Specified Reversal Date
Configure an accounting rule to use a user-specified source as the reversal accounting date for Accounting Hub transactions. This provides you the flexibility to use other date sources as the accounting date for both original and reversal transactions.
You can configure the accounting date of subledger journal entries to not depend on transaction date and use the accounting date for reversal transactions too.
You can use this feature to account for back dated transactions. Keep the original transaction date for reference and account for back dated transactions in the current accounting period.
To do this, select a date source other than the predefined Transaction Date source for the Accounting Date accounting attribute.
Subsequently, use the date source in the journal entry rule set assignments to derive the accounting date.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
You don't need to do anything to enable this feature. It is available automatically for customers who have enabled the Transaction Reversal feature from update 19B.
You should ensure that the accounting date source value is from an open or future enterable accounting period. Otherwise, transactions are flagged as invalid. In such cases, you can use the Accounting Hub Maintenance process in the Purge invalid transactions mode to delete invalid transactions, adjust dates in the data file, and then import the transactions again.