CHARM transports - all transports have to go to production?

[Former Member]

Does CHARM require all transports created in DEV have to go to QA and production?

What if you have specific transports for data loads in QA that is not required for production?

also what about security transports that target only QA?

This seems like a huge risk to move a transport into production that is not required for prodc....

CHARM doesnt seem flexible so why should I use this tool?

Thanks

Mikie

[Former Member · Accepted solution]

Hi Mikie,

you could create another maintenance project with a logical component in which you specifiy your DEV and QA system only.

Then you can do your transports just till QA and not to PROD.

Regards,

Alex

[Former Member]

Thanks for the info....that solves one problem.

Is there a way to migrate transports from on maintenance project to another...

So if I build one project called TEST and specify DEV and QA....and the another prject called GO LIVE and use dev qa and prod...

can I selectively add transports from project TEST to project GO LIVE?

Also what tables contain the transport information for each project....

thanks

mikie

[Former Member]

Hi Mikie,

in the change request you have to specify in the field component to which system you want to transport.

That means for your example:

If you specify the QA you only get the assignment to the TEST project.

If you specifiy the PROD you only get the assignment to the GO LIVE Project.

You could change the attributes on the transport header in SE01/SE10 manually to set it to another project.

But for what would you want to do that?

The tables for the transport data are E070*.

Hope that helps...

Regards,

Alex