- Revision History
- Overview
- Feature Summary
- Accounting Foundation
-
- Accounting Foundation
-
- Automation of Creation of BI Cloud Connector Extract Jobs
- Ingestion of Journals from Oracle ERP
- Usage of Journals Ingested from ERP for Instrument-Balance Computation
- Flexible Publishing of Events and Journals to ERP AHCS
- Ability to Modify SLA Definition Post Publishing
- Availability of Public API Endpoints
- Enhanced Governance Workflow
- Verification of Control Information While Ingesting Data
- Additional Data Quality Checks
- Availability of Additional Public API Endpoints
- Support for New Dimensions in Catalog
- Support for New Dimensions in Reconciliation
- Improved Logging for Connector Executions
- Metadata Updates in Hierarchy for Reconciliation
-
- Accounting Foundation
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 |
|---|---|---|---|
| 02 SEP 2022 | Usage of Journals Ingested from ERP for Instrument-Balance Computation |
Updated document. Revised feature information to include content for version 22.8.1. |
|
| 03 AUG 2022 | Additional Data Quality Checks | Updated document. Revised feature information to include content for version 22.7.1. | |
| 03 AUG 2022 | Updated document. Revised feature information. | ||
| 03 AUG 2022 | Support for New Dimensions in Catalog | Updated document. Delivered new feature from version 22.7.1. | |
| 03 AUG 2022 | Support for New Dimensions in Reconciliation | Updated document. Delivered new feature from version 22.7.1. |
|
| 03 AUG 2022 | Improved Logging for Connector Executions | Updated document. Delivered new feature from version 22.7.1. |
|
| 03 AUG 2022 | Updated document. Delivered new feature from version 22.7.1. | ||
| 18 JUL 2022 | Ingestion of Journals from Oracle ERP | Updated document. Revised feature information. | |
| 18 JUL 2022 | Flexible Publishing of Events and Journals to ERP AHCS | Updated document. Revised feature information. |
|
| 14 JUL 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 fsgbu-mrf-communications_in@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 |
|
||
Usage of Journals Ingested from ERP for Instrument-Balance Computation |
||||||
Automation of Creation of BI Cloud Connector Extract Jobs
The BICC Extract Jobs for balance, journals and code combinations data will now be automatically created.
- Extract Job for Journals - JOURNAL_INGESTION_EXTRACT_JOB
- Extract Job for GL balance - GL_SR_EXTRACT_JOB
Steps to Enable
- Navigate to the Administration Window and select ERP Settings.
- Click the Save Button.
You will get a confirmation message, once the BI Cloud Connector (BICC) extract jobs are successfully created.
Key Resources
Ingestion of Journals from Oracle ERP
AFCS will now support extraction of journals from ERP and its ingestion into the AFCS through the ERP Journal Ingestion Process.
Performs the following tasks:
- Extract Journal Headers, Journal Lines, Code Combinations, Transaction Entities and Ledgers from the BI Cloud Console.
- Populate ERP Journals into the AFCS Data Store.
- Run Data Quality Checks on Journals received.
- Decompose Grouped Journals.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See Journal Ingestion.
Usage of Journals Ingested from ERP for Instrument-Balance Computation
AFCS will now support decomposition of journals from ERP for use in instrument-grain balance computation.
This functionality is currently limited to the following Products in the Catalog:
- Loans
- Current & Savings Accounts
- Bills
- Forex
- Investments
This functionality also supports Passthrough journals received from ERP. This feature is available as part of the 22.8.1 monthly patch of this 22B release.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See Journal Ingestion.
Flexible Publishing of Events and Journals to ERP AHCS
AFCS will now support publishing of events or pass-through journals for a given SLA multiple times for a given as-of date.
Only data that is an increment over the previous publication is added increasing the efficiency.
Steps to Enable
NOTE: You are not required to perform any action to enable Flexible Publication in new SLAs or SLAs that are not in the 'Available' State.
To enable Flexible Publication for SLAs in the 'Available' State, perform the following steps:
- Open the SLA and navigate to the Review Section.
- Click the Unpublish Button. The status of the SLA will change to 'Configured'.
- Re-configure the SLA.
- Click the Publish Button.
Key Resources
- See Publishing SLAs and Unpublishing SLAs.
Ability to Modify SLA Definition Post Publishing
AFCS will now support modification of mapping and grouping information for previously published SLAs.
Users can modify the Heading and Line Mappings in the published SLAs.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See Unpublishing SLAs.
Availability of Public API Endpoints
AFCS will now have API endpoints for a set of functions.
- The PAR URL for File Operations API creates a PAR File that you can use to perform file operations in the Object Store for end-to-end integrations.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
AFCS now supports an approval workflow for Issues and Actions.
Users can approve and reject the actions submitted for the corresponding issues in the application.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Verification of Control Information While Ingesting Data
AFCS will now support verification against Control Information while ingesting source data files.
The following Control Information is supported:
- Record count
- Aggregates of numeric values (sum, maximum, minimum, and average)
- Error threshold
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See Journal Ingestion.
Additional Data Quality Checks
AFCS will now provide an enhanced set of list-of-values DQ checks.
These DQ checks will ensure that values captured against specific business terms are restricted to Catalog-permitted lists.
These DQ Checks ensure that the values captured against specific business terms are restricted to the referenced dimensions. This feature is available as part of the 22.7.1 monthly patch of this 22B release.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See Data Quality Checks.
Availability of Additional Public API Endpoints
AFCS now provides APIs to do the following:
- Retrieve data from entities loaded through Data Ingestion Connectors.
- Allow initiation of processes.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Support for New Dimensions in Catalog
AFCS additionally supports the following dimensions in this release for Catalog:
- Business Unit
- Channel
Steps to Enable
You don't need to do anything to enable this feature.
Support for New Dimensions in Reconciliation
AFCS additionally supports the following dimension in this release for Reconciliation:
- Business Unit
Business Unit Dimension is added as an Optional Dimension. Customers can now choose Business Unit as a Reconciliation Dimension during the rule creation process on the User Interface.
Steps to Enable
You don't need to do anything to enable this feature.
Improved Logging for Connector Executions
AFCS now has enhanced Connector execution logs.
- Provides detailed information on the execution process and the errors encountered.
Steps to Enable
You don't need to do anything to enable this feature.
Metadata Updates in Hierarchy for Reconciliation
AFCS now provides Parent-Child hierarchies for Reconciliation.
In other words, the Legal Entity and GL Code is enabled to read the entire set of the hierarchy nodes by Effective Date. The snapshot of the entire hierarchy is read by the latest Effective Date.
Steps to Enable
You don't need to do anything to enable this feature.