R12: GLOOAP, OOAP0019, ORA-1403: YTD of Latest Period Is Not Same As Prior Period Although There Is No Period Activity (Doc ID 1327591.1)

Last updated on SEPTEMBER 16, 2016

Applies to:

Oracle General Ledger - Version 12.0.6 to 12.1 [Release 12.0 to 12.1]
Information in this document applies to any platform.
Executable:GLOOAP - Open Period


Symptoms

Discrepancies are seen in the balances for an account in period Dec-11.
The YTD balance for the prior period, Nov-11 is 29298.95
The YTD balance for Dec-11 is 755.26
There is no period activity for Dec-11, so it is expected that the YTD balance for Dec-11 would be the same as Nov-11.
 
Steps to recreate:
------------------
1. Calendar is defined as follows:
 Sep-11 Closed
 Oct-11 Closed
 Nov-11 Closed (this is the latest opened period)
 Dec-11 Future
 No periods defined after this
Number of Future periods is set to 1.

2.  Run Open Period
Open Period is run in this scenario and creates balances row for Dec-11
although the program errors out. The latest_opened_period_name and
closing_status for the period are not updated.
The log file shows:

>> glornp() 05-APR-2011 17:00:47
OOAP0019: There are not enough periods defined in your Calendar. Please
define your future enterable periods.

<x glornp() 05-APR-2011 17:00:48
*****************************************************
sqlcaid: sqlabc: 0 sqlcode: 0 sqlerrml: 0
sqlerrmc:
ORA-01403: no data found

3.  Balances are created for period Dec-11.
Nov-11 is still the latest opened period.
Dec-11 status is still 'F' - Future Enterable.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms