Jobs For wrote:
We converted RESPAREA as Org level value ...
Ouch, ouch, ouch.... You should not do that and if you do (SAP will not stop you except warning about the roles which already use this complex field...) then you have to be very disciplined about naming conventions in CO master data and are booby-trapped into keeping the objects sharing the field separate from each other at role level, as they will be cascaded, but they cannot be (except for the KS scenario is you only ever use that).
Basically you have created a mess. I don't thing that a discussion here can help you to be very honest, as you are going to have to rethink the whole thing. This might have impacted your role design more than you can imagine.
Just being honest - as you have an anonymous user ID description, I assume that is no problem for you...
Cheers,
Julius