topic Re: ok_code in Application Development and Automation Discussions

ok_code

Former Member — Tue, 19 Jun 2007 05:38:51 GMT

the ok_code serves what purpose

Re: ok_code

Former Member — Tue, 19 Jun 2007 05:40:58 GMT

Hi,

The ok_code is of the type sy-ucomm.. Any interaction, which the user does with the screen, the function code gets returned in the system variable sy-ucomm. Even if you double click, it has a function code assigned to it. You capture these function codes and then depending on your requirement, you do further processing.

For example, you are displying a standard sales order details. on double clicking on any of the order no. you wish to show the item details in the next screen. In this case, as soon as the user double clicks, the function code &IC1 (can be found out by debugging ) is returned in the system variable sy-ucomm (or you declare variable ok_code type sy-ucomm). nOw check this variable and do further processing.

Reward all Helpful Answers,

Regards,

Padmam.

Re: ok_code

Former Member — Tue, 19 Jun 2007 05:43:55 GMT

HI Suresh,

Do note the difference between Sy-ucomm and ok_code.

sy-ucomm is for doing the functions what the user wishes to do at that particular event. You use it in menus and other place . this mainly in using <pfstatus>

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.

Thanks,

Sapna

Re: ok_code

Former Member — Tue, 19 Jun 2007 05:44:34 GMT

suresh,

In your application programs, the first step in PAI processing should be to save the function code in an auxiliary variable and then initialize the OK_CODE field. You can then read the function code from the auxiliary variable (for example, using a CASE structure), and control the program flow from there.

The OK_CODE field can have a different name on each screen. However, common practice is to use the same name for the field on each screen of an ABAP program. You then only need one field in the ABAP program, with the same name, into which the function code is placed, and from which you can read it.

Pls. reward if useful

Re: ok_code

Former Member — Tue, 19 Jun 2007 05:45:52 GMT

Do reward points for the helpful replies...

Regards:

Sapna