EEX 9.2: Getting An 'Invalid Date. (180,112)' Error When Adding An Expense Location Amount With Date 02/29 (29 February) (Doc ID 2115644.1)

Last updated on MARCH 14, 2016

Applies to:

PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

Getting error 'Invalid date. (180,112)' when adding an Expense Location Amount with End Of Season 02/29 (29 February) and effective date is not in leap year

Steps:
The issue can be reproduced at will with the following steps:
1. Log in as a User.
2. Go to Setup Financials/Supply Chain>Product Related>Expenses>Location>Expense Location Amount
3. Open any existing record or create a new one - make sure the effective date is not in leap year.
4. Now add a new row or modify one with End of Season of 02/29 (29 February)
5. Save the page.

Error:
Invalid date.(180,112)EX_LOC_AMT_DTL.SETID.SavePreChange PCPC:2183 Statement:51

An invalid date has been encountered in a PeopleCode program.

Review the PeopleCode program to determine the cause of the error.

Application Server logs show the same error.

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