Question:
Hi,
We have functional consultants in different countires responsible for the developement in their own contries. Is it possible to limit their developement work only in their own countries? I guess we can use organisational elements, but this still will not stop their configuration ability in various tables.
Any thoughts on this?
Answer:
SAP does not have currently plan an authorization concept for developers - let alone by country...!
Though, the modularization of humans may create a legal requirement for this at some point in time.
Ned
Answer:
Yes, If dev classes are set up for each country, then the dev roles are restricted to the specifed dev classs, and then assigned to the users.
Answer:
But the developer in class A could write a program to develop something in class B which is a different country?
I have an idea how it could be done, but SAP is built the wrong way round and would be too complex and messy.
As John always says, keep it simple and look at what you are doing.
Ned
Answer:
so org element limitation does not help much?
any more thoughts?
Answer:
If you can write code you have access to everything in every client. There is no control or "other" option.
Answer:
Okay, just thought: I donīt have access to the programs, but if I imagine how they are set up, one could try the following:
Turn the call stack on itīs head to mirror the modularization above it in the application?
If the IDīs correspond to the controls of S_DEVELOP => Walla!
But, if I can read, then one would need to consider modifications both at the end of the current call stack (as I imagine it) and the S_DEVELOP on the screen...
Something like a narrow gateway in the middle (to pass) with a V form where the ends must match (to pass)?
Ned
Answer:
both at the end of the current call stack (as I imagine it) and the S_DEVELOP on the screen...
Sorry, that should have been should have been "on itīs head", not current.
PS: An advantage of such a strategy, in general, could possibily also enable events without the systems noticing it and requiring all sorts of funny entries which are default as OFF, or 1, or 12 or what-ever the logic makes of it.
I think that has been the greatest problem and is causing the greatest concern now with all the ideas going around.
A little miracle could be handy perhaps, and usually happens shortly before the go-live and not during the planning stage
One could even use an object out of the box... like like asset classes? to ensure that the person belongs to that chosen group, a characteristic and has an interest in the companies assets?
Or just use it as a decoy for those who thing that S_DEVELOP is enough => it wouldnīt make the last match at the bottom of the call stack!!!
Mr. Jabba