SAP Function Modules

SDU_ENTITY_FETCH SAP Function module







SDU_ENTITY_FETCH is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name SDU_ENTITY_FETCH into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SDU2
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM SDU_ENTITY_FETCH - SDU ENTITY FETCH





CALL FUNCTION 'SDU_ENTITY_FETCH' "
* EXPORTING
*   as4local = 'A'              " dm02l-as4local  Validity
*   dmoid = SPACE               " dm40l-dmoid   Data model name
*   entity = '*'                " dm02l-entid   Entity type
*   langu = SY-LANGU            " dm02t-sprache  Language
*   longtxt = '*'               " dm02t-langbez  Long text, if selection via long text required
*   sel_mode = SPACE            "               Del. flag ' '-all, L-deleted only, U-not deleted
  TABLES
    entities =                  " dm02v         Table with entity types that were found
  EXCEPTIONS
    NOT_FOUND = 1               "
    .  "  SDU_ENTITY_FETCH

ABAP code example for Function Module SDU_ENTITY_FETCH





The ABAP code below is a full code listing to execute function module SDU_ENTITY_FETCH including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_entities  TYPE STANDARD TABLE OF DM02V,"TABLES PARAM
wa_entities  LIKE LINE OF it_entities .


SELECT single AS4LOCAL
FROM DM02L
INTO @DATA(ld_as4local).


SELECT single DMOID
FROM DM40L
INTO @DATA(ld_dmoid).


SELECT single ENTID
FROM DM02L
INTO @DATA(ld_entity).


SELECT single SPRACHE
FROM DM02T
INTO @DATA(ld_langu).


SELECT single LANGBEZ
FROM DM02T
INTO @DATA(ld_longtxt).

DATA(ld_sel_mode) = 'some text here'.

"populate fields of struture and append to itab
append wa_entities to it_entities. . CALL FUNCTION 'SDU_ENTITY_FETCH' * EXPORTING * as4local = ld_as4local * dmoid = ld_dmoid * entity = ld_entity * langu = ld_langu * longtxt = ld_longtxt * sel_mode = ld_sel_mode TABLES entities = it_entities EXCEPTIONS NOT_FOUND = 1 . " SDU_ENTITY_FETCH
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_as4local  TYPE DM02L-AS4LOCAL ,
it_entities  TYPE STANDARD TABLE OF DM02V ,
wa_entities  LIKE LINE OF it_entities,
ld_dmoid  TYPE DM40L-DMOID ,
ld_entity  TYPE DM02L-ENTID ,
ld_langu  TYPE DM02T-SPRACHE ,
ld_longtxt  TYPE DM02T-LANGBEZ ,
ld_sel_mode  TYPE STRING .


SELECT single AS4LOCAL
FROM DM02L
INTO ld_as4local.


"populate fields of struture and append to itab
append wa_entities to it_entities.

SELECT single DMOID
FROM DM40L
INTO ld_dmoid.


SELECT single ENTID
FROM DM02L
INTO ld_entity.


SELECT single SPRACHE
FROM DM02T
INTO ld_langu.


SELECT single LANGBEZ
FROM DM02T
INTO ld_longtxt.

ld_sel_mode = 'some text here'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name SDU_ENTITY_FETCH or its description.