SAP Function Modules

comments icon Comments

ORA_SYS_EVT_HIS_OKCODE_HANDLER SAP Function module - ok code handler for the GV$SYSTEM_EVENT history monitor







ORA_SYS_EVT_HIS_OKCODE_HANDLER is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ORA_SYS_EVT_HIS_OKCODE_HANDLER into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SDBORA1
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM ORA_SYS_EVT_HIS_OKCODE_HANDLER - ORA SYS EVT HIS OKCODE HANDLER 





CALL FUNCTION 'ORA_SYS_EVT_HIS_OKCODE_HANDLER' "ok code handler for the GV$SYSTEM_EVENT history  monitor
  EXPORTING
    i_okcode =                  " syucomm       Function code / OK-Code
  IMPORTING
    e_dynnr =                   " sydynnr       Next subscreen (0 when end of sub monitor)
    e_okcode_handled_by_submoni =   " xfeld     Flag: OK-Code was handled by sub monitor
    .  "  ORA_SYS_EVT_HIS_OKCODE_HANDLER

ABAP code example for Function Module ORA_SYS_EVT_HIS_OKCODE_HANDLER





The ABAP code below is a full code listing to execute function module ORA_SYS_EVT_HIS_OKCODE_HANDLER including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA:
ld_e_dynnr    TYPE SYDYNNR
,
ld_e_okcode_handled_by_submoni    TYPE XFELD
.




DATA(ld_i_okcode) = 'some text here'.
.

CALL FUNCTION 'ORA_SYS_EVT_HIS_OKCODE_HANDLER'
  EXPORTING
    i_okcode =                   ld_i_okcode
  IMPORTING
    e_dynnr =                    ld_e_dynnr
    e_okcode_handled_by_submoni =    ld_e_okcode_handled_by_submoni
    .  "  ORA_SYS_EVT_HIS_OKCODE_HANDLER

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_e_dynnr  TYPE SYDYNNR ,
ld_i_okcode  TYPE SYUCOMM ,
ld_e_okcode_handled_by_submoni  TYPE XFELD .




ld_i_okcode = 'some text here'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name ORA_SYS_EVT_HIS_OKCODE_HANDLER or its description.


   
 

ORA_SYS_EVT_HIS_OKCODE_HANDLER - ok code handler for the GV$SYSTEM_EVENT history monitor
ORA_SYSTEM_EVENT_HISTORY_INIT - Initialization of GV$SYSTEM_EVENT history monitor
ORA_SYSTEM_EVENT_HISTORY_FREE - Deallocation of all used memory resources
ORA_SQL_SHOW_PROCESS - 
ORA_SQL_SHOW_DETAIL - 
ORA_SQL_SESSION_WRITE_LIST -