SAP Knowledge Base Article - Preview

3591040 - GB AUDDIS (BACS) payment format has an incorrect sequence number

Symptom

A BACS payment run was executed in the system. The first run is  successful, but the second and third encountered an error when uploading to the bank.  The issue stems from the reference code in line 1 of the BACS payment TXT file, which must be unique to prevent upload failures. 
The bank's BACS guidance states that this reference must remain unique for three months. To avoid manual adjustments, a system configuration is needed to generate a different reference for each payment, such as incorporating the date into the reference format (e.g., VOL1ddmmyy). 


Read more...

Environment

  • SAP R/3
  • SAP ERP
  • SAP S/4HANA
  • SAP R/3 Enterprise
  • SAP ERP Central Component
  • SAP enhancement package for SAP ERP
  • SAP enhancement package for SAP ERP, version for SAP HANA 

Product

SAP ERP Central Component all versions ; SAP ERP all versions ; SAP R/3 Enterprise all versions ; SAP R/3 all versions ; SAP S/4HANA all versions ; SAP enhancement package for SAP ERP all versions ; SAP enhancement package for SAP ERP, version for SAP HANA all versions

Keywords

GB_BACS, AUDDIS, XML, F110, RFFOBC_T, sequence number, payment file, BACS , KBA , FI-AP-AP-B1 , Payment transfer (w/o DE, US) , FI-LOC-CA-GB , Great Britain , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.