15.14.2 Processing History Prior to Live Production Use

AFCS facilitates ingestion of movement historical data and computation of balance based on it, without accounting rules or decomposition treatment.

This is in support of moving history data into AFCS. Post balance initiation, the movement history can be brought into AFCS and balance computed off it, without data moving through ERP FAH or being decomposed. The Stage accounting entries journals data is loaded into BCE directly and will bypass ERP and Decomposition. Balance Initialisation is required for balance initialization on the first instance of processing and users are expected to bring balances.

Processing history optionally happens post balance initialisation, subject to the approach being followed for switching AFCS and ERP to production use. Here, AFCS will support journal information at ML segments grain being supplied directly from a non-Oracle ERP source via Staging, which can then be used for balance computation. Such journal information can be withheld from publishing to ERP and all associated processes thereof. Such journals should carry segment values, GL CoA and ML, as they should be rendered, given no segment value lookup function in FAH will apply here.

Prerequisite: All BCE prerequisite steps must be completed before executing the pipeline.

Note:

The Day Zero and Data Conversion Balance Computation pipeline should NOT be executed more than once for any combination of run time parameters.

Note:

All Accounting balance figures processed by this pipeline are as of a given MIS Date and Effective Date. This pipeline should be executed chronologically for contiguous dates through the fiscal year.

Note:

Even when attempted over a closed fiscal period, this pipeline batch does not fail; it does not process anything.

Note:

Even when there are no journals present for a particular day, the Day Zero and Data Conversion Balance Computation pipeline must be executed.

Note:

AFCS requires that accounting balance information be initialised prior to processing transactions or journals data through the service, integrated with Oracle Financials Cloud. The following process pipeline should be used for initialisation purposes: Day Zero and Data Conversion Balance Computation.

Further to this, AFCS supports building of balance information for a subscriber-chosen period of time post initialisation date using appropriate journals data sourced for the purpose. This is an optional step that does not involve data flows between the service and Financials Cloud. The following process pipeline should be used for initialisation purposes: Day Zero and Data Conversion Balance Computation.

Please note that no ledger or portion thereof should be initialised more than once.

If the optional step of building balance information for a period of time post initialisation date without Financials Cloud involvement is being used:

• The balance computation processes involved should be run in chronological order
• Such processes should be run for contiguous dates

Once such activities of initialisation and building of balance information for a period of time are both completed, ‘Regular’ processing of transactions or journals through the service can commence. ‘Regular’ here refers to the flow of data from sources into AFCS and integrated data movements between the service and Financials Cloud.

Once regular processing has started for a given ledger or portion thereof, no activities of initialisation or balance building without Financials Cloud involvement should be performed.

To process history data balances, follow the steps mentioned in the Ingest Initial Balance section.

Note:

There will be no backdated journal balances processed during the execution.