SAP SDU_SPECIAL_FETCH Function Module for UDM get several specializations









SDU_SPECIAL_FETCH is a standard sdu special 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 specializations 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 special fetch FM, simply by entering the name SDU_SPECIAL_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_SPECIAL_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_SPECIAL_FETCH'"UDM get several specializations
  EXPORTING
*  AS4LOCAL = 'A' "Validity
   ENTIDFROM =  "Entity type from
   ENTIDTO =  "Entity type to
*  FLG_LONGTXT = ' ' "Flag: Read in long text
*  LANGU = SY-LANGU "Language
*  SEL_MODE = ' ' "Del. flag: ' '=all, L=deleted only, U=not deleted
*  SPECID = '*' "Specializ. category

TABLES
   SPECIALS =  "Specializations

EXCEPTIONS
   NOT_FOUND = 1
.



IMPORTING Parameters details for SDU_SPECIAL_FETCH

AS4LOCAL - Validity

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

ENTIDFROM - Entity type from

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

ENTIDTO - Entity type to

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

FLG_LONGTXT - Flag: Read in long text

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)

SPECID - Specializ. category

Data type: DM46S-SPEZID
Default: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for SDU_SPECIAL_FETCH

SPECIALS - Specializations

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

EXCEPTIONS details

NOT_FOUND - Specializations not found

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

Copy and paste ABAP code example for SDU_SPECIAL_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 DM46S-AS4LOCAL, "   'A'
lt_specials  TYPE STANDARD TABLE OF DM46I, "   
lv_not_found  TYPE DM46I, "   
lv_entidfrom  TYPE DM46S-ENTIDFROM, "   
lv_entidto  TYPE DM46S-ENTIDTO, "   
lv_flg_longtxt  TYPE DM46S, "   SPACE
lv_langu  TYPE DM02T-SPRACHE, "   SY-LANGU
lv_sel_mode  TYPE DM02T, "   SPACE
lv_specid  TYPE DM46S-SPEZID. "   '*'

  CALL FUNCTION 'SDU_SPECIAL_FETCH'  "UDM get several specializations
    EXPORTING
         AS4LOCAL = lv_as4local
         ENTIDFROM = lv_entidfrom
         ENTIDTO = lv_entidto
         FLG_LONGTXT = lv_flg_longtxt
         LANGU = lv_langu
         SEL_MODE = lv_sel_mode
         SPECID = lv_specid
    TABLES
         SPECIALS = lt_specials
    EXCEPTIONS
        NOT_FOUND = 1
. " SDU_SPECIAL_FETCH




ABAP code using 7.40 inline data declarations to call FM SDU_SPECIAL_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 DM46S INTO @DATA(ld_as4local).
DATA(ld_as4local) = 'A'.
 
 
 
"SELECT single ENTIDFROM FROM DM46S INTO @DATA(ld_entidfrom).
 
"SELECT single ENTIDTO FROM DM46S 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 SPEZID FROM DM46S INTO @DATA(ld_specid).
DATA(ld_specid) = '*'.
 


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!