Why can I release a transport request with an unclassified task?

[Former Member]

Gentlemen,

I am developing and maintaining BEx Queries. Therefore, I created a transport request and assigned it to my package (the standard BEx transport request). Initially, the transport request contained only an Unclassified task. I forgot to switch its type to a Development/Repair. I continued to make changes to a couple of BEx queries without error. Finally, I wanted to release first the task and then the transport request as usually. However, I failed to release the task because it was still Unclassified. Despite this, I succeeded in releasing the entire transport request. And I could import it to the next platform without errors. I verified that all my changes were transported, too.

Having read a lot about the Transport Management System, I wonder why I could release a transport request with an Unclassified task.

Can you explain?

Thanks in advance.

Best regards

Johannes

[Former Member]

Hi

Request contains the task and task contains the changed objects. When the task is first created, it is created as unclassified. When the first modified object is saved in the request/task, the system automatically changes the nature of the task to Development/Repair. This is my observation.

Regards

Murthy

[Former Member]

Hello Murthy,

thank you for your answer.

But in my case, the Unclassified Task must have disappeared from the transport request when I released the request. The object list of the request containing the "Element of the Query Builder" I changed is now directly assigned to the request. This is what I see whe I inspect the transport request using transction STMS.

How come a task disappears from its transport request?

Regards

Johannes