Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Hello All - I wanted to see if there is any work around for my issue, here is the scenario:
Company policy says contractors cannot get access on PRD, so on every sandbox refresh contractors or interns are losing their access because sandbox is a copy of production.
I was trying to find if there is any work around to come over this issue, like putting these specific users in transport with their roles. This way I can import this transport to sandbox after sandbox refresh.
I searched user admin tcodes to see if I have any options, I did not see any.
In this case as mentioned already the effort is eased out if a separate client is used and data related to roles and users are exported and re imported in the client in Post Refresh step.
As you are not concerned about data confidentiality, but only it's integrity (in PROD), I would recommend creating a "Backup" client.
Assuming that your "refresh" is still capable of doing it via a client copy (temporarily permitted?), you can then do another client copy from the backup client to your "contractor sandbox client" after the fresh.
If it is a system copy, then consider a backup client in an intermediate system (e.g. QAS) to copy back from for the user profile, and then reactivate the ID's for them, You could provide a password self-service for them, which would also validate whether they are on the project or not - for example by sending a password on request to the mail ID, possibly after having been able to correctly answer an embarassing question....
In this case as mentioned already the effort is eased out if a separate client is used and data related to roles and users are exported and re imported in the client in Post Refresh step.
Bluesky
