Material data cleansing

[Former Member]

Dear friends,

Can you pls help with your expertise for below mentioned scenarios?

Material data cleansing:

We are planning to create new material code numbering to all of the existing material >= 140,000 with "international standards and our own company customized Numbering."

1.How should we start with new materials (transaction MMNR) and how we should discontinue old materials(tcode-MM06)?

What is effective method to do the same as the number is so huge?

2.What will be impact on the existing thousands of open orders with old materials? And what will be other issues.

3.Do we need to take separate database or instance for cleansing of all material and then finally move from that database/instance?

4.What are the critical parameters in material master that we need to care during cleansing?

It will have much wider impact across transaction Work order, PR, RFQ, Contracts, PO, GR, IR and other sales transaction and other modules.

And thatu2019s why we need to tackle it smoothly.

Rgrds,

Deep Jain

[JL23 · Accepted solution]

We are planning to create new material code numbering to all of the existing material 

are you changing systems, or will you continue with this system? Means you finally have doubled the materials, which creates even a bigger mess for the users to decide for the right one.

if you dont change to a new system, then you have no other chance than doing the cleansing within your system, this has in general nothing to do with a DEV and QA system as it is master data.

if you know how the new materials should be, then you can certainly use LSMW functionality to load the new materials.

And you have to take care about the old materials, so that users do not continue using it for new business cases, however they need to finish old business cases. Here you cn work with material and sales statuses.

But you will probably never get rit of the old materials, for this you need to archive, but to archive a material, you have to archive all business data that used this material first, e.g. POs , sales orders, requisitions, special stock, and many many more, this activities can take years.

forget the 309 movement, it can only happen if the base unit is the same.

Issue the stock and create stock again for new material using the initial inventory movement 561 and 562 ff, which should be release for this project and customized to hit certain GL accounts.

You have to setup a huge project, similar to a full migration to a new system, as any change of material will effect others, you need to create new info records, source lists , BoMs, contracts, conditions, ..........

[Former Member · Accepted solution]

Dear Jürgen /Friends,

Thanks for your reply.

Yes, We will be continuing with same System..Do we no need to use separate instance in that case, just for cleansing activity?

There are thousands of open PO,PR, Work order, are there..This is also a huge job . I understood the issue of master data.

Is the use of deletion flag funtionality(tcode-MM06) in the system will be a big tedious job for it?

Rgrds,

Pradeep Jain

[Former Member · Accepted solution]

Dear Jürgen /Friends,

Thanks for your expert comments.

Rgrds

Pradeep Jain