SAP BDT_INSTANCE_ATTRIBUTES_GET Function Module for
BDT_INSTANCE_ATTRIBUTES_GET is a standard bdt instance attributes get 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 instance attributes get FM, simply by entering the name BDT_INSTANCE_ATTRIBUTES_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUSS
Program Name: SAPLBUSS
Main Program: SAPLBUSS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BDT_INSTANCE_ATTRIBUTES_GET 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_INSTANCE_ATTRIBUTES_GET'".
EXPORTING
* IV_HANDLE = "ID of a BDT Instance
IMPORTING
EV_OBJAP = "BDT: Application Object
EV_HANDLE_SUPER = "
EV_DISPLAY_MODE = "BDT Display Mode
EV_XPASS_REQFIELDS = "
EV_XFRGN = "
EV_FRGID = "
EV_VALDT = "Validity date for business partner data
EV_INSTANCE = "Data for BDT Instance
EV_FCODE = "
EV_FCODE_CLASSIC = "
EV_CRSFIELD = "
EV_OBJID = "General ID (key) of a BDT application object
EV_CRSLINE = "
EV_XUPDTASK = "
EV_XARCHIVE = "
EV_XSAVE = "Indicator: Business partner safeguards himself
EV_NODATA = "BDT: No data character
EV_XCHECK_ONLY = "Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')
EV_XCHDOC = "
EV_XRECOM = "
EV_XEXTRA_SCRSEQ_POPUP = "
EV_XLEAVE_SCRSEQ_LASTSCR = "
EV_AKTYP = "Activity Category
EV_ACTION = "Step
EV_MESSAGE_MODE = "Collective Status for Message Handler
EV_MESSAGE_MODE_DCHCK = "
EV_XPRIMARY = "
EV_HANDLE_PRIMARY = "
EV_XSUPER = "
TABLES
* ET_RLTYP = "
* ET_RLTYP_SEL = "
* ET_RLTGR_SEL = "CBP: BP Role Groupings
* ET_TBZ3D = "BDT Sections: Texts
EXCEPTIONS
HANDLE_NOT_FOUND = 1
IMPORTING Parameters details for BDT_INSTANCE_ATTRIBUTES_GET
IV_HANDLE - ID of a BDT Instance
Data type: BDT_INSTANCE_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BDT_INSTANCE_ATTRIBUTES_GET
EV_OBJAP - BDT: Application Object
Data type: BU_OBJAPOptional: No
Call by Reference: No ( called with pass by value option)
EV_HANDLE_SUPER -
Data type: BDT_INSTANCE_IDOptional: No
Call by Reference: No ( called with pass by value option)
EV_DISPLAY_MODE - BDT Display Mode
Data type: BDT_DISPLAY_MODEOptional: No
Call by Reference: No ( called with pass by value option)
EV_XPASS_REQFIELDS -
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
EV_XFRGN -
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
EV_FRGID -
Data type: BU_FRGIDOptional: No
Call by Reference: No ( called with pass by value option)
EV_VALDT - Validity date for business partner data
Data type: BU_VALSTROptional: No
Call by Reference: No ( called with pass by value option)
EV_INSTANCE - Data for BDT Instance
Data type: BDT_INSTANCEOptional: No
Call by Reference: No ( called with pass by value option)
EV_FCODE -
Data type: SYUCOMMOptional: No
Call by Reference: No ( called with pass by value option)
EV_FCODE_CLASSIC -
Data type: SYUCOMMOptional: No
Call by Reference: No ( called with pass by value option)
EV_CRSFIELD -
Data type: BU_TBFLDOptional: No
Call by Reference: No ( called with pass by value option)
EV_OBJID - General ID (key) of a BDT application object
Data type: BDT_OBJIDOptional: No
Call by Reference: No ( called with pass by value option)
EV_CRSLINE -
Data type: SYLILLIOptional: No
Call by Reference: No ( called with pass by value option)
EV_XUPDTASK -
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
EV_XARCHIVE -
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
EV_XSAVE - Indicator: Business partner safeguards himself
Data type: BU_XSAVEOptional: No
Call by Reference: No ( called with pass by value option)
EV_NODATA - BDT: No data character
Data type: BDT_NO_DATAOptional: No
Call by Reference: No ( called with pass by value option)
EV_XCHECK_ONLY - Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
EV_XCHDOC -
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
EV_XRECOM -
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
EV_XEXTRA_SCRSEQ_POPUP -
Data type: BDT_EXTRA_SCRSEQOptional: No
Call by Reference: No ( called with pass by value option)
EV_XLEAVE_SCRSEQ_LASTSCR -
Data type: BDT_LEAVE_SCRSEQOptional: No
Call by Reference: No ( called with pass by value option)
EV_AKTYP - Activity Category
Data type: BU_AKTYPOptional: No
Call by Reference: No ( called with pass by value option)
EV_ACTION - Step
Data type: BU_ACTION_TBZ0MOptional: No
Call by Reference: No ( called with pass by value option)
EV_MESSAGE_MODE - Collective Status for Message Handler
Data type: BU_COLSTATOptional: No
Call by Reference: No ( called with pass by value option)
EV_MESSAGE_MODE_DCHCK -
Data type: BU_COLSTATOptional: No
Call by Reference: No ( called with pass by value option)
EV_XPRIMARY -
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
EV_HANDLE_PRIMARY -
Data type: BDT_INSTANCE_IDOptional: No
Call by Reference: No ( called with pass by value option)
EV_XSUPER -
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BDT_INSTANCE_ATTRIBUTES_GET
ET_RLTYP -
Data type: BUS0RLTYPOptional: Yes
Call by Reference: Yes
ET_RLTYP_SEL -
Data type: BUS0RLTYPOptional: Yes
Call by Reference: Yes
ET_RLTGR_SEL - CBP: BP Role Groupings
Data type: BUS0RLTGROptional: Yes
Call by Reference: Yes
ET_TBZ3D - BDT Sections: Texts
Data type: TBZ3DOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
HANDLE_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BDT_INSTANCE_ATTRIBUTES_GET 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: | ||||
| lt_et_rltyp | TYPE STANDARD TABLE OF BUS0RLTYP, " | |||
| lv_ev_objap | TYPE BU_OBJAP, " | |||
| lv_iv_handle | TYPE BDT_INSTANCE_ID, " | |||
| lv_handle_not_found | TYPE BDT_INSTANCE_ID, " | |||
| lv_ev_handle_super | TYPE BDT_INSTANCE_ID, " | |||
| lv_ev_display_mode | TYPE BDT_DISPLAY_MODE, " | |||
| lv_ev_xpass_reqfields | TYPE BOOLE_D, " | |||
| lv_ev_xfrgn | TYPE BOOLE_D, " | |||
| lv_ev_frgid | TYPE BU_FRGID, " | |||
| lv_ev_valdt | TYPE BU_VALSTR, " | |||
| lv_ev_instance | TYPE BDT_INSTANCE, " | |||
| lv_ev_fcode | TYPE SYUCOMM, " | |||
| lv_ev_fcode_classic | TYPE SYUCOMM, " | |||
| lv_ev_crsfield | TYPE BU_TBFLD, " | |||
| lv_ev_objid | TYPE BDT_OBJID, " | |||
| lt_et_rltyp_sel | TYPE STANDARD TABLE OF BUS0RLTYP, " | |||
| lv_ev_crsline | TYPE SYLILLI, " | |||
| lv_ev_xupdtask | TYPE BOOLE_D, " | |||
| lv_ev_xarchive | TYPE BOOLE_D, " | |||
| lv_ev_xsave | TYPE BU_XSAVE, " | |||
| lv_ev_nodata | TYPE BDT_NO_DATA, " | |||
| lv_ev_xcheck_only | TYPE BOOLE_D, " | |||
| lv_ev_xchdoc | TYPE BOOLE_D, " | |||
| lv_ev_xrecom | TYPE BOOLE_D, " | |||
| lv_ev_xextra_scrseq_popup | TYPE BDT_EXTRA_SCRSEQ, " | |||
| lv_ev_xleave_scrseq_lastscr | TYPE BDT_LEAVE_SCRSEQ, " | |||
| lv_ev_aktyp | TYPE BU_AKTYP, " | |||
| lt_et_rltgr_sel | TYPE STANDARD TABLE OF BUS0RLTGR, " | |||
| lt_et_tbz3d | TYPE STANDARD TABLE OF TBZ3D, " | |||
| lv_ev_action | TYPE BU_ACTION_TBZ0M, " | |||
| lv_ev_message_mode | TYPE BU_COLSTAT, " | |||
| lv_ev_message_mode_dchck | TYPE BU_COLSTAT, " | |||
| lv_ev_xprimary | TYPE BOOLE_D, " | |||
| lv_ev_handle_primary | TYPE BDT_INSTANCE_ID, " | |||
| lv_ev_xsuper | TYPE BOOLE_D. " |
|   CALL FUNCTION 'BDT_INSTANCE_ATTRIBUTES_GET' " |
| EXPORTING | ||
| IV_HANDLE | = lv_iv_handle | |
| IMPORTING | ||
| EV_OBJAP | = lv_ev_objap | |
| EV_HANDLE_SUPER | = lv_ev_handle_super | |
| EV_DISPLAY_MODE | = lv_ev_display_mode | |
| EV_XPASS_REQFIELDS | = lv_ev_xpass_reqfields | |
| EV_XFRGN | = lv_ev_xfrgn | |
| EV_FRGID | = lv_ev_frgid | |
| EV_VALDT | = lv_ev_valdt | |
| EV_INSTANCE | = lv_ev_instance | |
| EV_FCODE | = lv_ev_fcode | |
| EV_FCODE_CLASSIC | = lv_ev_fcode_classic | |
| EV_CRSFIELD | = lv_ev_crsfield | |
| EV_OBJID | = lv_ev_objid | |
| EV_CRSLINE | = lv_ev_crsline | |
| EV_XUPDTASK | = lv_ev_xupdtask | |
| EV_XARCHIVE | = lv_ev_xarchive | |
| EV_XSAVE | = lv_ev_xsave | |
| EV_NODATA | = lv_ev_nodata | |
| EV_XCHECK_ONLY | = lv_ev_xcheck_only | |
| EV_XCHDOC | = lv_ev_xchdoc | |
| EV_XRECOM | = lv_ev_xrecom | |
| EV_XEXTRA_SCRSEQ_POPUP | = lv_ev_xextra_scrseq_popup | |
| EV_XLEAVE_SCRSEQ_LASTSCR | = lv_ev_xleave_scrseq_lastscr | |
| EV_AKTYP | = lv_ev_aktyp | |
| EV_ACTION | = lv_ev_action | |
| EV_MESSAGE_MODE | = lv_ev_message_mode | |
| EV_MESSAGE_MODE_DCHCK | = lv_ev_message_mode_dchck | |
| EV_XPRIMARY | = lv_ev_xprimary | |
| EV_HANDLE_PRIMARY | = lv_ev_handle_primary | |
| EV_XSUPER | = lv_ev_xsuper | |
| TABLES | ||
| ET_RLTYP | = lt_et_rltyp | |
| ET_RLTYP_SEL | = lt_et_rltyp_sel | |
| ET_RLTGR_SEL | = lt_et_rltgr_sel | |
| ET_TBZ3D | = lt_et_tbz3d | |
| EXCEPTIONS | ||
| HANDLE_NOT_FOUND = 1 | ||
| . " BDT_INSTANCE_ATTRIBUTES_GET | ||
ABAP code using 7.40 inline data declarations to call FM BDT_INSTANCE_ATTRIBUTES_GET
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.Search for further information about these or an SAP related objects