EAP: BANK STATEMENT IMPORT Primary Resolution for Setup and Issues
(Doc ID 1408674.1)
Last updated on JUNE 12, 2024
Applies to:
PeopleSoft Enterprise FIN Cash Management - Version 8.9 and laterInformation in this document applies to any platform.
Purpose
The purpose of this knowledge document is to act as a repository for the Bank Statement Import issues.
Questions and Answers
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
| Purpose |
| Questions and Answers |
| Setup, Configuration and How To |
| How to configure Bank Node for Import Bank Statement when Import Type = FTP or HTTP |
| How can a Bank Statement File be imported when Application Server and Process Scheduler are on Different Servers |
| PSBD1 Bank Statement File -Record File Layout |
| PSBD2 layout specifications and sample file |
| Bank Statement file formats for PSBD1 / BAI2 in Release 9.1 |
| Errors and Problems |
| Invalid Date error when importing Bank statement file in SWIFT MT940 format |
| Bank Date incorrectly loaded when importing Bank Statement file in MT940 format |
| Error (2,263) with Bank Statement Import when Uploading SWIFT File |
| Invalid PeopleSoft Business Document (9400,302) error when importing bank statement in MT940 format |
| Clicking the File Path Change on the Select File Page of the Bank Statement Import times out. |
| System allows to load duplicate Bank Statements |
| Bank Statement Import process abends at BSP_IMPORT.PROCESS.FILELOOP(PeopleCode) |
| Bank Statement File import in PSBD1 format truncates the values |
| Bank Statement Activity Type is not populated when MT940 Bank Statement file is imported |
| Bank Statement Import process fails at step TR_FA_LOAD.FA_SvcAj.INS_SVCA for EDI822 file format |
| Bank Reference ID field in PS_BANK_STMT_TBL is not populated for SWIFT MT940 file format |
| Bank Statement Import process fails when Multiple Files are loaded with Post Process File Action of Move, Copy or Delete |
| Invalid Number-Processing Halted (9450,1209) when PSBD1 bank statement file is imported |
| 'Bank does not exist' warning message when importing SWIFT MT940 bank statement file |
| BNK_ID_NBR is not populated in BANK_STMT_TBL during TR_BSP_LOAD process |
| Bank Statement Import is not loading SWIFT MT940 file when the bank account has multiple messages |
| Bank Statement Manager page is blank for the Statements loaded |
| Class Record method GetField: parameter 1 is invalid (2,267) error, when importing EDI 824 file |
| Bank Statement Load, TR_BSP_LOAD, might fail at step TR_BSP_LOAD.HEADER.INS_PD on Parallel Processing |
| References |