Vendor Data Migration Approach & Strategy

Vendor Data Migration Approach:

A. Migration methodology.

Vendor master forms an important component of Logistics Supply Chain. The Successful migration of
Vendor Master is a Key towards Successful Migration of other Data Objects viz. Purchase Info records,
Source List, Equipment Master, BOM’s etc.

In view of above, the foremost important Step is to Identify and listing down the Rules for Identification
of eligible Vendors for Migration.

Once the Rules are identified the Next step is to extract the Vendors from the Source system with all
necessary details that are relevant for Migration in the Target system.

In Order to simplify the Upload Process in Target System, effort should be put in to have the Extracted
Data template in sync with Upload data template. This Synchronization activity will help in reduced
Manual Effort in making the Upload Template thus improving Data Accuracy and faster Upload Time.

B. Extraction Criteria

Step # Description
Select all purchase orders from V_EKKO_EKPO where EKPO-MATNR is in Golden
1 List of Ganymede Materials

Select all vendors (EKKO-LIFNR) from the POs from step 1 where EKKO-AEDAT >
2 01.01.2015

Add Vendor numbers which have been found as partner function additionally (ab
3 Additional Vendors by WYT3

Org levels have been taken from the TOM document:

BUKRS: 1230,1372,1318,1353,1276,0673,0134,0963
4
EKORG:BY49,NC09,BYUS,NA09,BYCA,BYBR,LA09,BYMY,BYTW,BYJP,JP09,BYKR,KR09

LFA1, LFB1, LFB5, LFBK, LFBW, LFM1, LFM2, WYT3, BNKA, ADRC, ADR2, ADR3,
5 ADR6, ADRT are taken from the master data server (MANDT 140). Bank
connection data must not be loaded for testing

6 Vendors assigned to Equipment’s: Table EQUI (Equipment) with Field ELIEF

7 Vendors assigned to Bill Of Materials: Table STPO (Bill Of Material Items) with Field
LIFNR.
 Vendor Data Migration Approach & Strategy

Vendor Data Migration Strategy:

Data that make up a Vendor Master is stored in Many SAP Tables. In Order to simplify the Process of
vendor Upload in NEWCO System, it is recommended to upload the Data in the Format of the Extracted
Data.

For Project, since Vendor data is provided as Table Dump, the recommended Upload Methodology
should be Table Upload.

Accordingly, below Upload Templates for each of the relevant Vendor Data Table has been created. It is
expected that Data is provided in the Upload Format Template Table wise by setting up appropriate SAP
Table Variants.

Tables in Vendor table Upload

Vendor Section Vendor Table Description
use Format

LFA1 Vendor Master (General Section)

ADRC Addresses (Business Address Services)

Vendor Telephone Numbers (Business Address

ADR2
Services)
General Data
Vendor Fax No. Numbers (Business Address
ADR3
Services)

Vendor E-Mail Addresses (Business Address

ADR6
Services)

Vendor master (VAT registration numbers

LFAS
General section)

Company Code
LFB1 Vendor Master (Company Code)
Data
 Vendor Data Migration Approach & Strategy

LFB5 Vendor master (Dunning data)

LFBK Vendor Master (Bank Details)

Vendor master record (withholding tax types)

LFBW
X

LFM1 Vendor master record: Purchasing Org. specific

Vendor Master Record: Purchasing Data Plant

Purchasing Data LFM2
specific

WYT3 Vendor Partner Functions

Apart from the .txt template, Please find below the Excel template for preparing Upload templates.

Vendor Upload
Template.xlsx

Special Considerations for preparing Upload Template:

1. For Preparation of Upload Template for Vendor Partner Function, once the Data is extracted in
the Upload template, we would require a Manual task.
Remove all Entries with partner Function except OA, VN and PI. Mark the remaining entries
XDELE Indicator to ‘X’ for all Records except Entries with Partner Function VN

Copy the entries other than entries with VN, and Paste them in the File with value of PARZA as
002.
Once done, Sort the Records with Descending Value of PARZA.
Your File is then ready for Upload.

2. For Vendors in LFA1 table with Country as ‘BR’, please consider below:
Nowadays, Bayer has Street Name and House Number on the same field. This is an issue while
creating nota fiscal.
 Vendor Data Migration Approach & Strategy

LFA1-STREET field should have only street name. Number should be on the appropriate field:
HOUSE-NUM1.
Example:
Vendor QBC = 7712483
Street Name: R 2 DE SETEMBRO 399
Should be:
Street Name: R 2 DE SETEMBRO
House Num1: 399

3. For Vendors in ADRC table with LFA1-Country as ‘BR’, please consider below:
Nowadays, Bayer has Street Name and House Number on the same field. This is an issue while
issuing nota fiscal.
LFA1-STREET field should have only street name.
Number should be on the appropriate field: HOUSE-NUM1.

4. For Vendors in LFM1 table with with LFA1-Country as ‘BR’, please consider below:
LFM1-WEBRE= “X”