DEFINE OK_CODE

[Former Member]

HAI,

WHAT IS MEANT BY OK_CODE? AND HOW TO CREATE PUSHBUTTON IN DIFFERENT SCREEN.

FOR EX, IN ONE SCREEN(100) THERE ARE TWO PUSHBUTTONS AND IN ANOTHER SCREEN(200) THERE ARE ONE PUSHBUTTON.WHILE I AM CLICKING THE ONE PUSHBUTTONS IN THE SCREEN 100. IT GOES TO THE SCREEN 200. AFTER IN THE SCREEN 200 AM CLICKING THAT ONE PUSHBUTTON. IT GOES TO THE SCREEN 100. I DONT KNOW HOW TO CODING THE ABOVE DESCRIPTION.CAN ANYBODY GIVE THE CODING

REGARDS

SURENDER

[Former Member]

Hi

ok_code is generally used in screen as of I have used. You will define the function in the screen. and you can use it in the main program.

ok_code acts just as a temporary variable that stores the value of sy-ucomm.

When user interacts with the screen elements, the function code that you have assigned is filled in the sy-ucomm field which is turn gets reflected in OK_CODE.

In your ABAP programs, you should work with the OK_CODE field instead of SY-UCOMM. There are two reasons for this: Firstly, the ABAP program has full control over fields declared within it, and secondly, you should never change the value of an ABAP system field. However, you should also always initialize the OK_CODE field in an ABAP program for the following reason:

In the same way that the OK_CODE field in the ABAP program and the system field SY-UCOMM receive the contents of the corresponding screen fields in the PAI event, their contents are also assigned to the OK_CODE screen field and system field SYST-UCOMM in the PBO event. Therefore, you must clear the OK_CODE field in the ABAP program to ensure that the function code of a screen is not already filled in the PBO event with an unwanted value. This is particularly important when the next PAI event can be triggered with an empty function code (for example, using ENTER). Empty function codes do not affect SY-UCOMM or the OK_CODE field, and consequently, the old field contents are transported.

[Former Member]

Hi,

Check out the below link

[About OK CODE and SY-UCOMM|;

Regards,

Chandru