Transport of User Roles in SRM

Question

We are using SRM 4.0 with 3 systems (Development, Quality, Production)
We have created roles where we use Authorization Limitations on
Purchasing Org. level. To limit this we need to enter the ObjectID of
the Purchasing Org. from the organizational structure (ppoma_bbp).
The problem is the the ObjectID is added to the purchasing org. in each
system when the organizational structure is created. So the ObjectID of
purchasing Org. XXXX is not the same on the development system, the
quality or the Production system.
So the authorization needs to maintained directly on each system.
Is there another way to do this?
Or is it possible use the name of the purchasing org. instead of the
ObjectID is the authorization?

Answer 1

Anders,
this would be quite hard to achieve I assume. The org.Mngmnt. has a very complex data model - although you might be able to enter a name into the corresponding field (type string probably), there might be checks within the Org.Mngmnt. SRM Org.Mngmnt consists of BC/HR-(you could say)layers and on top of this SRM is built with its own logic. Let's assume that you will switch off/modify the checks in a way that you can maintain a name instead a number on Org.Mngmnt. -- you still have to check, whether your new value can be stored in all the tables holding the SRM transactional data. I think at this point you would run into hard problems...
Only option I see is to live with the 'wrong numbers' in the non-productive systems -- then, each time when this wrong value is passed into a backend document, you have to replace the Purch.Org.ID with correct for the corresponding backend in a BADI <filling the right values from a routing table>.
But there might be many pitfalls - eg. depending on the technical deployment scenario etc. etc. To be honest... I don't see this as a viable solution. Maybe somebody else has an idea.
Richard