SAP SDU_RELATION_FETCH Function Module for UDM get several relationships









SDU_RELATION_FETCH is a standard sdu relation 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 UDM get several relationships 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 relation fetch FM, simply by entering the name SDU_RELATION_FETCH into the relevant SAP transaction such as SE37 or SE38.

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



Function SDU_RELATION_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 'SDU_RELATION_FETCH'"UDM get several relationships
  EXPORTING
*  AS4LOCAL = 'A' "Validity
   EBROLNR =  "Relationship role
   ENTIDFROM =  "Entity type for
   ENTIDTO =  "Entity type to
*  FLG_LONGTXT = ' ' "which entity short name is read
*  LANGU = SY-LANGU "Language
*  SEL_MODE = ' ' "Del. flag ' ' all; L=deleted only, U=not deleted
*  FLG_TXTTYPE = 1 "Short text type

TABLES
   RELATIONS =  "Relationships

EXCEPTIONS
   NOT_FOUND = 1
.



IMPORTING Parameters details for SDU_RELATION_FETCH

AS4LOCAL - Validity

Data type: DM42S-AS4LOCAL
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EBROLNR - Relationship role

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

ENTIDFROM - Entity type for

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

ENTIDTO - Entity type to

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

FLG_LONGTXT - which entity short name is read

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

LANGU - Language

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

SEL_MODE - Del. flag ' ' all; L=deleted only, U=not deleted

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

FLG_TXTTYPE - Short text type

Data type: DMCTL-TXTTYPE
Default: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for SDU_RELATION_FETCH

RELATIONS - Relationships

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

EXCEPTIONS details

NOT_FOUND - Relationship not found

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

Copy and paste ABAP code example for SDU_RELATION_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_as4local  TYPE DM42S-AS4LOCAL, "   'A'
lv_not_found  TYPE DM42S, "   
lt_relations  TYPE STANDARD TABLE OF DM42I, "   
lv_ebrolnr  TYPE DM42S-EBROLNR, "   
lv_entidfrom  TYPE DM42S-ENTIDFROM, "   
lv_entidto  TYPE DM42S-ENTIDTO, "   
lv_flg_longtxt  TYPE DM42S, "   SPACE
lv_langu  TYPE DM02T-SPRACHE, "   SY-LANGU
lv_sel_mode  TYPE DM02T, "   SPACE
lv_flg_txttype  TYPE DMCTL-TXTTYPE. "   1

  CALL FUNCTION 'SDU_RELATION_FETCH'  "UDM get several relationships
    EXPORTING
         AS4LOCAL = lv_as4local
         EBROLNR = lv_ebrolnr
         ENTIDFROM = lv_entidfrom
         ENTIDTO = lv_entidto
         FLG_LONGTXT = lv_flg_longtxt
         LANGU = lv_langu
         SEL_MODE = lv_sel_mode
         FLG_TXTTYPE = lv_flg_txttype
    TABLES
         RELATIONS = lt_relations
    EXCEPTIONS
        NOT_FOUND = 1
. " SDU_RELATION_FETCH




ABAP code using 7.40 inline data declarations to call FM SDU_RELATION_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 AS4LOCAL FROM DM42S INTO @DATA(ld_as4local).
DATA(ld_as4local) = 'A'.
 
 
 
"SELECT single EBROLNR FROM DM42S INTO @DATA(ld_ebrolnr).
 
"SELECT single ENTIDFROM FROM DM42S INTO @DATA(ld_entidfrom).
 
"SELECT single ENTIDTO FROM DM42S INTO @DATA(ld_entidto).
 
DATA(ld_flg_longtxt) = ' '.
 
"SELECT single SPRACHE FROM DM02T INTO @DATA(ld_langu).
DATA(ld_langu) = SY-LANGU.
 
DATA(ld_sel_mode) = ' '.
 
"SELECT single TXTTYPE FROM DMCTL INTO @DATA(ld_flg_txttype).
DATA(ld_flg_txttype) = 1.
 


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!