2023-02-07 1854280

1854280 - BAPI: IBAN and SWIFT_CODE

Version 8 Type SAP Note
Language Anglais Master Language Allemand
Priority Correction with high priority Category Advance development
Release Status Pilot Release Released On 25.02.2022
Component MM-IV-LIV-BAPI ( BAPI )

Please find the original document at https://launchpad.support.sap.com/#/notes/ 1854280

Symptom

You want to use the BAPI BAPI_INCOMINGINVOICE_CREATE to make postings to one-

time accounts or different payees. When you do this, you want to transfer the
bank details as a combination of SWIFT code and IBAN (which is the standard
behavior in case of SEPA payments, for example).

Other Terms

BAPI_INCOMINGINVOICE_PARK, SPC_SCM1, BAPI, Business Application Programming

Interface, SEPA, single euro payments area, IBAN, International Bank Account
Number

Reason and Prerequisites

At the FI document level, the bank details are not mapped using SWIFT code and
IBAN.
The document segment for one-time accounts (table BSEC) does not contain any
fields for SWIFT code and IBAN. Instead, the bank details as always consist of
the bank country (BANKS), the bank key (BANKL) and the bank account number
(BANKN).
Therefore, the fields SWIFT_CODE and IBAN only serve as a reference for
populating these fields.
The SWIFT code is assigned using the bank master (table BNKA). The IBAN is
mapped in form of a technical bank account number (starting with <IBAN>) using
the table TIBAN.
A suitable bank master record for the SWIFT code must already exist for a
posting to be made. A TIBAN record is created automatically during the posting
(if required).

Solution

After you implement the attached correction instructions and add the fields IBAN
and SWIFT_CODE to the structure BAPI_INCINV_CREATE_ADDRESSDATA (see "Manual
Activity" section of this SAP Note), you can create postings with SWIFT code and
IBAN.
Note the following when filling the BAPI parameter ADDRESSDATA:
If the field SWIFT_CODE is filled, the otherwise optional field
IBAN becomes a required entry field. In addition, the fields BANK_ACCT, BANK_NO,
and BANK_CTRY must not be filled in this case. These fields are derived
internally from SWIFT_CODE and IBAN.
If the system fails to uniquely derive the traditional bank details (BANKS,
BANKL, and BANKN) from the combination of SWIFT_CODE and IBAN, the system
rejects the posting and issues error message BF00 018 ("Bank key not found").
In this case, check the bank master data (the SWIFT code is then unknown or
ambiguous).

© 2023 SAP SE or an SAP affiliate company. All rights reserved 1 of 4

2023-02-07 1854280

Restriction:

For technical reasons, the two new fields IBAN and SWIFT_CODE are also displayed
in the BAPI BAPI_INCOMINGINVOICE_SAVE. Currently, entering an IBAN and a SWIFT
code is not supported for this BAPI. Leave these fields empty. Otherwise, the
system issues error message M8 737 ("Delete field ... (import parameter
ADDRESSDATA)").
Instead, fill the classical bank fields in this BAPI.

As of release SAPK-S4CLOUD_1802 and for releases higher than 618 or higher than S/4HANA
OP1709, this SAP Note is part of the standard and must no longer be implemented.

Manual Activities

------------------------------------------------------------------------
|Manual Activity |
------------------------------------------------------------------------
|VALID FOR |
|Software Component S4CORE |
| Release 100 All Support Package Levels |
| Release 101 All Support Package Levels |
| Release 102 All Support Package Levels |
------------------------------------------------------------------------

Caution: You have to perform this manual activity separately in each system into which you
transport the Note for implementation.

• Use transaction SE11 to add the following fields to the BAPI structure
BAPI_INCINV_CREATE_ADDRESSDATA:

IBAN with the component type IBAN

SWIFT_CODE with the component type SWIFT

Add these fields at the end of the structure and choose "Activate".

• Use transaction SE91 to add the new message 357 in the message class M8_2 with the
following message short text:

"Field & must remain blank when field & is filled".

Save the change.

------------------------------------------------------------------------
|Manual Activity |
------------------------------------------------------------------------
|VALID FOR |
|Software Component SAP_APPL SAP Application |
| Release 600 All Support Package Levels |
| Release 602 All Support Package Levels |
| Release 603 All Support Package Levels |
| Release 604 All Support Package Levels |
| Release 605 All Support Package Levels |
| Release 606 All Support Package Levels |
| Release 616 All Support Package Levels |
| Release 617 All Support Package Levels |

© 2023 SAP SE or an SAP affiliate company. All rights reserved 2 of 4

2023-02-07 1854280
| Release 618 All Support Package Levels |
------------------------------------------------------------------------

Caution: You have to perform this manual activity separately in each system into which you
transport the Note for implementation.

• Use transaction SE11 to add the following fields to the BAPI structure
BAPI_INCINV_CREATE_ADDRESSDATA:

IBAN with the component type IBAN

SWIFT_CODE with the component type SWIFT

Add these fields at the end of the structure and choose "Activate".

• Use transaction SE91 to add the new message 357 in the message class M8_2 with the
following message short text:

"Field & must remain blank when field & is filled".

Save the change.

Software Components

Software Component Release

SAP_APPL 600 - 600

SAP_APPL 602 - 602

SAP_APPL 603 - 603

SAP_APPL 604 - 604

SAP_APPL 605 - 605

SAP_APPL 606 - 606

SAP_APPL 616 - 616

SAP_APPL 617 - 617

SAP_APPL 618 - 618

S4CORE 100 - 100

S4CORE 101 - 101

S4CORE 102 - 102

Correction Instructions

© 2023 SAP SE or an SAP affiliate company. All rights reserved 3 of 4

2023-02-07 1854280
Software Component From To Version Changed on ID

SAP_APPL 606 618 4 25.02.2022 16:20:21 0001249391

SAP_APPL 604 605 4 25.02.2022 16:39:59 0001267910

SAP_APPL 603 603 3 25.02.2022 16:43:22 0001267911

SAP_APPL 600 602 4 25.02.2022 16:47:12 0001268010

S4CORE 100 102 3 25.02.2022 16:51:39 0000585183

Prerequisites

Software SAP
From To Title Component
Component Note/KBA

BAPI: Error message with one-time vendor and MM-IV-LIV-

S4CORE 100 105 3014777
empty exchange rate BAPI

BAPI_INCOMINGINV MM-IV-LIV-
SAP_APPL 600 600 1597782
OICE_PARK: FF707 prevents parking BAPI

BAPI: Error message with one-time vendor and MM-IV-LIV-

SAP_APPL 600 618 3014777
empty exchange rate BAPI

BAPI_INCOMINGINV MM-IV-LIV-
SAP_APPL 602 602 1597782
OICE_PARK: FF707 prevents parking BAPI

BAPI_INCOMINGINV MM-IV-LIV-
SAP_APPL 603 603 1597782
OICE_PARK: FF707 prevents parking BAPI

BAPI_INCOMINGINV MM-IV-LIV-
SAP_APPL 604 604 1597782
OICE_PARK: FF707 prevents parking BAPI

This document refers to

SAP Note/KBA Title

1622412

1600775 BAPI: Tax reporting date (VATDATE)

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2023 SAP SE or an SAP affiliate company. All rights reserved 4 of 4