EGL9.2: Year End Close Process(GL_YC) Abends With "Cannot Update ("xxxxx"."PS_JP_JHDR_TAOn"."FISCAL_YEAR") to NULL Error" If Calendar Is Not Defined For Next Year
(Doc ID 2276972.1)
Last updated on OCTOBER 22, 2019
Applies to:PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
When journal post process running, either triggered directly or triggered while running the closing GL_YC process getting below error:
ORA-01407: cannot update ("SYSADM"."PS_JP_JHDR_TAO4"."FISCAL_YEAR") to NULL
Failed SQL stmt: UPDATE PS_JP_JHDR_TAO4 SET FISCAL_YEAR = ( SELECT A.FISCAL_YEAR FROM PS_CAL_DETP_TBL A WHERE A.CALENDAR_ID = '01' AND A.SETID = 'SHARE' AND PS_JP_JHDR_TAO4.ADB_DATE BETWEEN A.BEGIN_DT AND A.END_DT), ACCOUNTING_PERIOD = ( SELECT A.ACCOUNTING_PERIOD FROM PS_CAL_DETP_TBL A WHERE A.CALENDAR_ID = '01' AND A.SETID = 'SHARE' AND PS_JP_JHDR_TAO4.ADB_DATE BETWEEN A.BEGIN_DT AND A.END_DT) WHERE BUSINESS_UNIT = 'SFGOV' AND ADJUSTING_ENTRY <> 'Y' AND PROCESS_INSTANCE = 51726
The issue can be reproduced at will with the following steps:
- trigger the journal post GL_JP process from the batch run control page
- or, trigger the journal post GL_JP process from the online journal lines page
[B] run the GL_YC Closing process which triggers the journal post GL_JP process
1. Set up Closing Rule
2. Set up Closing Group, using above closing rule
3. Run the Close process using above closing group
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document