cancel
Showing results for 
Search instead for 
Did you mean: 

Updating a characteristic value (CT04)

scottcarricknwn
Participant
0 Kudos

I have created a new class with corresponding characteristic. My characteristic has a single value, "01" representing document version number. I the MM, i add this new class to the Classification view for the appropriate material number. However, i have noticed that when we go to update the value in the characteristic, from lets say "01" to "02", we first get an error saying the value cannot be deleted (but the system lets us do this anyway) but more importantly when we do change the value, our hope was that the value in the MM class would automatically be updated as well. That doesnt seem to be the case as I have to physically go into the MM record and delete the class, then re-add it with the new updated value for the update to appear in the MM record as well as AUSP. This is my first time dealing with classifications/classes. Can someone give me guidance on how to achieve something more easily maintained?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hello

it does not update the material master automatically when you change the characteristic value. You have to manually make the changes in material master or in CL24N transaction code.

Check this link for more information on classification - https://help.sap.com/saphelp_46c/helpdata/en/24/47633a416711d189ec0000e81ddfac/frameset.htm

scottcarricknwn
Participant
0 Kudos

Thanks span 1. CL24N will get the job done. However, when there are 200+ material numbers assigned to one class, i still have to change them one at a time in CL24N. I wish there was a way i can update the whole block of records at once.

Answers (2)

Answers (2)

former_member42743
Active Contributor
0 Kudos

Have you looked at using transaction CLMM for making the changes?

Craig

scottcarricknwn
Participant
0 Kudos

Thanks Craig. I'm not too familiar with this transaction. I see i can set and change the value of a characteristic but not sure how that connects to the MARA record?

former_member42743
Active Contributor
0 Kudos

In the CLMM transaction, select "Set and Change Values". 

In the next screen, enter in 001 for material class in the class type field.  Then add the characteristics you wish to change on the tab labelled "Chars".  You can just add a new value to change all instances or you can specify an old value to change and only those with matching values will be changed.

Now click on the "Target Objs" tab.  Enter in the material numbers you want to change.  Click on the indicator "Overwrite Existing Values" to replace values, leave it blank if you are adding new values for a characteristic that allows multiple values.

On the menu bar is a button labelled "Test".  Click on this to do a test run and see the log that is generated.  When you have all the right selections, and the log looks correct, click on the button to the left of the Test button to execute the changes.

You can also use this to mass change assignments in certain classes. On the first screen,  the first choice "Copy Values assigned to object" allow you copy the values from one object to another.. say for instance all the material class values from material A to Material A, B and C.

The third choice is "Assign value in matrix".  This is very cool as it gives you a spread sheet form with the all the objects, (materials), listed vertically, and all the characteristics listed across.  You can see the current values, and manually change any of the ones you want to.

This can be a very powerful transaction.  It should be limited to only a handful of people

Craig

scottcarricknwn
Participant
0 Kudos

Awesome stuff Craig. Thanks very much for your time.

Former Member
0 Kudos

Hi Scott,

If the characteristic represents your document version number, what makes you delete an allowed value of 2 in CT04? Directly go to MM02 and change the characteristic in the classification tab. Also, you will have to have more allowed values in your characteristic, say 1-10 or something.

The message clearly states that deleting will lead to inconsistencies. You are deleting an allowed value which will be effective from the next transaction, not for characteristics already using this value.