SAP SDU_DOCU_GET Function Module for EDM get documentation









SDU_DOCU_GET is a standard sdu docu get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for EDM get documentation 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 sdu docu get FM, simply by entering the name SDU_DOCU_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function SDU_DOCU_GET 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 'SDU_DOCU_GET'"EDM get documentation
  EXPORTING
*  KEY1 = ' ' "Key 1 doc. object
*  LANGU = SY-LANGU "Language
*  OBJ_ID = ' ' "EDM object ID
*  KEY2 = ' ' "Key 2
*  KEY3 = ' ' "Key 3
*  KEY4 = ' ' "
*  KEY5 = ' ' "
*  KEY6 = ' ' "
*  KEY7 = ' ' "
*  KEY8 = ' ' "
*  KEY9 = ' ' "

 IMPORTING
   HEAD =  "Doc. header
   GET_TYP =  "
   GET_STATE =  "

TABLES
   LINES =  "Doc. lines

EXCEPTIONS
   NOT_FOUND = 1    WRONG_OBJ_ID = 2
.



IMPORTING Parameters details for SDU_DOCU_GET

KEY1 - Key 1 doc. object

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

LANGU - Language

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

OBJ_ID - EDM object ID

Data type: DMINF-FLG_ENTRY
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

KEY2 - Key 2

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

KEY3 - Key 3

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

KEY4 -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

KEY5 -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

KEY6 -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

KEY7 -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

KEY8 -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

KEY9 -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SDU_DOCU_GET

HEAD - Doc. header

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

GET_TYP -

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

GET_STATE -

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

TABLES Parameters details for SDU_DOCU_GET

LINES - Doc. lines

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

EXCEPTIONS details

NOT_FOUND - Documentation not found

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

WRONG_OBJ_ID -

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

Copy and paste ABAP code example for SDU_DOCU_GET 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_head  TYPE THEAD, "   
lv_key1  TYPE THEAD, "   SPACE
lt_lines  TYPE STANDARD TABLE OF TLINE, "   
lv_not_found  TYPE TLINE, "   
lv_langu  TYPE SY-LANGU, "   SY-LANGU
lv_obj_id  TYPE DMINF-FLG_ENTRY, "   SPACE
lv_key2  TYPE DMINF, "   SPACE
lv_get_typ  TYPE DOKIL-TYP, "   
lv_wrong_obj_id  TYPE DOKIL, "   
lv_key3  TYPE DOKIL, "   SPACE
lv_get_state  TYPE DOKIL-DOKSTATE, "   
lv_key4  TYPE DOKIL, "   SPACE
lv_key5  TYPE DOKIL, "   SPACE
lv_key6  TYPE DOKIL, "   SPACE
lv_key7  TYPE DOKIL, "   SPACE
lv_key8  TYPE DOKIL, "   SPACE
lv_key9  TYPE DOKIL. "   SPACE

  CALL FUNCTION 'SDU_DOCU_GET'  "EDM get documentation
    EXPORTING
         KEY1 = lv_key1
         LANGU = lv_langu
         OBJ_ID = lv_obj_id
         KEY2 = lv_key2
         KEY3 = lv_key3
         KEY4 = lv_key4
         KEY5 = lv_key5
         KEY6 = lv_key6
         KEY7 = lv_key7
         KEY8 = lv_key8
         KEY9 = lv_key9
    IMPORTING
         HEAD = lv_head
         GET_TYP = lv_get_typ
         GET_STATE = lv_get_state
    TABLES
         LINES = lt_lines
    EXCEPTIONS
        NOT_FOUND = 1
        WRONG_OBJ_ID = 2
. " SDU_DOCU_GET




ABAP code using 7.40 inline data declarations to call FM SDU_DOCU_GET

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.

 
DATA(ld_key1) = ' '.
 
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_langu).
DATA(ld_langu) = SY-LANGU.
 
"SELECT single FLG_ENTRY FROM DMINF INTO @DATA(ld_obj_id).
DATA(ld_obj_id) = ' '.
 
DATA(ld_key2) = ' '.
 
"SELECT single TYP FROM DOKIL INTO @DATA(ld_get_typ).
 
 
DATA(ld_key3) = ' '.
 
"SELECT single DOKSTATE FROM DOKIL INTO @DATA(ld_get_state).
 
DATA(ld_key4) = ' '.
 
DATA(ld_key5) = ' '.
 
DATA(ld_key6) = ' '.
 
DATA(ld_key7) = ' '.
 
DATA(ld_key8) = ' '.
 
DATA(ld_key9) = ' '.
 


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!