topic Re: bdc_okcode & bdc_cursor in Application Development and Automation Discussions

bdc_okcode & bdc_cursor

Former Member — Tue, 12 Feb 2008 22:52:07 GMT

hi friends

what is the difference betweenn

bdc_okcode and bdc_cursor

Re: bdc_okcode & bdc_cursor

Former Member — Tue, 12 Feb 2008 22:56:30 GMT

BDC _OKCODE

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.

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.

Refer the link:

http://help.sap.com/saphelp_47x200/helpdata/en/d1/801e61454211d189710000e8322d00/frameset.htm

Re: bdc_okcode & bdc_cursor

Former Member — Wed, 13 Feb 2008 02:05:13 GMT

BDC_OKCODE

BDC_OKCODE is used to trigger the function keys

BDC_CURSOR

BDC_CURSOR is used to place cursor on particular field.

BDC_OKCODE

OK_CODE is the key which gets filled when u click on user-commands(like buttons).

BDC_OKCODE is one which is normally used in BDC programming...When U want to navigate from one screen to other screen or u want to press enter or save buttons...U need to fill the BDC_OKCODE with revelant values so that while running the BDC u can navigate according to the values specified.

Execute the transaction SHDB and give the transaction for which you want to do A BDC. Enter all the details and then save it.

Now, when you see the saved data, you can see that in many places, BDC_OKCODE would have some values like /00 and such things..These indicate, what is the action that you have done ,

For example, /00 indicates ENTER.

BDC_CURSOR

Eg...HANDLING OF POP UP SCREEN IN BDC

Many times in transaction pop up screen appears and for this screen you don’t pass any record but some indication to system telling it to proceed further.

To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.

Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.

Re: bdc_okcode & bdc_cursor

Former Member — Wed, 13 Feb 2008 04:20:52 GMT

hi,

BDC_CURSOR is to place the cursor in the field where u want.

BDC_OKCODE is the command to trigger the particular action.