SAP /SEHS/DG16_OK_CODE_FETCH Function Module for Transfer OK Code from Other Function Group









/SEHS/DG16_OK_CODE_FETCH is a standard /sehs/dg16 ok code fetch SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Transfer OK Code from Other Function Group 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 /sehs/dg16 ok code fetch FM, simply by entering the name /SEHS/DG16_OK_CODE_FETCH into the relevant SAP transaction such as SE37 or SE38.

Function Group: /SEHS/DG16
Program Name: /SEHS/SAPLDG16
Main Program: /SEHS/SAPLDG16
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function /SEHS/DG16_OK_CODE_FETCH 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 '/SEHS/DG16_OK_CODE_FETCH'"Transfer OK Code from Other Function Group
EXPORTING
I_OKCODE = "ok_code
.



IMPORTING Parameters details for /SEHS/DG16_OK_CODE_FETCH

I_OKCODE - ok_code

Data type: SY-TCODE
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for /SEHS/DG16_OK_CODE_FETCH 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_i_okcode  TYPE SY-TCODE. "   

  CALL FUNCTION '/SEHS/DG16_OK_CODE_FETCH'  "Transfer OK Code from Other Function Group
    EXPORTING
         I_OKCODE = lv_i_okcode
. " /SEHS/DG16_OK_CODE_FETCH




ABAP code using 7.40 inline data declarations to call FM /SEHS/DG16_OK_CODE_FETCH

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 TCODE FROM SY INTO @DATA(ld_i_okcode).
 


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!