This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Product | Feature | Notes |
---|---|---|---|
04 SEP 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 using the following privileges:
- Review Applications Offering (ASM_REVIEW_APPLICATIONS_OFFERINGS_PRIV)
- Configure Oracle Fusion Applications Offering (ASM_CONFIGURE_OFFERING_PRIV)
Here’s how you opt in to new features:
- Click Navigator > My Enterprise > New Features.
- On the Features Overview page, select your offering to review new features specific to it. Or, you can leave the default selection All Enabled Offerings to review new features for all offerings.
- On the New Features tab, review the new features and check the opt-in status of the feature in the Enabled column. If a feature has already been enabled, you will see a check mark. Otherwise, you will see an icon to enable the feature.
- Click the icon in the Enabled column and complete the steps to enable the feature.
For more information and detailed instructions on opting in to new features for your offering, see Offering Configuration.
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 in this update, 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 automatically enabling the feature. You can also click here to see features with current Opt In Expirations across all Oracle Cloud Applications. Beyond the current release, the Financials forums on Cloud Customer Connect have details of Opt In Expirations upcoming in future releases.
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 |
|
||
Corrective Actions for Accounting Hub Exceptions
Review accounting exceptions and their recommended corrective actions for Accounting Hub and Oracle subledgers. With the required privilege, General Ledger users can also navigate to relevant configuration tasks, resolve the error, and submit the accounting process again.
From the General Ledger Journals work area, select the Manage Accounting Errors task. On the Manage Accounting Errors page, search for errors in primary ledgers and subledgers. Optionally you can narrow down the search result by error category.
NOTE: When you search for exceptions in a primary ledger, accounting errors in the subledger-level reporting currency or secondary ledgers are also displayed.
You can review the recommended action and alternate actions and determine which one is more appropriate for the exception scenario. Depending on the error and the action you decide to take, you select the recommended action or manually navigate to the required task to make the correction. You can also select the Action Taken check box to mark whether the corrective action has been performed for the particular error. Later, when you search again for errors with the value of action taken as No, the errors for which corrective action has not been taken are displayed. This helps you focus on errors that still require your attention.
After you have corrected the accounting errors, you can submit the Create Accounting or Create Multiperiod Accounting process again for the erroneous records by selecting the Action button. Use any of the following options to run these processes:
- Select Create Accounting to submit the Create Accounting process in Final mode and close all error records up to the current date.
-
Select Create Draft Accounting to submit the Create Accounting process in Draft mode and close all error records up to the current date.
-
Select Create Accounting and Replace Invalid Account to submit the Create Accounting process in Final mode and close all error records up to the current date. In this case, if an invalid account is encountered, the application replaces the invalid account with the suspense account defined for the ledger.
-
Select Create and Post Multiperiod Accounting to submit the Create Multiperiod Accounting process in Final mode and transfer the multiperiod journals to General Ledger.
-
Select Create Draft Multiperiod Accounting to submit the Create Multiperiod Accounting process in Draft mode.
After General Ledger transfer errors have been corrected, you can navigate to the Scheduled Processes task and submit the Post Subledger Journal Entries process to transfer all eligible subledger journals to General Ledger.
The Manage Accounting Errors page allows you to streamline and centralize the exception handling process. You can now view all accounting exceptions for a particular ledger and subledger in one page, review, and take suggested action to resolve the issue.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- This feature is available automatically for customers who have enabled the the feature 'Review and Correct Accounting Exceptions for Subledgers' from 20C.
- Accounting exceptions occurred before enabling the 'Review and Correct Accounting Exceptions for Subledgers' feature will not be displayed in the Manage Accounting Errors page unless accounting automation is enabled. However, you must submit the accounting process again after the feature is enabled to review existing accounting exceptions in the Manage Accounting Errors page.
- Purged accounting errors will not show in the Manage Accounting Errors page. Use the Accounting Hub Maintenance process execution report instead to review purged accounting errors when invalid transactions have been purged manually or if the Automatically delete invalid transactions option is enabled for the Accounting Hub subledger.
- The Manage Accounting Errors page can only display up to 1000 records. When you resolve these errors and create accounting again, other error records will be displayed on the page as the one you corrected will be removed unless the issue is not fully resolved yet. Alternately, select the Export to Excel option to export all the accounting errors to a spreadsheet.
- Optionally, you can also update the Action Taken checkbox after you've corrected an error and search by action not taken yet to focus on outsatanding errors.
- Use the Transaction Information field in the Search section to search for accounting errors for a particular transaction. Enter a number that can identify the transaction, for example, the invoice number or receipt number.
Key Resources
- Watch Review and Correct Accounting Exceptions for Subledgers Readiness Training
- Oracle Accounting Hub Cloud What’s New for Update 20C: Export Accounting Errors When Purging Invalid Accounting Hub Transactions