BSP_DLC_OTYPE_GET SAP Function module - Search Help for Object Type

BSP_DLC_OTYPE_GET 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 BSP_DLC_OTYPE_GET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BSP_DLC_OTYPE_SHELP
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM BSP_DLC_OTYPE_GET - BSP DLC OTYPE GET

CALL FUNCTION 'BSP_DLC_OTYPE_GET' "Search Help for Object Type
* EXPORTING
*   iv_object_type =            " bsp_dlc_object_type  UI Object Type
*   iv_langu = SY-LANGU         " sylangu       Language Key of Current Text Environment
*   iv_source = BSPCD_SOURCE_CUST_SAP  " bsp_dlc_design_layer_source  Source of Design Layer Data: Customer / SAP / Both
  IMPORTING
    es_object_type_data =       " bsp_dlcs_object_type_data  Object type data
    et_object_type_data =       " bsp_dlcs_object_type_data_t  Object types data
  EXCEPTIONS
    NOT_FOUND = 1               "               Object Type not found
    .  "  BSP_DLC_OTYPE_GET

ABAP code example for Function Module BSP_DLC_OTYPE_GET

The ABAP code below is a full code listing to execute function module BSP_DLC_OTYPE_GET 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:
ld_es_object_type_data  
 
 TYPE BSP_DLCS_OBJECT_TYPE_DATA
,
ld_et_object_type_data  
 
 TYPE BSP_DLCS_OBJECT_TYPE_DATA_T
.


DATA(ld_iv_object_type) = 'Check type of data required'.

DATA(ld_iv_langu) = 'Check type of data required'.

DATA(ld_iv_source) = 'Check type of data required'.
.

CALL FUNCTION 'BSP_DLC_OTYPE_GET'
* EXPORTING
*   iv_object_type =             ld_iv_object_type
*   iv_langu =                   ld_iv_langu
*   iv_source =                  ld_iv_source
  IMPORTING
    es_object_type_data =        ld_es_object_type_data
    et_object_type_data =        ld_et_object_type_data
  EXCEPTIONS
    NOT_FOUND =                  1
    .  "  BSP_DLC_OTYPE_GET

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_es_object_type_data
 
 TYPE BSP_DLCS_OBJECT_TYPE_DATA ,
ld_iv_object_type
 
 TYPE BSP_DLC_OBJECT_TYPE ,
ld_et_object_type_data
 
 TYPE BSP_DLCS_OBJECT_TYPE_DATA_T ,
ld_iv_langu
 
 TYPE SYLANGU ,
ld_iv_source
 
 TYPE BSP_DLC_DESIGN_LAYER_SOURCE .


ld_iv_object_type = 'Check type of data required'.
ld_iv_langu = 'Check type of data required'.
ld_iv_source = 'Check type of data required'.