Question:
Hello,
I have come across a problem I have never encountered. It appears that the BWART field (movement type) has been made into an org level value in our development system. The strange thing is that it is not an org level in QA or PRD. I believe it was never intended to be an org level.
I noticed this because in QA or PRD, you can look at the values in role generator and it shows $BWART. Obviously with that value, you would fail on movement type but users are not failing. That prompted me to look in table UST12 (true authorization values) and you find random movement type ranges like 101-112 etc. which explains why users are not failing even though the role tells me they will.
This leaves me with 2 issues -
1. How do I make BWART a non org level in my development system?
2. What is the best way to make sure my roles in PRD get rid of the specific movement types since the roles tell you they are not there?
Thanks!
Answer:
Execute PFCG_ORGFIELD_DELETE
_________________
bwSecurity