topic Problem while transporting Screen exit object from DEV to QAS client in Application Development and Automation Discussions

Problem while transporting Screen exit object from DEV to QAS client

Former Member — Mon, 04 Jan 2010 05:39:21 GMT

Hello All,

I have developed screen exit for tcode 'ME51N' to add customer field in newly added TAB. To grayout that field in display mode, I have added code on the PBO event of that screen. Code for PBO even has been written inside the include. Exit is working fine on development client.

After transporting the exit on QAS client the field graying out functionality in diplay mode is not working eventhough the include which contains the code for PBO even is exist on QAS. Also in flow logic if i double clock on the PBO module event, it says object does not exist, eventhough the include which contains the PBO event code exist in QAS.

Please, help me to understand why the linkage between flow logic PBO event and the include where the PBO code has been written is not getting transported from DEV to QAS.

Re: Problem while transporting Screen exit object from DEV to QAS client

vinod_vemuru2 — Mon, 04 Jan 2010 06:04:22 GMT

Hi,

First check the TR log if there is any errors. If no errors, then check if all the objects were properly transported or not.

You might have missed out in transporting the enhancement activation(CMOD).

Try to Rebuild the object list for updating the navigation index. You can do this from SE80=>Rightclick on function group=>More functions=>Rebuild object list.

Thanks,

Vinod.

Re: Problem while transporting Screen exit object from DEV to QAS client

Former Member — Mon, 04 Jan 2010 06:08:42 GMT

In QAS system, please check project, in which you have included your function and screen exit, is activated or not. If it is not activated, please activate it. Sometimes, after transport, project is not in activated state.

Re: Problem while transporting Screen exit object from DEV to QAS client

Former Member — Tue, 05 Jan 2010 08:37:02 GMT

Thanks a lot Vinod and Ashwin.

Issue has been resolved. It was due to manual error... . One request was missing to transport....After transporting that perticular request issue got resolved....