PURCHASING INFORECORDS MIGRATION

1|Page
Document Management
Project ID: One ERP
Status: Initial

Team: Data Migration

Author: Ana Moldovan

Data Created: 31.01.2020

Revision History
Version Date Description Created by
1.0 31.01.2020 Initial Ana Moldovan

2|Page
 I. General

1. Purpose
This document pertains to transferring Purchasing Inforecords from legacy system, ITP, to its
intended target SAP S/4 HANA systems. In this document the focus is on defining the
migration object definition in the Migration Tools, extraction criteria, and the mapping rules
applicable for the data-object. It will be input for the extraction-resources, the data-cleansers
and the transformation-resources to perform their activities.

2. General Information
Source System

The Source is SAP R/3, ITP, productive system.

Target System

There will be more clients and systems involved in the migration process.

Test systems

Development System – DEV100/200

Quality Systems – QAS100, QAS200, QAS300, QAS400

Productive System

PRD, client 100.

3|Page
II. Data Extraction
As a part of data preparation, data cleansing activities will be performed on the legacy
system before extraction. Tables will be manually extracted from the legacy system - ITP and
saved on One ERP Project Folder, on the Hoffmann Neopac server.

1. Selection of data
The selection of Purchasing Inforecords is the responsability of the Data Owners. It is their
decision which Purchasing Inforecords will be transferred from source ITP system to new S/4
Hana target system.

Table selection

The following tables need to extracted from the source system ITP for the Purchasing
Records Migration.

Table Table Details

EINA Purchasing Info Records General Data
EINE Purchasing Info Records Purchasing Organization Data
A018 Material Info Record
A017 Material Info Record (Plant-Specific)
KONP Conditions Item
KONM Conditions (1-Dimensional Quantity Scale)

In order to ease the extraction, tables A017/018, KONP and KONM will be extracted in one
single report, with the help of program ZMIG_EXTRACT_PURC_INFO_RECORDS.

Data Selection Criteria

At the same it must be checked that the Purchasing Inforecords in the respective tables
follow the below selection criteria:

1. Field DATLB–EINE Document Date

4|Page
Only Purchasing Info Records which were used in Purchasing Info Records after the date
01.01.2018 must be selected.

2. The Field LOEKZ-EINE– Deletion Indicator

Purchasing Info Records with deletion indicator must not be migrated.

3. Field NETPR-EINE Net Price

Only Purchasing Info Records with conditions will be transferred to the target System S/4
Hana. That means that the Net Price must be higher than 0.

The Purchasing Info Records with Net Price 0 are automatically created by the system,
because of the Info Update Indicator in the Purchasing Documents.They are not relevant for
migration.

4. Field WERKS-EINE Plant

Only the Purchasing Info records for plants HT01, NP01 and TD01 will be migrated.

5. Field INFNR – Purchasing Info Record Number

After the extraction of PIR from table EINE, considering the above mentioned filters, the
Purchasing Info Record Number – INFNR can be used as a selection criteria in table EINA
and in the report created by the program ZMIG_EXTRACT_PURC_INFO_RECORDS.

There is a limitation in the report created by the program

ZMIG_EXTRACT_PURC_INFO_RECORDS, i.e. only 2000 records can be extracted in one
step.

6. Field MATNR-EINA Material

Only the Purchasing Info Records for materials without deletion indicator ( and which are
already transferred to the target system) are relevant for migration.

7. Field LIFNR-EINA Vendor

Only the Purchasing Info Records for vendors without deletion indicator ( and which are
already transferred to the target system) are relevant for migration.

1. The Field LOEKZ-EINA– Deletion Indicator

5|Page
Purchasing Info Records with deletion indicator must not be migrated.

2. Purchasing Info Records Longtexts extraction

Because texts are encrypted, the Long texts extraction from legacy system, ITP, will be done
with the help of program ZMIG_READ_LONGTEXTS.

The following selection criteria will be used to download long texts:

Text Type Text Object Text ID Language

Info record note

EINA AT EN,
HU,DE
Purchase order
texts EINE BT

III. Data transformation

1. Data Transfer Rules
In the process of data transformation, the requirements at field level have been defined in the
Purchasing Info Records – Field Requirement Definition. In this file it is defined how the
data in the extracted files will be transferred to the target system.

 One to one transfer ( !) – the data will be taken over exactly as in the extracts from
the legacy system;
 Data Conversion (%) – data will be modified in order to adapt to the new values in
the S/4 Hana PRD system, different than those in the source system. The
equivalence between old values and the new values can be found in mapping tables;

6|Page
 - Defaults (1) – in this case the same value will be taken for all the material within that
material type, irrespective of what the value in the source system was, even if it was
an empty field.

- Automatically Determined by system (3)

IV. Migration Tools & Migration Objects

Migration tools used to migrate Purchasing Info Records are Migration Cockpit (Data
Migration from File) and the older application for Data Upload, Legacy System Migration
Workbench- LSMW.

There will be more migration objects, with different templates, which will be used to create
the Purchasing Info Records.

1. Purchasing Info Records ( General and Purchasing Data)

In order to migrate the main part of the Purchasing Info Records the Migration Cockpit will
be used.

It is a pre-defined object created by SAP: Purchasing Info record with conditions.

Project Name: Purchasing Info Records

Mass transfer ID: PIR

2. Conditions for Purchasing Info Records

In order to migrate conditions for purchasing info records the LSMW will be used.

Migration object type in LSMW: Standard Batch Input.

Project Name: HN Migration/Material

7|Page
Migration Object: Conditions – Purchasing Inforecords Conditions

Customized.

Note: this additional migration object was used, because in the initial migration testing cycles
there was a problem to migrate these with Migration Cockpit.

3. Purchasing Info Records long texts

In order to migrate long texts for Purchasing Info Records the LSMW will be used.

Migration object type in LSMW: Standard Batch Input.

Project Name: HN Migration/General Migration

Migration Object: Material Long texts(CREATE_LONG_TXT)

Customized.

V. Data validation
After loading the data in SAP, the data owners will first do a check on the correctness of the
loaded date. If this check is positive, the data team will check a set of data (e.g. top 20
Purchasing Info Records). If all data is loaded correctly, the Data Owner needs to sign
off/confirm that the data has been loaded correctly.

8|Page