My Oracle Support Banner

GLEOYR Module: Open Encumbrance Year Throws 'EOYR0002: Your calendar is not properly defined for the year XXXX' (Doc ID 1338418.1)

Last updated on MARCH 03, 2021

Applies to:

Oracle General Ledger - Version 11.5.10.2 and later
Information in this document applies to any platform.
GLEOYR module: Open Encumbrance Year

Symptoms

NOTE: In the images/examples above or below and/or the attached document, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance).  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

When attempting to run GLEOYR module: Open Encumbrance Year, the request ends in error.

The logfile for the process show the error message:

EOYR0002: Your calendar is not properly defined for the year ...

 

Log File Example:

GLEOYR module: Open Encumbrance Year
........................................................................
>>
>>
>>
<< gleogsd_get_ledger_data() <DATE TIME>

>> gleoctp_check_tot_period() <DATE TIME>


* DEBUG: exp_tot = 13
* DEBUG: fnd_tot = 6

EOYR0002: Your calendar is not properly defined for the year<YEAR>
<x gleoctp_check_tot_period() <DATE TIME>

>> gleoqtp_quit_the_program() <DATE TIME>
SHRD0014: GLEOYR - process exiting with failure.
<x gleoqtp_quit_the_program() <DATE TIME>
........................................................................
Deleting output file.
EOYR0002: Your calendar is not properly defined for the year <YEAR>
>>>>>>>>>>

Changes

Tried to open new encumbrance year. 

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
Changes
Cause
Solution
 Still Have Questions?


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