RollOut: Data migration phase - material master

[Former Member]

Dear all,

we are going to implement the SAP in one of our subsidiaries. The phase data migration of the material master is not that clear because I am not very experienced in such a project.

Can anybody consult me concerning my intentions?

I would like to subdivide the prozess data migration in the following separate steps:

1. Analysis of the structure and the material master fields of the legacy system

First I would require an example structure of the legacy system to get a first overview. This structure should be an excel sheet. Then I would discuss this structure with the staff of our subsidiary.

2. Structure of our SAP system

The structure of the SAP and all the necessary fields of the material master will be discussed with the staff of the subsidiary.

3. Comparing of both structures

Compare both structures and define which fields are missing and which fields have to be added

4. Preparation of the migration tool (LSMW)

I would be very grateful to get a reply or critic are recommendations.

Did I forget anything?

Thank you very much

Conan

[Former Member]

Thank you for the reply.

I got the strucutr of the material master records of the legacy system now. I am a bit confused because in the legacy system there have only ten fields to be filled.

They only have:

material number

material description

material description2

category number

unit of measure

tax idendicator

material group

EAN number

package quantity

price

I think that makes the data migration easier, doen't it? Because we just have to think about the mandatory fields in the SAP.

Is that correct are have I anything forgotten?

Greetings conan

[JL23]

I think you basically got what needs to be done.

I usually let the module teams deliver the SAP fields that are necessary for their process.

For the source data I contact the team that deals with the legacy system.

Then we map fields and find the source fields that have to target, as well as mandatory target fields that have no source data.

And I request this usually per material type, as each material type may have different requirements.

Start with the process as early as possible, best with project begin already.

I am currently doing a huge migration project (merging of several SAP systems) , started last December, and I still miss a lot of mappings.

I made the exerience that I get mapping for the well kown entries of a field, however, there are many records that have different values, maybe values that should not be used anymore in the legacy system, but old records never go adjusted, hence I have them as error when loading.