3375859 - DBSQL_SQL_ERROR during upload of bank statement CAMT053 - S/4HANA Cloud

Bank statement type CAMT053 cannot be uploaded via App "Manage Incoming Payment Files".

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

SAP S/4HANA Cloud

1. Enter App "Manage Incoming Payment Files".
2. Upload bank statements are canceled.
3. In the Log check the error: "Internal session terminated with runtime error DBSQL_SQL_ERROR(see ST22)".

Several bank statement items contain the same Entry Reference (<Refs>) or Account Servicer Reference (<AcctSvcrRef>). Whereas Entry Reference is supposed to uniquely identify an item within a bank statement, Account Servicer Reference is supposed  to uniquely identify an item reported in several files for the same bank account.

The system tries to identify if there was already a bank statement item with identical Account Servicer Reference to avoid double postings.

According to the CGI guideline, the field has to be unique or empty per transaction.

1. Contact your bank that they send you the file either with unique or empty Account Servicer References.
2. Afterwards reverse the imported statements and import the corrected ones again.

(If Intraday Posting has been activated for your bank account, after the upload the bank statement state is "Secondary Item - Not to be processed". This check was implemented with release 2308 to support Intraday Bank Statement Posting).

Intraday Bank Statement Posting

bank statement, upload, rejected, canceled, DBSQL_ERROR, runtime error, Manage Incoming Payments Files, Account Servicer Reference, CAMT053, F1680 , KBA , FI-BL-PT-BA-2CL , bank statement (Public Cloud) , Problem