AFCS Is Unable To Process Future Dated Journals (Doc ID 2945188.1)

Last updated on MAY 03, 2023

Applies to:

Symptoms

AFCS 22D, AFCS is unable to process future dated journals

When we post future dated journals to AH, the ERP journals are ingested back with as of date as accounting date as per the below formula given in the user guide:

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).

Tried the following scenario:

Step 1:
Loaded the data into AFCS stage table with As of date = 7th Aug and accounting date = 8th aug and 7th AUg.
Posted this data to AH and generated the extracts .
ERP Journals ingestion connector loaded two sets of data

Set 1. Records with accounting date = 7th AUg were loaded with as of date 7th Aug.
Set 2. Records with accounting date = 8th AUg were loaded with as of date 8th AUg

The decomposition picked up only those records with as of date= 7th Aug.

Step 2:
Loaded the data into AFCS stage table with As of date = 8th Aug and accounting date = 8th aug
Posted this data to AH and generated the extracts .
ERP Journals ingestion connector failed because data with as of date = 8th Aug was already loaded in step 1 the previous day.

Changes

 NA

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.