Varian Master Data Maintenance after transactions

[Former Member]

Dear Experts,

How to handle master data change in VC after transaction on live system?

We are working on material variant concept so VC is only at sales, we use KMAT in sales order to replace with FERT (Material Variant)

master data change possibilities could be

1. Addition of new characteristics

2. Deletion of Char Value

3. Addition of new char in Class

4. Deletion of char from class

5. Configuration profile change

6. KMAT change in material variant

Please suggest the standard way to mange these activities, as a single change can affect multiple material variants against KMAT.

Regards,

ATP

[Ritz · Accepted solution]

ATP _SAP,

what's your system architecture?

are you making changes directly in production or changing in quality and moving to production?

My suggestion is, please try to check what processes and steps your consulting partner provided your business at the time of implementation.

Another point, as per my knowledge , its not possible to change KMAT assignment to Material variant.

So please explain what are you expectation over here?

For other changes you can simple use report " RCUUPDMATVAR" relevant to material variant it will update changes. Use SE38 to execute this report. or use transaction "CUUPDMV"

Hope it will help you.

Thanks

Ritesh

[Former Member · Accepted solution]

Ritesh,

Thank you for the inputs.

Our architecture  DEV> QA>PRD

are you making changes directly in production or changing in quality and moving to production?

Here I need expert suggestion how we should make changes, If not on PRD then how to move it from quality as it is master? this is my exact concern.

Yes I understand that there is no possibility to remove KMAT assignment without ABAP and which is not suggested.

Variant is not  configured in PRD we are still testing on quality. But these are query to manage data on PRD after moving VC.

Regards.

ATP

[Ritz · Accepted solution]

ATP _SAP,

Have you gone throughthe report i mention in my previous post?

please check out , it will be helpfull for changing configuration of amaterial variant.

Another input , yes its possible to create these VC related data ( classes , characterstic, values, configuration profile) in quality and test it and then move to production. you can use ALE for it.

My suggesstion is hire a VC professional.What ever we are discussing here is not so easy , which can be achived just by running few transaction.

My opinion is , you need processes setup for VC data design , testing and its migration to production. I also assume linkage with engineering change management.

Hope it will help you.

Thanks

Ritesh

[Former Member · Accepted solution]

Ritesh,

Thank You for valuable inputs.

My team and management want me to explore VC.

Yes I am working on ALE and and more or less we succeed while testing in QA environment except dependency assignment. (I am trying to analyse the problem)

I just want to know if not ALE then what choices we have?

For upload We have developed BAPI and BDC's which are working fine in test client.

We will have dependency only for pricing.

ECM: I am testing with ECM also. I need your suggestion here Can we change Class, characteristics and dependencies with linkage of ECM and Material Variant by report which suggested without ECM.

Regards,

ATP

[Ritz · Accepted solution]

ATP _SAP,

In my view ALE is good opetion to migrate VC data from Quality to production.

But when you also have Change management , its becomes tricky as once a object is created with one ECN in oen system, while migrating we may need same number to be available in next system.

So my suggestion is while making all such decision , involve a experiance consultant, or otherwise it will be mess.

Let me know , if i can if you need more details on same.

All the best.

Ritesh

[Former Member · Accepted solution]

Ritesh,

To migrate we need a clean client where transactions are prohibited only VC master maintenance can be done in this client.

I will be needing your and other experts help and guidance in the forum to handle such scenario.

One more point,

If I don't go with ALE, if we consider ECM only for Characteristics, class and dependencies what problem could arrive.

If possible provide me your details.

Regards,

ATP

[Ritz · Accepted solution]

ATP _SAP ,

Thanks for marking replies helpful.

didnt understand below?

To migrate we need a clean client where transactions are prohibited only VC master maintenance can be done in this client.

you can use Quality to create & test thsi object & migrate them to production.

Thanks

Ritesh

[Former Member]

Hi,

Use following transactions for modifying VC master data.

1. Addition of new characteristics--CT04

2. Deletion of Char Value-------------CT04

3. Addition of new char in Class----CL02

4. Deletion of char from class-------CL02

5. Configuration profile change-----CU42

6. KMAT change in material variant--MM02 (Basic data2 & MRP3 tab)

You may also modify dependencies by CU02/CU22 these changes can be done from Tcode PMEVC.

Thanks

Laxmana

[Former Member]

Hi Laxmana

Thank you for your reply. My query is not about the Transaction codes.

By using these transactions we can change master but it can cause inconsistency in master on live system.

How to avoid inconstancy after changes,

Hope my requirement is clear now.

[Former Member]

Hi,

To avoid Inconsistencies,test/simulate the model in CU50 and modify object dependencies as needed.

Thanks