Release 22C

Revision History

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
01 DEC 2022		Result Area Entities	Updated document. Revised feature information.
25 NOV 2022		Restriction of User Activities when Catalog Extension is Ongoing	Updated document. Delivered new feature in 22.11.1.
25 NOV 2022		Data Extraction from ERP Financials Cloud when As-of and Calendar Dates do not Match	Updated document. Delivered new feature in 22.11.1.
25 NOV 2022		Data Lineage from ERP Financials Accounting Hub Cloud to AFCS	Updated document. Delivered new feature in 22.11.1.
25 NOV 2022		Extended List of Attributes corresponding to CoA Segments available in AFCS Reports	Updated document. Delivered new feature in 22.11.1.
25 NOV 2022		Result Area Entities	Updated document. Delivered new feature in 22.11.1.
07 OCT 2022		DQ Process and Engine Optimization	Updated document. Delivered new feature in 22C.
07 OCT 2022		Rerun, Resume, and Abort PMF Execution API	Updated document. Delivered new feature in 22C.
07 OCT 2022		PMF Execution Status API	Updated document. Delivered new feature in 22C.
06 OCT 2022		Additional Data Quality Checks	Updated document. Revised feature information.
06 OCT 2022		Exchange Rates Handling	Updated document. Revised feature information.
06 OCT 2022		Accounting Standard and Functional Currency Assignment for GL Balance and ERP Financials Cloud Journals	Updated document. Revised feature information.
06 OCT 2022		Standardized CoA Segments	Updated document. Revised feature information.
06 OCT 2022		Support for Multi-Ledger Deployments	Updated document. Revised feature information.
06 OCT 2022		Ledger Name Resolution for Publishing	Updated document. Revised feature information.
28 SEP 2022			Created initial document.

Overview

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.

Feature Summary

Accounting Foundation

Accounting Foundation

Ledger Name Resolution for Publishing

AFCS will support assignment of Ledger Name when journal and transaction data is published to Financials Cloud Accounting Hub. Such assignment is user-configurable based on SLA attributes mapped to Catalog business terms.

This enhancement will facilitate efficient support with multi-ledger Financials Cloud deployments.

NOTE: A maximum of 30 Catalog attributes can be used in combination to lookup Ledger Name.

Steps to Enable

• Unpublish existing SLAs
• Configure ledger-name lookup as per user guide
• Publish SLAs
• Assign values for lookup as per user guide
• No specific steps for the new SLA

Key Resources

• Ledger Name Assignment

Exchange Rates Handling

Scale and precision of Exchange Rate has been set to Number (30,11) to accommodate conversion rate values exceeding limits imposed by the previous version.

This enhancement allows for extended precision and scales to be assigned to currency conversion rates captured and processed in AFCS.

NOTE: Exchange Rate Business Term data length increased to support Number(30,11).

No impact on existing exchange rate data available on the system.

Steps to Enable

You don't need to do anything to enable this feature.

Population of Initial (Day 0) Balance for Management Ledger

Enhancements to the population of initial (day 0) balance have been made as follows:

• The initial balance for Management Ledger can now be ingested via a data file and automated processes thereafter.

• The initial balance should be provided with GL and customer accounts, alongside other relevant segment values.

• Balance information will need to be rendered via Accounting Entries as follows:
  • Balance against Asset, Expense, and Contra-Liability GL account types should be flagged as DR journal lines.
  • Balance against Liability, Revenue, Equity, and Contra-Asset should be flagged as CR journal lines.
  • Balance in Entered and Functional currencies should be provided.

This enhancement will provide a controlled mechanism for the provision of initial Management Ledger balance information.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Initial Instrument-Grain Accounting Balance for Management Ledger

Accounting Standard and Functional Currency Assignment for GL Balance and ERP Financials Cloud Journals

AFCS will now support establishing the Ledger dimension with user-specified values for Accounting Standard and Functional Currency. The values so specified will be assigned to ingested GL balance and journal data based on the lookup of the Ledger dimension rather than being required as part of code-combinations.

This enhancement will provide flexibility in establishing Chart of Accounts segments without impacting AFCS data requirements.

Steps to Enable

• Build Ledger dimension
• Ensure Consolidation Flag and Accounting Standard Code are populated as appropriate for each ledger

Key Resources

• Balance Reconciliation

Setting Journal and GL Balance As-Of Date

AFCS will support the run-time setting of As-Of date across the journal and GL balance ingestion from Financials Cloud. In the case of journal data, the AFCS Posting Date will also be set based on the As-Of date set at run-time and ERP Accounting Date.

The following logic will apply:

• As-Of Date is provided as a run-time parameter.

