QUESTION POSED ON: 05 March 2002
What is the best way to restrict movement types within transactions for a particular activity group? For example, I have an activity group which contains transaction code MB1A. I want to restrict this to movement types 221, 222, for example. However when we test, other transactions within this activity group are now also restricted e.g. MB1B. So everything that uses MSEG_BWA is affected. This means that every single transaction within the activity group needs to be checked in case it uses this. In some cases, even transaction codes that are flagged as having no impact, do not work. Is there a better way to do this?
|
