Meaning of each BDC_OKCODE

[Former Member]

Hi...Guru...

I'm doing data conversion using BDC. However, I have question about meaning of each BDC_OKCODE. Anyone has a list of meaning of BDC_OKCODE for example, \00, =TSMAIN, = TSLINKS, etc., please send me to email a.trongsittirak@gmail.com. Reward is available for your kindness. Thank you very much.

Cheers,

[former_member188829]

Hi,

[Former Member]

hi

good

please check this

Direct call of transactions, session handling:

/nxxxx This terminates the current transaction, and starts transaction xxxx

/n This terminates the transaction. This generally corresponds to pressing F15 to go back.

/nend This termiantes all separate sessions and logs off (corresponds to System - Logoff

/nex This terminates all separate sessions and logs off immediately (without any warning!).

/oxxxx This opens a new session and starts transaction xxxx in This session.

/o This lists existing sessions and allows deletion or opening of a new session.

/i This terminates the current session (corresponds to System End

/i1, /i2,... This terminates the session with the number given.

.xyzw Fast path: 'xyzw' refers to the underlined letters in the menus. This type of navigation is uncommon and is provided more for emergencies (such as a defective mouse).

Batch

The following commands can be entered in correction mode ('Process in foreground' or 'Display errors only') when processing a batch input session:

/n This terminates the current batch input transaction and characterizes it as

/bdel This deletes the current batch input transaction.

/bend This terminates batch input processing and sets the session to Failed

/bda This switches from Display errors only to Process in foreground

/bde This switches from Process in foreground to Display errors only

ABAP/4

/h This switches into debugging mode.

/hs This switches into debugging mode and activates the debugging of system functions.

Buffer

WARNING: Resetting buffers can significantly change the performance of the entire system for a long time. It should therefore only be used where there is a good reason tdso. As of release 3.0B system administator authorization is required (authorization object (S_ADMI_FCD). The action is noted in the system log.

/$SYNC This resets all buffers of the application server

/$CUA This resets the CUA buffer of the application server

/$TAB This resets the TABLE buffers of the application server

/$NAM This resets the nametab buffer of the application server

/$DYNP This resets the screen buffer of the application server

R/3 note no. 45507

The note summarizes general rules for processing batch input sessions in the foreground.

/*xxxx starts transaction xxxx and skips the first screen. So, it has the same effect as /nxxxx followed by ENTER.

=xxxx This entry is still possible for compatibility reasons, but is nlonger supported.

%sc Searches character patterns in lists

%pc Downloads lists

%pri Prints lists

reward point if helpful.

thanks

mrutyun^

[Former Member]

Hi

You can not get list of BDC_OKCODE. If you really want to find some informatio on this, just try like below.

Reward if it dose something.

Thanks

Siva Kumar

'/00' is generally the BDC_OKCODE for the ENTER key.

You don't need to know the list of the BDC_OKCODE s.

You go to the transaction SHDB.

You can execute any transaction here.

Then you can replay the execution of the trasaction afterwards.

Select 'display all screens' mode.

BDC_OKCODEs for each one functions you use is displayed on the screen.

Now, regarding the error handling in call transaction.

The BDCMSGCOLL does not have the messages text. It has only the message type, number and message parameters.

You have to read the message text. (recall that the database table T100 stores all the messages.)

There are more than one method of doing this.

Following is the psuedocode for one of the methods.

LOOP for the internal table IT1 which has data value from flat file.

call transcation using....

if SY-SUBRC <> 0.

Read the dictionary table T100 FOR ALL ENTRIES in BDCMSGCOLL.

(also use the condition T100-SPRAS = SY-LANGU (the log on language. This is because you need only the message texts in English if the user is logged in English language)

IF message type is E , then, transfer the contents of this particular error record to file x. (TRANSFER......)

( Ignore all other messages. Only consider type 'E' messages. Ignore other types of messages.)

(You can also store the message text from T100 and the error record in another internal table IT2)

.....

....

ENDLOOP.

Please note that the client might ask you for a file of records which could not be uploaded.

Give him the file created in the above psuedocode. (most often you will have to do this).

Otherwise just display the error messages and the error records in the internal table IT2 in the form of a list.

Thats it.

Alternatively,

Instead of

" Read the dictionary table T100 FOR ALL ENTRIES in BDCMSGCOLL."

you can use the function module

WRITE_MESSAGES to read the messages.

Please refer to the function module for the list of parameters.

Also refer FORMAT_MESSAGES function module.