Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

AUSP Data Inconsistency after Char. Value Deletion

former_member305388
Active Contributor

Hi Experts!

We have written a program to display the classification data of a material through CLAF_CLASSIFICATION_OF_OBJECTS. While testing we figured a strange thing. For a specific characteristic ABC, we earlier had char values as 1, 2, 3 and 4. And for material MAT1, in AUSP, we have a record with ATWRT = 3. However, after sometime, these char values are modified where 3 is deleted. But we still have the record existing in AUSP. Now, when executing for material MAT1, we are getting the value for ABC as 3 from the FM, but in MM03 we can see this clearly as blank, as 3 is no more valid.

To correct this the only way that we see now is to write all selections (like KLAH, KSML, CABN, CAWN, AUSP etc.) and display the output details. This looks to be rigorous job for us now and hence we would like to correct AUSP inconsistency through some note or so. We have searched for a few but didn't find any specific thing for char values. We were able to find some related notes to char deletion, but not char value deletion.

Can someone please provide your inputs? Your help is appreciated.

Thanks.

3 REPLIES 3

JL23
Active Contributor
0 Kudos

If you just deleted the allowed values from a characteristics then this does not automatically remove the values that have already been used to classify one or a million materials.

What you see in MM03 is also very depending on the individual user settings, as characteristics and classification values can be displayed technically neutral or language dependent . (menu Extras > user settings when you are in the classification view of your material)

Why no allowing the value again? then use CLMM for a mass change of your existing data, and once this is done you can remove it from the allowed values.

former_member305388
Active Contributor
0 Kudos

The problem is not with the saving of new values. We are able to provide and save new values. But when we run the report, we are getting the obsolete values displayed. But if AUSP records are corrected, then it means these obsolete data will be deleted and thus getting blank for those char. in the output of the report too. So, what we need is a way to correct the AUSP records.

0 Kudos

Hello!

In AUSP table, field Author, filter "Do not select: Equal to" = 8

Records with Author = 8 have inconsistency.