• When it concerns journals data:
  • If ERP Accounting Date is on or after run-time As-Of Date
    • As-Of Date and Posting Date are both set to ERP Accounting Date.
  • If ERP Accounting Date is prior to run-time As-Of Date
    • As-Of Date is set to the provided As-Of Date
    • Posting Date is set to ERP Accounting Date (indicating a back-dated journal line)

• When it concerns GL Balance data:
  • AFCS As-Of Date is recorded as the run-rime As-Of Date provided
  • GL Balance extract jobs will not permit extraction of balance ‘as of a prior date

This enhancement will facilitate flexibility in handling data movements that spill over calendar dates, while pertaining to a given as-of date.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Balance Reconciliation

Additional Data Quality Checks

AFCS will provide an enhanced list of data quality checks enforcing referential integrity constraints that ensure that, for example, ingested data has code values against attributes aligned with corresponding Dimensions.

This enhancement will facilitate data errors being identified and eliminated at the earliest possible stage in the data lifecycle.

NOTE: This is incremental to those delivered with the AFCS 22.7.1 Patch.

Additional referential integrity Data Quality checks for Business Terms Project Code, Ledger Identifier, Business Unit Code, Business Segment Code, and Location Code.

Steps to Enable

You don't need to do anything to enable this feature.

Decomposition for Catalog Product-Processor Entities Used in Sub Ledger Applications

AFCS will support the decomposition of journals resulting from grouped event information for all product processors in its Catalog that participate in publishing information via provided Sub Ledger Applications, for purposes of accounting balance computation at instrument-grain.

This enhancement will extend the coverage of journal-decomposition for balance computation to all participant product processor entities.

Steps to Enable

You don't need to do anything to enable this feature.

General Ledger to Management Ledger Reconciliation

AFCS will support the reconciliation of GL balance figures with ML and identify/log reconciliation breaks. This is in addition to the reconciliation of GL balance figures with Product Processors already available in the service.

This enhancement will facilitate additional rigor to the options available in establishing the quality and reliability of information managed in AFCS.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Ledger to Management Ledger Reconciliation

Execution of Multiple Reconciliation Rules in A Single Process

AFCS will now support the execution of multiple reconciliation rules in a single process as against the current requirement that each rule is executed in a separate process.

This enhancement will facilitate additional flexibility and convenience while configuring and executing reconciliation processes.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Execution of Rule

Catalog Content Extension

AFCS will support the extension of its Catalog’s content with the following user-defined artifacts:

• Business Terms
• Business Term to Entity association
• Dimensions against Business Terms

AFCS will also perform automated generation of Data Quality checks based on configured Business Term specifications.

This enhancement will allow users to extend Catalog content reflecting the service’s data model and leverage data elements proprietary to their business.

NOTE: Catalog extension will not permit user association of Business Terms directly with Dimension entities.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Catalog Extension

Discrete Error Identification, Logging and Response Steps While Ingesting Sourced Data

AFCS will separately identify and log:

1. Technical errors while reading source data files 

2. Referential-integrity errors upon loading destination Catalog entities

• Referential-integrity errors will be verified against user-configured error-thresholds.

This enhancement will allow clearer separation of data error types – technical and those related to constraints imposed by AFCS Catalog – and therefore facilitate more efficient resolution of the same.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Target Rejection Threshold

Explicit Environment Identification While Accessing AFCS UI

AFCS will now show the following details of the environment instance being accessed:

• Instance identifier
• Version
• Patch version

Subscribers will also be allowed to assign a unique name to each instance they are permitted access to.

This enhancement will make it easy for users allowed access to multiple AFCS instances (e.g., production, test and non-production) to identify the instance being accessed.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• User Group and User Role Mapping

Revised User Experience for File Operations

User experience has been enhanced with the ability to search for ingested, generated, or extracted files based on:

• Process / Task Execution ID
• Date-time range
• Size of file
• Name / name-pattern of file

UI-rendering performance while listing files has been improved.

This enhancement will improve user experience (speed and convenience) while dealing with file-operations via AFCS user interface.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• File Operations

Data Extraction Via Connectors for Catalog Entities in Staging and Results

AFCS will support extraction of data from Stating and Results entities into text files with user-configured Connectors. These Connectors will also automate additional lookup required while extracting Results data.

This enhancement will facilitate tactical extraction of catalogued AFCS data as text files.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Data Extraction

Data Visualization for Catalog Entities in Staging

AFCS will support user access to data content in Staging entities via Data Visualization. This facility will augment existing facilities of REST API with JSON response and newly introduced Data Extraction, listed below.

This enhancement will facilitate efficient, safe access to data in Staging for purposes of verification and validation.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Data Visualization Reports

Decomposition of Journals Resulting from Grouped Pass-through Journals for Balance Computation

