BDT_TBZ3T_GET_SINGLE SAP Function module

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

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

Pattern for FM BDT_TBZ3T_GET_SINGLE - BDT TBZ3T GET SINGLE

CALL FUNCTION 'BDT_TBZ3T_GET_SINGLE' "
  EXPORTING
*   iv_client = SY-MANDT        " mandt         Client
*   iv_spras = SY-LANGU         " spras         Language Key
    iv_objap =                  " bu_objap      BDT: Application Object
    iv_varnr =                  " bu_varnr      BDT: Screen Sequence
  IMPORTING
    ev_tbz3t =                  " tbz3t         BDT Screen Sequence Variants: Texts
  EXCEPTIONS
    NOT_FOUND = 1               "               No Entry Found
    .  "  BDT_TBZ3T_GET_SINGLE

ABAP code example for Function Module BDT_TBZ3T_GET_SINGLE

The ABAP code below is a full code listing to execute function module BDT_TBZ3T_GET_SINGLE 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_ev_tbz3t  
 
 TYPE TBZ3T
.


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

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

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

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

CALL FUNCTION 'BDT_TBZ3T_GET_SINGLE'
  EXPORTING
*   iv_client =                  ld_iv_client
*   iv_spras =                   ld_iv_spras
    iv_objap =                   ld_iv_objap
    iv_varnr =                   ld_iv_varnr
  IMPORTING
    ev_tbz3t =                   ld_ev_tbz3t
  EXCEPTIONS
    NOT_FOUND =                  1
    .  "  BDT_TBZ3T_GET_SINGLE

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_ev_tbz3t
 
 TYPE TBZ3T ,
ld_iv_client
 
 TYPE MANDT ,
ld_iv_spras
 
 TYPE SPRAS ,
ld_iv_objap
 
 TYPE BU_OBJAP ,
ld_iv_varnr
 
 TYPE BU_VARNR .


ld_iv_client = 'Check type of data required'.
ld_iv_spras = 'Check type of data required'.
ld_iv_objap = 'Check type of data required'.
ld_iv_varnr = 'Check type of data required'.