ECM / EAP: Invalid date. (180,1 12) TR_FORMAT.BankStatement.PSBD1Formatter.OnExecute when running Import Bank Statements
(Doc ID 1469594.1)
Last updated on FEBRUARY 23, 2018
Applies to:
PeopleSoft Enterprise FIN Cash Management - Version 9.1 to 9.1 [Release 9]PeopleSoft Enterprise FIN Payables - Version 9.1 to 9.1 [Release 9]
Information in this document applies to any platform.
Symptoms
When trying to load a Bank Statement file using Import Bank Statements (IMPORT_FILE), the process abends at TR_FORMAT.BankStatement.PSBD1Formatter.OnExecute with an error. The dates are coming across as 0000/00/00
for the value date and transaction date for a bank statement line.
ERROR
File '/fndb/apps/psoft/prod/fscm/iofiles/chinrcno.txt' had the following error: Invalid date. (180,1 12) TR_FORMAT.BankStatement.PSBD1Formatter.OnExecute Name:formatPSBD1Date PCPC:31815 Statement:39 9 Called from:TR_FORMAT.BankStatement.PSBD1Formatter.OnExecute Name:format_str Statement:140 Called from:BS_PSBD1_XFM.MAIN.GBL.default.1900-01-01.Step01.OnExecute Statement:41 (0,0)
STEPS
1. Load a Bank Statement file using Import Bank Statements
2. Process will abend at Invalid date. (180,1 12) TR_FORMAT.BankStatement.PSBD1Formatter.OnExecute
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 |
| References |