11-16-2009 12:43 AM
hi guys,
we have a table index that is active in SE11 but in transport request (SE10) its inactive. Why is this so? how to fix this?
Thanks!
11-16-2009 3:30 AM
Hi Freishz ,
Sometimes in the Transport request, objects will not get updated.
Transport organizer and open the tree of Transport request and click on Refresh.
It should update and show Index related request number in that.
If this does not resolve your issue, Open the index and check in which transport request this index is getting stored in Object Directory Entry.
In case if this does not resolve the issue.
Try to delete the table entry from the transport list and save the index once again in your table and activate it.
Save it in the transport request and try.
If this does not resolve the issue then please let me know, if the Index is just created in your development server ?
Regards,
Kittu
11-16-2009 2:29 AM
Hi,
Try to delete the table entry from the transport list and save the index once again in your table and activate it.
Save it in the transport request and try.
Regards,
Subhashini
11-16-2009 3:30 AM
Hi Freishz ,
Sometimes in the Transport request, objects will not get updated.
Transport organizer and open the tree of Transport request and click on Refresh.
It should update and show Index related request number in that.
If this does not resolve your issue, Open the index and check in which transport request this index is getting stored in Object Directory Entry.
In case if this does not resolve the issue.
Try to delete the table entry from the transport list and save the index once again in your table and activate it.
Save it in the transport request and try.
If this does not resolve the issue then please let me know, if the Index is just created in your development server ?
Regards,
Kittu
11-16-2009 4:10 AM
I'm not sure I understand the question. In the transport request you should only see the index, not if it's active or inactive. Basically the transport request should initially only contain the reference to some object and later, when the transport is released, a snapshot of the version is taken. Thus for example when you delete the index, it will still be present in the transport, but at release time SAP would figure out that it's no longer there and therefore has to be tagged as a "delete action".