Import of maintenance cycle with deleted transport requests in queue

[Former Member]

We use Solution manager 7.0 with one maintenance cycle per satelite system landscape.

In this maintenance cycle Regular corrections and Urg. corrections are used.

When a transport request (connected to a correction) is re-imported into the quality assurance system.

The transport request triggers a deletion and "add to buffer" of the same request into the import queue of the production system.

The sequence of the transport in the production queue is correct before the "import all" into production is triggered via the tasklist of the maintenance cycle.

During the "import all" of the maintenance cycle into production the re-imported requests are pushed to the end of the importqueue.

The re-imported transports are imported last in the sequence and left in the importqueue.

The deletion of the request in the import queue causes this problem.

Re-importing a request is sometimes unavoidable (E.g. after a client copy to QAS).

All our satelite systems have a 3-tier landscape with a simple transport routes configuration.

We are looking for a solution to problem, this can be either technical or adjusting procedures.

Kind regards

Gert-jan Meijer

[Former Member]

Hello Gert-jan,

your problem is described in SAP note 793879 - Incorrect transport sequence after preliminary import.

regards

Andy

[Former Member]

hello Gert-Jan

The refresh of QAS and Solution Manager is an interesting question, especially when you run different projects in parallel.

When you refresh QAS with the production, you can re-import all transports that were still waiting in the import queue of production but indeed you overwrite all settings done with transports of copies that went to QAS and not to prod.

With CHARM you can manage this properly with the status of the open change documents

[Former Member]

- Consolidated : no problem because you re-import the import queue of prod to QAS with your refresh procedure

- To be tested : problem here because you have lost your changes. You need to reset your correction into development in order to resend you change to QAS with a new test transport or resetting it to be tested

- In development : no major problem because when changing the status to be tested it will resend a copy of the transport to QAS. The our Solution Manager consultant told us it will be an issue but it went ok.

[Former Member]

In this case you avoid sequence issue within your project. It will never solve cross-projects sequence issue. (this is even independant from refresh of QAS)

[Former Member]

Therefore we do not reapply transports of copies but only final transport in QAS.

[Former Member]

Ur.gent corrections are not an issue

The rest is done via Solution Manager

We used this within our company and didn't encounter any issue so far

best regards Xavier

(Apologize for this message cut in4 pieces SAP refuses my post)

[Former Member]

Dear Xavier,

The problem which we're having is that de re-import of any transport causes problems in the importsequence into the production system. This is because the re-import into the QAS triggers a deletion and add to buffer in the PRD importqueue. The same problem occurs when a transport is deleted from the QAS importqueue.

We 're looking reason that SAP / solman modifies the importsequence of these requests.

Kind regards,

Gert-jan

[Former Member]

Hi Gert-Jan,

We do the same and we don't face this issue. There is thus a solution.

I never had this case, this might be a parameter in your QAS refresh procedure.

1/ If you empty your production import buffer (meaning you import it all to production) before tacking the production copy you will never have this issue.

2/ If you have some transportd left in the import buffer of production , you have this issue ? I guess this is our case

I will try to reformulate the case.

The refresh of QAS is causing the lost of some customizing that were not yet imported in production but was imported in QAS prior to the refresh of QAS.

When you reimport the "overwritten" transports in QAS after the refresh, this transport is removed from the QAS import buffer and going too the import buffer of production.

A/The same transport is now twice in the import buffer of production ? we don't have this in our landscape (I even think this was not possible)

B/Or in between this transport has been imported in production and thus you are right it falls in the import buffer of production again with another sequence.

Thank you to confirm your case A or B ?.