fcode leaving Dynpro field

[Former Member]

Hello All

My search in the forums has brought me nothing. Maybe someone can help. How can I have the action of leaving an i/o defined dynpro field (using tab or clicking into a different dynpro field) create an event that will go through PAI / PBO?

Thanks for any ideas.

[Former Member]

u have to write in PAI

c some examples...

REPORT demo_dynpro_tabstrip_local.

REPORT demo_dynpro_tabstrip_server.

REPORT demo_custom_control .

Ramesh..

[Former Member]

you can create a new fcode at this point using this class :

CALL METHOD CL_GUI_CFW=>SET_NEW_OK_CODE

EXPORTING

NEW_CODE = NEW_CODE.

Now a fcode NEW_CODE will be created.You can do some coding for this fcode and after execution control will finally go back to PBO as usual.

[Former Member]

Thanks for the prompt responses. Sorry if I might have been unprecise in my question. What I would like to do is react to the key-press of the TAB key on the keyboard. This will set the cursor on the next line of a table-control and within this process values in other fields of the dynpro will be recalculated. Would it be possible for you to explain a bit in more detail how your answers can help?

Thanks

[Former Member]

Dont you just then want to to set the cursor when your OK code changes to ..'XXXX'. just set cursor then. hope that helps. if so POINTS

Regards

[Former Member]

hi Harry Fumey ,

enter the /H command in the command box then just Press the TAB key and see the SY-UCOMM value(if not create a Fcode from SET PF-STATUS), what is getting, lets say if it getting 'TAB' then write a module in the PAI. just write as normal as we write for a function code

If SY-UCOMM = 'TAB'.

Calculate the fields here which you want to calculate.

Endif.

hope you get some idea from this one

Regads

Sudheer

[Former Member]

Hello Sudheer

Yes, I would like to do this but if for example I start transaction xd02 and then use /H to start debugging mode..... using the TAB key on the keyboard does not trigger any event. No fcode at all is issued and only after klicking a button or pressing the ENTER key does the program go into debugging mode. Please let me know if you get a different result then I do.