SAP C104_HANDLE_SUBS_OKCODE Function Module for NOTRANSL: EHS: Okcode Verarbeitung vom Subscreen









C104_HANDLE_SUBS_OKCODE is a standard c104 handle subs okcode SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: EHS: Okcode Verarbeitung vom Subscreen processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for c104 handle subs okcode FM, simply by entering the name C104_HANDLE_SUBS_OKCODE into the relevant SAP transaction such as SE37 or SE38.

Function Group: C104
Program Name: SAPLC104
Main Program: SAPLC104
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function C104_HANDLE_SUBS_OKCODE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'C104_HANDLE_SUBS_OKCODE'"NOTRANSL: EHS: Okcode Verarbeitung vom Subscreen
EXPORTING
I_OKCODE = "Screens, Function Code That Triggered PAI
* I_TABREG = "Title Element

IMPORTING
E_OKCODE = "
E_FLG_CHANGED = "
.



IMPORTING Parameters details for C104_HANDLE_SUBS_OKCODE

I_OKCODE - Screens, Function Code That Triggered PAI

Data type: ESP1_OKCODE_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

I_TABREG - Title Element

Data type: RCGTSDEF-REGISTER_KEY
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for C104_HANDLE_SUBS_OKCODE

E_OKCODE -

Data type: ESP1_OKCODE_TYPE
Optional: No
Call by Reference: Yes

E_FLG_CHANGED -

Data type: ESP1_BOOLEAN
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for C104_HANDLE_SUBS_OKCODE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_e_okcode  TYPE ESP1_OKCODE_TYPE, "   
lv_i_okcode  TYPE ESP1_OKCODE_TYPE, "   
lv_i_tabreg  TYPE RCGTSDEF-REGISTER_KEY, "   
lv_e_flg_changed  TYPE ESP1_BOOLEAN. "   

  CALL FUNCTION 'C104_HANDLE_SUBS_OKCODE'  "NOTRANSL: EHS: Okcode Verarbeitung vom Subscreen
    EXPORTING
         I_OKCODE = lv_i_okcode
         I_TABREG = lv_i_tabreg
    IMPORTING
         E_OKCODE = lv_e_okcode
         E_FLG_CHANGED = lv_e_flg_changed
. " C104_HANDLE_SUBS_OKCODE




ABAP code using 7.40 inline data declarations to call FM C104_HANDLE_SUBS_OKCODE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
"SELECT single REGISTER_KEY FROM RCGTSDEF INTO @DATA(ld_i_tabreg).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!