AFCS will support decomposition of journals sourced from Financials Cloud resulting from grouped pass-through journals published via AFCS based on composition proportionality and grouping information.

This enhancement will allow additional flexibility with optimizing data detail and volume flowing to Financials Cloud, for pass-through journal-type sub-ledgers.

Steps to Enable

You don't need to do anything to enable this feature.

Standardized CoA Segments

AFCS will support an extended list of standardized CoA segments with the following key additions:

• Project
• Counterparty
• Intercompany (Legal Entity)
• Channel

This will be applicable across GL balance, ERP journals, and Management Ledger data.

This enhancement will provide additional flexibility in user-choice of Ledger Chart of Account Segments.

Steps to Enable

• Build Ledger dimension
• Map AFCS dimensions to CoA Segments
• Execute ingestion processes as provided by the service

Key Resources

• CoA Segment Mapping

Support for Multi-Ledger Deployments

In addition to Ledger Name assignment, AFCS will support Financials Cloud multi-ledger deployment by capturing, processing, and retaining ledger identification alongside GL balance and journals data ingested from ERP.

This enhancement will facilitate efficient support with multi-ledger Financials Cloud deployments.

Steps to Enable

• Build Ledger dimension
• Map AFCS dimensions to CoA Segments
• Execute ingestion processes as provided by the service

PMF Execution Status API

This public API helps to fetch various execution statuses for a given PMF Process execution for a given process Instance ID.

This enhancement facilitates an interface to get the statuses of a PMF process execution. This is a public Rest API.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Fetching the PMF Execution Status

Rerun, Resume, and Abort PMF Execution API

• Abort Process: Aborts execution for the given process Instance ID.
• Rerun Process: Rerun the entire process with the same process instance ID.
• Resume Process: Resume the process which is in Failed or Cancelled state.

This enhancement facilitates an interface to Rerun, Resume, and Abort a PMF process execution. This is a public Rest API.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Rerun PMF Execution Process
• Resume PMF Execution Process
• Abort PMF Execution Process

DQ Process and Engine Optimization

DQ Process and Engine have been optimized for better performance by parallelizing the Save API and execution of rules respectively.

Reduction in Execution time of the DQ process.

Steps to Enable

You don't need to do anything to enable this feature.

Restriction of User Activities When Catalog Extension is Ongoing

The following user activities will be disallowed when Catalog Extension processes are going on:

• SLA Configuration
• Data Ingestion Connector creation or modification
• Data Extraction
• Process Pipeline Executions
• CoA Segment Mapping

This enhancement will ensure that regular user activities and catalog extension tasks do not disrupt each other.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Catalog Extension

Data Extraction from ERP Financials Cloud When As-of and Calendar Dates Do Not Match

AFCS will now support extraction of files produced by Business Intelligence Cloud Connector process(es) even when As-of and calendar dates do not match.

This enhancement will enable flexibility with date/time of data extraction from Financials Cloud with respect to As-of-date applicable.

NOTE: While managing process sequence/scheduling, please note that BICC extract jobs should be followed by corresponding AFCS ingest processes. Once JOURNAL_INGESTION_EXTRACT_JOB is executed in BICC, 'ERP Journal Ingestion' process should be executed in AFCS before the former is executed again.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Data Extraction

Data Lineage from ERP Financials Accounting Hub Cloud to AFCS

Data lineage from ERP Financials Accounting Hub Cloud to AFCS can be established via ERP Financials Cloud 'Configure & Extend' features and AFCS report templates delivered via the service's Oracle Analytics instance.

This enhancement will support user configuration in Financials Cloud allowing lineage trace to AFCS.

Steps to Enable

• Raise a Support Request on AFCS via My Oracle Support portal to obtain URL pattern for your AFCS Oracle Analytics instance stating 'Data lineage from ERP Financials Accounting Hub Cloud' as the headline.

• Perform Oracle Financials Cloud Configure & Extend - Modify Pages steps as per the user guide on Oracle Help Center.

Extended List of Attributes Corresponding to CoA Segments Available in AFCS Reports

AFCS Oracle Analytics instance will now include the extended list of attributes made available in AFCS 22C in its repository.

This enhancement will support inclusion of additional attributes introduced in release 22C for consumption via AFCS Analytics.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• CoA Segment Mapping

Result Area Entities

New entities have been created to persist Journal, General Ledger Account, Transactions & Contract data. In addition, 12 new dimension entities have also been added.

This enhancement will support the persistence of sourced/processed data for performing analysis.

NOTE: The current persistent/result area entity for the contract has only limited attributes required to support current/immediate requirements and would be extended further in future releases.

Steps to Enable

For any existing extractions defined on Journal, Journal Header, and General Ledger Account data, re-select the grain, entity, and attributes and save. This will enable extraction from the persistence layer.