GLOOAP: Periods - Open Periods Throws Error with OOAP0014: Unable to find the closing status of the target period
(Doc ID 2104707.1)
Last updated on APRIL 04, 2025
Applies to:
Oracle General Ledger - Version 12.1 and laterInformation in this document applies to any platform.
Symptoms
The concurrent program "Periods - Open Periods" throws the following error when changed the period name before opening the first period.
- OOAP0014: Unable to find the closing status of the target period: XXXXXXXXX
Steps to Reproduce
1. Create a new calendar
(N)Setup > Financials > Calendars > Accounting
Year Quarter Num From To Name Adjusting
---- ------- --- ----------- ----------- -------- ---------
2015 1 1 01-APR-2015 30-APR-2015 APR-2015
2015 1 2 01-MAY-2015 31-MAY-2015 MAY-2015
2015 1 3 01-JUN-2015 30-JUN-2015 JUN-2015
2015 2 4 01-JUL-2015 31-JUL-2015 JUL-2015
2015 2 5 01-AUG-2015 31-AUG-2015 AUG-2015
2015 2 6 01-SEP-2015 30-SEP-2015 SEP-2015
2015 3 7 01-OCT-2015 31-OCT-2015 OCT-2015
2015 3 8 01-NOV-2015 30-NOV-2015 NOV-2015
2015 3 9 01-DEC-2015 31-DEC-2015 DEC-2015
2015 4 10 01-JAN-2016 31-JAN-2016 JAN-2016
2015 4 11 01-FEB-2016 29-FEB-2016 FEB-2016
2015 4 12 01-MAR-2016 31-MAR-2016 MAR-2016
2015 4 13 31-MAR-2016 31-MAR-2016 ADJ-2016 Yes
---> The Name format is "MON-YYYY"
2. Create a new ledger
(N)Setup > Financials > Accounting Setup Manager > Accounting Setups
======================================
First Ever Opened Period : APR-2015
======================================
Check the table data:
(Ex)
LEDGER_ID NAME FIRST_LEDGER_PERIOD_NAME
--------- ---------- ------------------------
2206 XXX_GLBOOK APR-2015
----> FIRST_LEDGER_PERIOD_NAME is still APR-2015
4. Open First Period
(N)Setup > Open/Close
=========================
First Period : APR-2015 <---It shows the old format.
=========================
Concurrent log:
GLOOAP module: Periods - Open Periods
+---------------------------------------------------------------------------+
Current system time is 05-FEB-2016 05:53:43
+---------------------------------------------------------------------------+
>> main() 05-FEB-2016 05:53:43
>> glusca() 05-FEB-2016 05:53:43
<< glusca() 05-FEB-2016 05:53:43
>> glulsr() 05-FEB-2016 05:53:43
<< glulsr() 05-FEB-2016 05:53:43
>> glooap() 05-FEB-2016 05:53:43
>> gloovp() 05-FEB-2016 05:53:43
OOAP0014: Unable to find the closing status of the target period: APR-2015
<x gloovp() 05-FEB-2016 05:53:43
<x glooap() 05-FEB-2016 05:53:43
Cause
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
| Symptoms |
| Cause |
| Solution |