topic Re: Transporting Roles in Application Development and Automation Discussions

Transporting Roles

Former Member — Wed, 24 Dec 2008 14:53:00 GMT

Hello,

When transporting roles, do these need to be performed from the golden client, or can it be done in another client.

Thanks TO All.

Re: Transporting Roles

Former Member — Wed, 24 Dec 2008 17:33:01 GMT

Hai,

Normally the customised roles for example the roles which you create from standard SAP roles are transported to other systems, you can do it from the client in which you created the role.

No need to do it from Golden client.

Regards,

Yoganand.V

Re: Transporting Roles

Former Member — Fri, 26 Dec 2008 06:09:41 GMT

Hi-

I guess, the role finally will move to production box. If so, you are recommended to transport to golden client first and then distribute to other qulity boxes from there. This is what has been conventional way of transporting roles to production.

Cheers!

Ashok

Re: Transporting Roles

Former Member — Fri, 26 Dec 2008 15:01:25 GMT

Hi - I would say it is also depends on your transport route, conventionally it always Golden client from where transports are moved evenly to all your Dev/QA/PRD clients. It will hard for you to keep your roles in sync on all systems if you have many clients. (005/010/060/021/....in our work place)

I hope it helps little bit!

Thanks.

Re: Transporting Roles

Former Member — Sat, 27 Dec 2008 15:28:42 GMT

Always recommended to transport it from the Golden client, esp when creating new roles. Every profile matches up to only one role.... and normally profile generation follows a number sequencing. The conflict will arise when 2 different roles are generated with the same profile name in 2 different clients.

If roles are generated in various clients in the same transport landscape, there is a chance of the profiles getting mismatched and the profile number ranges will get whacked out! Leading to further dismay of roles not getting imported due to profile inconsistencies, and a regret of doing it the right way in the first place.

Re: Transporting Roles

Former Member — Sat, 27 Dec 2008 17:30:51 GMT

> Abhishek Belokar wrote:

> .... and normally profile generation follows a number sequencing.

It does not have to, but it is IMO better that it does.

> The conflict will arise when 2 different roles are generated with the same profile name in 2 different clients.

It does not have to. Take a look at - and the SAP Note mentioned towards the end.

> If roles are generated in various clients in the same transport landscape, there is a chance of the profiles getting mismatched and the profile number ranges will get whacked out! Leading to further dismay of roles not getting imported due to profile inconsistencies, and a regret of doing it the right way in the first place.

Another possibility is to transport the role data without generated profiles, and generate them locally in the target clients.

Don't say that SAP is inflexible!

I don't think there is any correct answer to this question.

Cheers,

Julius

Edited by: Julius Bussche on Dec 28, 2008 9:55 AM

Link corrected.

Re: Transporting Roles

Former Member — Sun, 28 Dec 2008 01:58:41 GMT

Well ...never said SAP is inflexible in any way...

Actually had come across this situation, where custom and unfortunately SAP standard roles were also generated in QA and many other clients, and we had to do a whole clean-up to first sync, get all updates to the golden client and then export and import the entire roles.

Rightly said, An alternative (which is always there and is always bombarded!) is transporting without profiles or downloading / uploading, then SUPC, but its easier when gone with the profile, (if) considering having multiple target clients

Moral for us was: follow the best practices