Relationship to existing contact persons is out of scope in Customer migration object. In order to migrate BP Relationship new Migration Object should be created. In this blog post you will learn how to do it.
Function Module BAPI_BUPR_CONTP_CREATE is using to create a contact person relationship between two business partners. The system checks that the specified business partners exist. The business partner that you enter in the "contact person" parameter must be in the "person" category.
1 Create new Migration Project. In LTMC t-code choose Create, fill Name and Mass Transfer ID.
2 Run LTMOM t-code. Open your migration project and create new user-defined migration object.
Menu Project – Create Migration Object – User-Defined – Migrate Data Using Files/Staging Tables. Go thought wizard steps as follow.
3 Create source structure. Append new structures below to lower level.
S_BUPR Business Partner Relationship fields
Key |
Name |
Data Type |
Length |
Column Header |
X |
BUSINESSPARTNER |
CHAR |
10 |
Business Partner |
X |
CONTACTPERSON |
CHAR |
10 |
Contact Person |
|
FUNCTION |
CHAR |
4 |
Function of partner |
|
DEPARTMENT |
CHAR |
4 |
Department at business partner |
|
COMM_TYPE |
CHAR |
3 |
Communication Method (Key) (Business Add |
4 Set up structure mapping as follow.
Source Structure |
Target Structure |
Access Type |
Mapping Type |
Source Cardinality |
Target Cardinality |
Data Path Type |
S_BUPR |
HEADER |
LOOP AT TABLE |
1:1 Relation |
1 |
1 |
Default Path |
S_BUPR |
R_BUSINESSPARTNER |
Mapping only |
1:1 Relation |
1 |
1 |
Not Applicable |
S_BUPR |
R_CONTACTPERSON |
Mapping only |
1:1 Relation |
1 |
1 |
Not Applicable |
S_BUPR |
R_VALIDFROMDATE |
Mapping only |
1:1 Relation |
1 |
1 |
Not Applicable |
S_BUPR |
R_VALIDUNTILDATE |
Mapping only |
1:1 Relation |
1 |
1 |
Not Applicable |
S_BUPR |
R_CENTRALDATA |
Mapping only |
1:1 Relation |
1 |
1 |
Not Applicable |
S_BUPR |
R_ADDRESSDATA |
Mapping only |
1:1 Relation |
1 |
1 |
Not Applicable |
5 Map Fields according data in table
Import Parameter |
Parameter Value |
Rule |
Target Field |
Target Structure R_BUSINESSPARTNER |
SENDERFIELD |
S_BUPR-BUSINESSPARTNER |
MOVE |
BUSINESSPARTNER |
Target Structure R_CONTACTPERSON |
SENDERFIELD |
S_BUPR-CONTACTPERSON |
MOVE |
CONTACTPERSON |
Target Structure R_CENTRALDATA |
SENDERFIELD |
S_BUPR-FUNCTION |
MOVE |
FUNCTION |
SENDERFIELD |
S_BUPR-DEPARTMENT |
MOVE |
DEPARTMENT |
Target Structure R_ADDRESSDATA |
SENDERFIELD |
S_BUPR-COMM_TYPE |
MOVE |
COMM_TYPE |
Save and generate run time object.
6 Run LTMC t-code, open your project, created migration object and download Template. Populate data as follow.
BUSINESSPARTNER |
CONTACTPERSON |
FUNCTION |
DEPARTMENT |
COMM_TYPE |
Business Partner* |
Contact Person* |
Function of partner |
Department at business partner |
Communication Method (Key) (Business Add |
17100001 |
17910007 |
0005 |
0003 |
TEL |
17100002 |
17910006 |
0001 |
0002 |
TEL |
17100002 |
17910005 |
0003 |
0004 |
TEL |
7 Go through migration steps. As result Contact Persons should be assigned to Business Partners.
Thereby we have created Contact Person assignment Migration Cockpit object.