Show TOC

Transfer Categories Business Partner

BP Data Interface

For transfer of business partner data, use transfer category '15'.

Structure 'BUS_DI' is defined in the DDIC for transferring business partner data.

This structure contains all general data, address data, address usages and bank details that belong to a business partner.

The most important fields are described below:

General

Field AKTYP = activity may assume the following values:

• '01' = Create BP

• '02' = Change BP

• '04' = Modify BP

• ' ' = More data on current BP

For example, if you want to create a partner with two addresses, two data records in the BUS_DI structure have to be generated.
In the first data record, AKTYP = '01' and is also the first address. In the second data record, AKTYP must be SPACE. At this point, the data for the second address is transferred.

AKTYP = '04' means:

• - if a partner does not exist, it will be created,

• - if a partner does exist, it is changed.

You can create up to 9 BP roles (for a business partner) at once, in one data record. To do this, fields RLTYP1 through RLTYP9 must have entries. At the very least, RLTYP1 may not be left blank.

With external number assignment, the PARTNER field must contain the partner number and field BU_GROUP = 'external number assignment' (such as GPEX). With internal number assignment, PARTNER must be left blank, and BU_GROUP = 'internal number assignment' (such as GPIN).

The TYPE field may assume the following 3 values:

• '1' = natural person

• '2' = organization

• '3' = group
  This field must have an entry for creation to take place.

The BPEXT field gives you the option of keeping an external partner number (such as a number from the legacy system) in the SAP system. This would allow you to access an already imported number with the intention of changing it without having to administer the SAP number in the legacy system.

Addresses

Because you can create an unlimited number of addresses for a partner, each address within a partner must be responsive to a key. For this purpose, you have field ADEXT_ADDR (external address number). This field must be unique within a business partner.

In the CHIND_ADDR field, you see the type of change to an address. The following values are permitted:

• 'I' = Insert

• 'U' = Change

• 'D' = Delete

• 'M' = Modify (Insert/Change)

Telephone/Fax Numbers

There may be any number of telephone and fax numbers in an address. The following functions may be used for these numbers:

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

• Change telephone/fax number: CHIND_TEL or CHIND_FAX = 'U'
  The numbers are identified by the following fields: TEL_NUMBER or FAX_NUMBER and TEL_EXTENS or FAX_EXTENS. You may change the note to a number (TEL_REMARK).

• Delete telephone/fax number: CHIND_TEL or CHIND_FAX = 'D'
  Identification takes place as with 'Change'

• Modify telephone/fax number: CHIND_TEL or CHIND_FAX = 'M'
  If the telephone/fax number already exists, it is changed. If it does not exist, it is created.
  If the telephone number changes, you first delete the old number and then create the new number.

Address Usages

You can create address usages for each address. The external address number under which the address was created must be given in the ADEXT_ADVW field. The address type entered in the ADR_KIND field is that to which the address is to be assigned.

There are four possible change types for address usage which are controlled from the CHIND_ADVW field:

• 'I' = Insert

• 'U' = Change

• 'D' = Delete

• 'M' = Modify (Insert/Change)

Bank Details

You can create any number of bank details for a business partner. Each set of bank details in a partner is identified by a unique key in the BKVID field.

There are four possible change types for bank details which are controlled from the CHIND_BANK field:

• 'I' = Insert

• 'U' = Change

• 'D' = Delete

• 'M' = Modify (Insert/Change)

You may keep an external bank details number (within a partner) in the SAP system for each set of bank details. This number is transferred to field BKEXT. You can use either the bank details ID (BKVID) or the external bank details (BKEXT) as an access key if you need to do a later update.

Examples

• two addresses (each with a telephone number)

• one address usage for each address

• one set of bank details

First data record: general data, first address (with
telephone number), first address usage, one set of bank details:

	Field	AKTYP	PARTNER	ADEXT_ADDR	CHIND_ADDR
	Contents	01	BP1	Adrext1		I
	CHIND_TEL	ADEXT_ADVW	CHIND_ADVW	BKVID	CHIND_BANK
	I	Adrext1	I	0001	I

Second data record: second address (with telephone number), second
address usage:

	Field	AKTYP	PARTNER	ADEXT_ADDR	CHIND_ADDR
	Contents			Adrext2		I
	CHIND_TEL	ADEXT_ADVW	CHIND_ADVW	BKVID	CHIND_BANK
	I	Adrext2	I

• one address with two telephone numbers

• two address usages

• one set of bank details

First data record: general data, address (with telephone number),
first address usage, one set of bank details:

	Field	AKTYP	PARTNER	ADEXT_ADDR	CHIND_ADDR
	Contents	01	BP1	Adrext1		I
	CHIND_TEL	ADEXT_ADVW	CHIND_ADVW	BKVID	CHIND_BANK
	I	Adrext1	I	0001	I

Second data record: second telephone number, second address usage:

	Field	AKTYP	PARTNER	ADEXT_ADDR	CHIND_ADDR
	Contents			Adrext1
	CHIND_TEL	ADEXT_ ADVW	CHIND_ ADVW	BKVID	CHIND_BANK
	I	Adrext1	I

Data record: general data, address (with telephone number):

	Field	AKTYP	BPEXT	ADEXT_ADDR	CHIND_ADDR
	Contents	02	BPEXT1	Adrext11	I
	CHIND_TEL	ADEXT_ADVW	CHIND_ADVW	BKVID	CHIND_BANK
	I

Note:

If the partner has been created with an external partner number (BPEXT), you can access the data record to make changes, as shown in the third example. If an external partner number was not assigned when the partner was created, you have to access the data record by using the (internal) partner number.