cancel
Showing results for 
Search instead for 
Did you mean: 

transport request problem with a ztable

Former Member
0 Kudos

Hello,

I have some problems releasing a customizing transport request. It contains "table contents" of a z table. This z table is marked as "customizing table" (option C).

Error message is "task desk900213 belongs to a different category"

Thanks.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Alberto,

What type of request are you using. Also let me know the classification of task.

I mean if you a workbench request is giving this error then try using a customising one and if a customising one is giving this error try using workbench transport.

I guess this is related to the thread:

Also I hope you have assigned a development class to the Z table.

Please award points accordingly.

Regards.

Ruchit.

Message was edited by:

Ruchit Khushu

Former Member
0 Kudos

Yes Ruchit, it is related with that question.

It a customizing request.

On releasing the request:

"Not all objects in the request could be locked.

Do you want to release then anyway?"

The error is

"Object messages R3TR TABU ZFI_VTOS

Task DESK900213 belongs to a different category"

Table ZFI_VTOS belongs to a package.

Former Member
0 Kudos

Hi Alberto,

You can ignore this error and go ahead with the release. Should not be an issue. I have done it several times.

But before that try this thing out. Select the task/request. In the menu bar select Request/Task -


>Object list----


>Lock objects.

Even if this doesnot work and the error reappears ignore it and go ahead with the release.

Please award points if answer was helpful.

Regards.

Ruchit.

Former Member
0 Kudos

System doesn't allow me to release the request.

I select "Yes" but it shows me the error.

Former Member
0 Kudos

could you please move this object to seprate request and try to relese both the request.

Cheers,

-Sunil

Former Member
0 Kudos

Problem solved.

Developer had changed the category of the table to CUSY.

I have changed it to CUST and all is working now.

Thank you all

Answers (1)

Answers (1)

Former Member
0 Kudos

do you have more detailed logs available?

cheers,

-Sunil