cancel
Showing results for 
Search instead for 
Did you mean: 

Tansport Target group: not all requests goes to production queue.

Former Member
0 Kudos

Hello,

I'm new to transport target group concept. All of my installations made so far used only simple transport

route (Standard config, 3 systems in group). But for this new systems, the DEV and QAS were installed

previously and configured "target group" like following:

Consolidation:

DEV -> QAS:300, QAS:400, QAS:500, QAS:600

Delivery

QAS -> PRD:800, PRD:900

The problem is one of the QAS client (QAS:500) is not being used and inactive for some time. So most

of the transports made so far goes to only QAS:300, QAS:400 and QAS:600. (not QAS:500) So most

of the requests are now showed up on PRD import queue.

Also the transport requests of ABAP programs were imported to only 1 QAS client.

I'll have to import the requests to Production in a few weeks now. I still have no idea how to

make these requests show up in Production system.

Is it possible to make the requests, that imported to only 1 (or more) client on QAS, show up on PRD queue?

If I cannot make these requests show up on production. Is it still possible to use:

tp addtobuffer ...

with client specified...

Regards,

Apisit Saksomboon

Accepted Solutions (1)

Accepted Solutions (1)

jörg_weichert
Explorer
0 Kudos

Hello,

Also the transport requests of ABAP programs were imported to only 1 QAS client.

ABAP programs are client independent thats why they are only imported in one client.

Cheers!

Jörg

Former Member
0 Kudos

Since all ABAP/Workbench requests will be imported to QAS to only 1 client.

And if I configure transport target group (with multiple clients on QAS), these

ABAP/Workbench requests will never show up on PRD queue, unless manually

forwarding those requests to PRD.

I don't think it make any senses. So I have to import ABAP/Workbench requests

to all clients on QAS to make them show up on PRD queue?

Edited by: Apisit Saksomboon on Jan 28, 2010 4:36 PM

jörg_weichert
Explorer
0 Kudos

Have you tried to create target groups for consolidation and delivery using client dependent transport routes?

What have you defined as source for delivery?

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello,

Use the import history of your QA system, this can be done via STMS.

In the import history you can use some filters like date and client.

In the import history of QA make a correct selection of the requests, select them and use the forward function in STMS to forward them to the production queue.

Before this operations you can first delete all pending requests in the PRD queue.

Afterwards you will end up with a production queue containing all requests in the correct sequence that were once imported in QA.

Success.

Wim

Former Member
0 Kudos

Thank you for very helpful workaround.

I think there might not be anyway to make all requests goes to PRD queue automatically.

So this must be the easiest way so far.