SAP BDT_TBZ3L_GET_SINGLE Function Module for









BDT_TBZ3L_GET_SINGLE is a standard bdt tbz3l get single SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bdt tbz3l get single FM, simply by entering the name BDT_TBZ3L_GET_SINGLE into the relevant SAP transaction such as SE37 or SE38.

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



Function BDT_TBZ3L_GET_SINGLE 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 'BDT_TBZ3L_GET_SINGLE'"
EXPORTING
* IV_CLIENT = SY-MANDT "Client
IV_OBJAP = "BDT: Application Object
IV_VARTP = "BDT: Screen Sequence Category

IMPORTING
EV_TBZ3L = "BDT-Screen Sequence Categories

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for BDT_TBZ3L_GET_SINGLE

IV_CLIENT - Client

Data type: MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: Yes

IV_OBJAP - BDT: Application Object

Data type: BU_OBJAP
Optional: No
Call by Reference: Yes

IV_VARTP - BDT: Screen Sequence Category

Data type: BU_VARTP
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for BDT_TBZ3L_GET_SINGLE

EV_TBZ3L - BDT-Screen Sequence Categories

Data type: TBZ3L
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND - No Entry Found

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

Copy and paste ABAP code example for BDT_TBZ3L_GET_SINGLE 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_ev_tbz3l  TYPE TBZ3L, "   
lv_iv_client  TYPE MANDT, "   SY-MANDT
lv_not_found  TYPE MANDT, "   
lv_iv_objap  TYPE BU_OBJAP, "   
lv_iv_vartp  TYPE BU_VARTP. "   

  CALL FUNCTION 'BDT_TBZ3L_GET_SINGLE'  "
    EXPORTING
         IV_CLIENT = lv_iv_client
         IV_OBJAP = lv_iv_objap
         IV_VARTP = lv_iv_vartp
    IMPORTING
         EV_TBZ3L = lv_ev_tbz3l
    EXCEPTIONS
        NOT_FOUND = 1
. " BDT_TBZ3L_GET_SINGLE




ABAP code using 7.40 inline data declarations to call FM BDT_TBZ3L_GET_SINGLE

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.

 
DATA(ld_iv_client) = SY-MANDT.
 
 
 
 


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!