Show TOC

 Business Partner Interface (Transfer Category 15)


Use transfer category ‘15’ for transferring business partner data.

The ‘BUS_DI’ structure is defined for business partner data transfer. This structure contains all general data, address data, address usages and bank data for a business partner.

The following section contains information about how the business partner functions can be applied in Contract Accounts Receivable and Payable (FI-CA), and what you must take note of with data transfer.



Every business partner addressed in Contract Accounts Receivable and Payable must exist in the Contract Partner (MCI) role.This role is hard coded.

The business partner in the Contract Partner role consists of the following data:

  • Personal data

  • Address data

  • Bank details

  • Payment cards

  • ID numbers

  • Tax numbers


The AKTYP field = activity can have the following values:

  • ’01’ = Create BP

  • ’02’ = Change BP

  • ‘04’ = Modify BP

  • ‘‘ = More data about the current BP

If you want to create a partner with two addresses, for example, transfer two data records for the BUS_DI structure.

In the first data record, enter AKTYP = ’01’, as well as the first address. In the second data record, enter AKTYP = SPACE and the data for the second address.

AKTYP = ’04’ means:

  • The partner is created if it is not yet available

  • The partner is changed if it is available

For external number assignment, you have to fill the PARTNER field with the partner number, and set BU_GROUP = ‘external number assignment’ (e.g. GPEX). For internal number assignment, the PARTNER field remains empty, and you use BU_GROUP = ‘internal number assignment’ (e.g. GPIN).


The usage of addresses in the business partner is based on central address management.

As n addresses can be created for a partner, every address for a partner must be addressable with a key. The ADEXT_ADDR field (external address number) must be unique for a partner.

The type of change for an address is in the CHIND_ADDR field. The following values are permitted:

  • ‘I’ = Add

  • ‘U’ = Change

  • ‘D’ = Delete

  • ‘M’ = Modify (add/change)

Address usages can be created for every address. The ADEXT_ADVW field must contain the external address number, under which the address was created. The ADR_KIND field contains the address type, to which the address is to be assigned.

There are four possible change types for the address usage, which are controlled in the CHIND_ADVW field.

  • ‘I’ = Add

  • ‘U’ = Change

  • ‘D’ = Delete

  • ‘M’ = Modify (add/change)

When transferring data to the interface you must take into account that you have allocated external address numbers where appropriate, that must be assigned to internal address numbers.

Internal address numbers are numbers that the SAP system assigns to addresses transferred from the operational system. The system uses these numbers within Contract Accounts Receivable & Payable (FI-CA).

In SAP terms, external address numbers are numbers that you allocate in your own operational system (probably because you want to differentiate between addresses belonging to a business partner) and are different to the SAP conventions for number assignment. These external address numbers are then converted at the interface. The external address numbers can also be used in other interfaces – for example, account.

You also enter information in the interface about which addresses the SAP system should use for certain functions, by specifying a certain (external) address number. Otherwise the SAP system works the standard address - if you do not use external address numbers to differentiate between multiple addresses for a partner. The standard address is the address to which the address usage XXDEFAULT is assigned.

Upgrade customers

The option of flagging the standard address with the field BUS020_DI-XDFADR no longer exists (change due to time-dependency for the SAP business partner).

Telephone and Fax Numbers

There can be n telephone and fax numbers within an address. The following functions are possible:

  • Create telephone/fax number: CHIND_TEL or CHIND_FAX = ‘I’

  • Change telephone/fax number: CHIND_TEL or CHIND_FAX = ‘U’

    The number is identified with the fields TEL_NUMBER or FAX_NUMBER and TEL_EXTENS or FAX_EXTENS. The comment (TEL_REMARK) for a number can be changed.

  • Delete telephone/fax number: CHIND_TEL or CHIND_FAX = ‘D’

    Identification takes place as for Change.

  • Modify telephone/fax number: CHIND_TEL or CHIND_FAX = ‘M’

    If the telephone/fax number already exists, it is changed. Otherwise it is created.

    If the telephone number changes, the old number must be deleted as a first step, and the new number is then created in the second step.

Bank Details

You can create n sets of bank details for a partner. Every set of bank details within a partner is identified by a unique key in the BKVID field.

There are four possible change types for the bank details, which are controlled in the CHIND_BANK field.

  • ‘I’ = Add

  • ‘U’ = Change

  • ‘D’ = Delete

  • ‘M’ = Modify (add/change)

An external bank details number (within a partner) can be stored in the SAP system for every set of bank details. This number is entered in the BKEXT field. You can choose whether to use the bank details ID (BKVID) or the external bank details ID (BKEXT) can be used as an access key, for any later bank data update. Bank details (BKEXT) are used as access key.