SAP C10R_TABSCREEN_OKCODE Function Module for NOTRANSL: EHS: Behandlung von Ok-Codes für Beförderungszulassung
C10R_TABSCREEN_OKCODE is a standard c10r tabscreen 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: Behandlung von Ok-Codes für Beförderungszulassung 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 c10r tabscreen okcode FM, simply by entering the name C10R_TABSCREEN_OKCODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: C10R
Program Name: SAPLC10R
Main Program: SAPLC10R
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function C10R_TABSCREEN_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 'C10R_TABSCREEN_OKCODE'"NOTRANSL: EHS: Behandlung von Ok-Codes für Beförderungszulassung.
EXPORTING
I_OKCODE = "
IMPORTING
E_OKCODE = "
IMPORTING Parameters details for C10R_TABSCREEN_OKCODE
I_OKCODE -
Data type: ESP1_OKCODE_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for C10R_TABSCREEN_OKCODE
E_OKCODE -
Data type: ESP1_OKCODE_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for C10R_TABSCREEN_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. " |
  CALL FUNCTION 'C10R_TABSCREEN_OKCODE' "NOTRANSL: EHS: Behandlung von Ok-Codes für Beförderungszulassung |
EXPORTING | ||
I_OKCODE | = lv_i_okcode | |
IMPORTING | ||
E_OKCODE | = lv_e_okcode | |
. " C10R_TABSCREEN_OKCODE |
ABAP code using 7.40 inline data declarations to call FM C10R_TABSCREEN_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.Search for further information about these or an SAP related objects