Transports - Security Team

[Jaynick]

Hi All

Can anyone share who does transports at their company? I would think it's generally a Basis task? Would any issues exist if all members in the security team was responsible for this task? What are the general recommendations around who should perform this task and why?

Any information will be appreciated.

Thanks,
Jaynick

[thx4allthefish]

Everybody having the authorisation to create and release a transport from DEV is responsible for her/his transport.

In QAS there is an automatic IMPORT_ALL every 15 minutes.

In PRD there is an automatc IMPORT_ALL once every day for all the transport requests that have been quality-released in QAS by their owners (= Basis people, security people, functional people and yes, even end-users (we have a very dumb application that needs storage location addresses maintained and transported every day - never mind)).

No human intervention necessary -usually- in case of a returncode >= 8 CCMS is triggered and sends a SMS to the consultant on duty that week.

[swright]

In our organisation transports are owned by the ceator, as epr fish's statement.

They are only released into QA/Test and Prod after approval by one of a team of three senior SAP specialists. This is in line with our Change Management process. A change request must be approved to built (Dev), have a test plan including roll-back (approval to QA/Test system), then once testing is signed off as successful then it permitted to be delpoyed (transport is approved to Prod).

We have 3 seniors, approving, so tat there is coverage when one or two are away. The approval step aligns with our change process and these guys are really useful when there is a major project gonig no, and lots of transports are on the go, with say a planned mass deploy to Prod - cos you want them in the right order!

[Jaynick]

Thanks, this is useful.