Transport exported from DEV not added to the import buffer of TST System

[Former Member]

Hello all... here is a quick question.

We have a 3 system landscape. We have a job running in the test system every 15 minutes to import the transports that were released in the past 15 minutes. I know it may not be the job but, for some reason (very sporadic), occasionally, one or two transport in a day do not get automatically imported to test system.

On further research found from the log that the transport did not even get added to the test buffer when it was released from development. The only log I see is, it is exported from Development and no further logs. Which means, the transport did not get added to the import buffer of test system.

Any idea what could be the cause? Did any of you been through this before?

Thank you.

[Former Member]

Had to apply patches to fix the problem.

[Former Member]

Hello,

We had a similar issue where a developer chose the wrong package to work in, which meant an incorrect transport layer assigned. These workbench related transports released ok but did not go to QAS. Once the package assignment was changed to a package allocated to transport layer z it worked for future transports. For example you can see an ABAP program's package in se38 - goto - object directory entry (from the popup select the Object attributes icon for the transport layer )

Regards

Robert

[Former Member]

Check if the transport is exported successfully from the development system, this usually happens when there are problems exporting the transport request, due to which the data and cofiles are not exported either with warnings or error( reason could be the network problems sometimes). Just make sure that you donot release another TR when you are not done with the previous one( you can check the logs in SE09 if it is being exported successfully).

In case of export problems you may add the transport to QA and prod systems following the path Extras> Other requests> Add.

Regards,

Sarita

[Former Member]

Please confirm if you are using a Standard job or a customized job to import into the target system.

try to add the requests manaully using TP command, if they get added then its the problem with the program.

please check and confirm

[Former Member]

Thank you for the quick response. The program used by the job is TMS_BCI_START_SERVICE. This is a standard program used for this purpose.

But, here is my thought. I don't even think the problem could be with the job.The reason is, I don't see the transport request in the TST import buffer at all. Usually, the automatic import jobs only starts working on those transports that are already added to the import buffer. In my case, the transport request released from the DEV system is only shown in the logs as exported from the DEV client. But, the log does not show as added to the TST import buffer. This doesn't happen to all the transports. Most of the transports are added to the TST import buffer and imported into test automatically by the automatic import job. Only one or two transports in a day go through this problem.

Any idea what the problem could be?

Thank you.

[Former Member]

Hi,

Could you correct the problem? I got the same error with some rwquest that are not added to the QA buffer.

Thanks

jose

[Former Member]

Hi,

Please have a crontab script designed to only add the request to the buffer of qas and have it schedule at 15 min.this will help in unix and in windows you can use some scheduler.

this way you can minmise the error.

thanks

Rishi Abrol