EAP: Getting Invalid decimal value Error when Importing MT940 Bank Statement File
(Doc ID 2012273.1)
Last updated on MARCH 01, 2023
Applies to:
PeopleSoft Enterprise FIN Cash Management - Version 9.1 to 9.1 [Release 9]Information in this document applies to any platform.
Symptoms
When importing MT940 file which contains Statement Sequence 62 in the :28C: line, the IMPORT_FILES process abends with the following error:
Invalid decimal value -- %1. (180,106)
Process 0 ABENDED at Step BS_SWIFT_XFM.MAIN.Step01 (PeopleCode) -- RC = 4
XML parser error CreateXmlDoc (159,5)
TR_FORMAT.Common.TransformDoc.OnExecute Name:GetContentsAsMe ssage
PCPC:3279 Statement:71 Called
from:TR_FORMAT.Utilities.BankStmtUtils.OnExecute Name:LoadFile
Statement:202 Called
from:BSP_IMPORT.PROCESS.GBL.default.1900-01-01.FILELOOP.OnExecute
Statement:61
This is due to Statement Date processing for :62 lines.
SWIFTFormatter splits text on all occurrences of :62 including :28C:62 where 62 is the Sequence.
STEPS
1. Navigate to Banking > Bank Statements > Import Bank Statements.
2. Upload MT940 file.
Changes
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 |
| References |