3715537 - Duplicate bank statements allowed when imported using BankStatementPost_IN API in SAP S/4HANA Cloud Public Edition

• Duplicate bank statements are being allowed to upload when imported using the BankStatementPost_IN API in the SAP S/4HANA Cloud Public Edition production system.
• The issue does not occur when uploading from the front end, as the validation works correctly and triggers an error message if the same bank statement number is uploaded, even in a different format.

SAP S/4HANA Cloud Public Edition

1. Import duplicate bank statements using the BankStatementPost_IN API
2. Observe that duplicate bank statements are allowed to upload without triggering an error message.

• The system treats entries with different page numbers (e.g., "BS 1, page 1" and "BS 1, page 0") as distinct, preventing duplicate detection.
• The page number is critical for duplicate checks, especially when the format uses pages (e.g., MT940) or when statements exceed the maximum item limit per page.
• In such cases, multiple entries for the same bank statement may appear in the system, such as "BS 1, page 1" and "BS 1, page 2."  
• For example, BS 1 page 1 is treated as distinct from BS 1 page 0. Thus no error will be raised during the duplicate check process, as the system did not identify them as duplicates. 

1. If the page feature is not utilized (i.e., bank statements do not exceed the maximum item limit), leave the page number field empty during the import process.
2. Ensure that the page number field is not populated to prevent the system from treating entries with different page numbers as distinct.

duplicate bank statements, BankStatementPost_IN API, SAP S/4HANA Cloud Public Edition, page number field, validation error, duplicate detection, production system, Q system, MT940 format, CAMT format, bank statement upload , KBA , FI-BL-PT-BA-2CL , bank statement (Public Cloud) , Problem