Customize change docs for classification

Question

Hi all,
I need to activate change documentation in order to be able to track changes for classification characteristics. In SPRO found that I can set it in Cross-Application Components >> Classification System >> Classes >> Maintain Object Types and Class Types
I'm interested in tracking changes of materials so chose table MARA and class type Material Class but to activate change docs there is need to set first "multiple objs allowed" and to do it I had to start RCCLUKA2 program. I did it for my class type, program has finished, it has created 2 files in DIR_HOME (DSKSSK,DSAUSP). Files are still on application server.
And here is my problem because checkbox "Multiple objs allowed" in SPRO still is not checked in spite of fact that program has finished without any errors. I tried to run report once again but got message: "Entries already exist in the INOB; check data"
I checked table TCLA field MULTOBJ and it's is empty for my Class Type. I have no idea what to do. Please help what to do in such situation and how to activate this change documentation for classification.
Thanks in advance for any help!
Best regards,
Darek

Answer 1

There are a couple of reason but part of it is following the whole "Don't change SAP standard, rather create a copy with a z naming convention for changes principle".
As a consulting company and given the fact that we are not the owners of the system, we sometimes don't have the opportunity to investigate if any objects are used elsewhere and in some cases, users themselves aren't aware that they are using the system in other areas (for example, some people don't realise that documents in the DMS are used in other areas like EH&S). By creating copies, we eliminate the possibility of making a change which may adversely affect another working area of the system that the project initiator is unaware of. It doesn't happen often that you make a change that impacts on others, but i'd rather take precautions than solve the issues afterwards.
We've also found that in some cases customers are incorrectly using something for the wrong purpose. For example, we found someone using the document structure type for reporting areas in another area of PM so we couldn't implement EasyDMS because they had changed one of the standard object types.
Edited by: Athol Hill on May 6, 2009 10:38 PM