Transport role directly from qas

hello,
i created role on qas (not on dev) and i want to transport it to prd system. when i go to stms and want to transport role, its name is i.e.
tstk90002. of course, i can not see it regulary on prd, but if i go to "import other request" and put exactly that name, it allows me to do that.
in a que on prd system all trasported requests are like devk90003...or so, so i am scared to do that.
is it possible to transport request from qas which is not created on dev?
thanks

hi,
you must go to your DEVELOPMENT system and re-create the Role, before performing a transport to Production.
It is not best practice to create a Role in QAS and then attempt to transport it to Production.
The transport route is from DEV-->>QAS-->>PRD
So do what is appropriate...go and start your role creation process in DEV...you should not create Roles in QAS, but DEV and then transport accordingly.
chumy

This should be a question for your Basis team as it is dependant on TMS
setup.
Why don't you create the role in Dev and transport through the standard
route? It will take 5 minutes to copy it into dev & do it properly.

To do a transport from QAS is not the correct way. Your system landscape
is not design for that.
You don't have to recreate the role in DEV, you can download it on QAS
and upload it in DEV. Then you put it in a transport and take it to QAS
again and then to PRD.
This will ensure that your Landscape stays in sync.

Hi,
why not download the role from QUA (PFCG -> menu bar "Role" -> "Download" (Ctrl+F11)) and upload it to DEV and then make a correct transport DEV -> QUA -> PRD?
Why did you create a new role in QUA at all?
Development should be made in DEV always.

Well. If creation time is an issue, just download the role from QAS to your
PC and then upload to DEV. Open the role in PFCG at DEV and make sure
everything is OK. Generate the role again and transport DEV--> QAS --> PRD.

H eniac,
Looks like you are not able to see transport in the queue / buffer, you can
add it into the queue using import other request
and once its in the queue you can import.
is it possible to transport request from qas which is not created on dev?
it depends on settings

Advice for a security person:
You should create all the roles in dev and move it to QA and then to
production.
Before transporting the request you need to know your TMS configuration / be
in touch with basis guy.
Thank you,
Sonia

Allright folks, I'm revoking all of your access to auth object SEC_EXPRT.
I've seen enough posts from most of you to know that you know better
than to initiate a transport out of QA. The potential for code
regression is significant, both for creating a transport in any instance
other than DEV and for downloading and uploading. Either of these
procedures will also render any transport tracking (e.g., Rev-Trac)
useless or worse for the contents being relocated with these methods.
Ask yourself this question: Does your basis team have a step in their
procedures for completing the transport path when this Role is ready for
Prod? Will it get to Prod if uploaded/downloaded?
Or this one: How will Basis know where this transport fits into the
transport sequence for cutover? If upload/download, will that be done
again for Prod?(!!!!!!)
Lastly: Will this transport fit into your change management procedures
and approval path? Is there a CM procedure for upload/download?
Lots of other questions, but you get the point. GIGO!
Thanks for listening.

Hi,
Normally QA system is setup as not modifiable, however if you are able to
create request in QA and as you already know the request #. Please ask Basis
person to copy co file and data file to Dev trans Directory and import to
Dev via OS level commands. Then once you re-generate role in Development can
move it to production.

Sheffeld,
The upload/Download others suggested is only for copying the role that he already created, instead of manually recreating the role in DEV. Then delete the one in QA. Once the role is in Dev, then he should be initiating a transport request like usual.
Please correct me if I missed something.
Thx
Lnb

Copyright 1998-2015 Ziff Davis, LLC (Toolbox.com). All rights reserved. All product names are trademarks of their respective companies. Toolbox.com is not
affiliated with or endorsed by any company listed at this site.