Rf screen BACK button issue - text is not displayed correctly

[Former Member]

Hi Experts,

I have developed custom tcode using Module pool which is called through RF handheld device.

when it is executed, it shows the test on LM01 tcode correctly after which my Ztcode is called. When i press back button, LM01 is called but the text is shown as <DIV ct = onclick = "SetokCode(=NEXT);"/>. it works fine on desktop, the issue is only on RF handheld device.

On BACK button, I am using LEAVE PROGRAM which works fine in existing custom tcodes.

It looks like RF screen si not getting refreshed. Any pointers will be helpful.

Thanks,

Rupali

[Former Member]

Hi Experts,

I have developed custom tcode using Module pool which is called through RF handheld device.

when it is executed, it shows the test on LM01 tcode correctly after which my Ztcode is called. When i press back button, LM01 is called but the text is shown as <DIV ct = onclick = "SetokCode(=NEXT);"/>. it works fine on desktop, the issue is only on RF handheld device.

On BACK button, I am using LEAVE PROGRAM which works fine in existing custom tcodes.

It looks like RF screen si not getting refreshed. Any pointers will be helpful.

Thanks,

Rupali

[SwadhinGhatuary]

Hi,

use once

set screen 0.

leave screen.

[Former Member]

I tried this, still it is showing HTML code on Handheld device.

" onclick="setOkCode('=CLR');" />

" onclick="setOkCode('/EBACK');" />  " onclick="setOkCode('=NEXT');" /> 

" onclick="setOkCode('=1');" />  " onclick="setOkCode('=2');" />  " onclick="setOkCode('=3');" />

[SwadhinGhatuary]

CHECK once that on back which ok code trigger.

use at exit command of back

look at this

http://scn.sap.com/thread/1958850

[Former Member]

On BACK, correct OK code is triggered as I can see it is working perfectly when tested on SAP but is failing on RF hand held device.

Thanks,

Rupali

[Former Member]

Hi Rupali,

Please create an HTML Template for each screen of your Z-Transaction for the corresponding Internet Service.

This will resolve the issue. 

Regards,

Bhakti Madhav