SAP BDT_INSTANCE_ATTRIBUTES_SET Function Module for









BDT_INSTANCE_ATTRIBUTES_SET is a standard bdt instance attributes set 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 set FM, simply by entering the name BDT_INSTANCE_ATTRIBUTES_SET 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_SET 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_SET'"
  EXPORTING
*  IV_HANDLE =  "ID of a BDT Instance
*  IV_VALDT =  "Validity date of changes
*  IV_APPLI_CALL =  "Application
*  IV_NO_DATA =  "
*  IV_XUPDTASK = '~' "
*  IV_XARCHIVE = '~' "
*  IV_XSAVE = '~' "Indicator: Business partner safeguards himself
*  IV_XCHECK_ONLY = ' ' "
*  IV_XRECOM = ' ' "
*  IV_XCHDOC = 'X' "
*  IV_XEXTRA_SCRSEQ_POPUP = ' ' "
*  IV_OBJID = GC_NODATA_STND "General ID (key) of a BDT application object
*  IV_XLEAVE_SCRSEQ_LASTSCR = 'X' "
*  IV_AKTYP =  "Activity Category
*  IV_ACTION =  "Step
*  IV_MESSAGE_MODE =  "Collective Status for Message Handler
*  IV_MESSAGE_MODE_DCHCK = '~' "
*  IV_DISPLAY_MODE =  "BDT Display Mode
*  IV_XPASS_REQFIELDS = '~' "
*  IV_FRGID = '~' "BDT: External Applications

TABLES
*  IT_RLTYP_SEL =  "
*  IT_RLTGR_SEL =  "
*  IT_APPLI_SEL =  "
*  IT_SICHT_SEL =  "
*  IT_SETID_SEL =  "

EXCEPTIONS
   HANDLE_NOT_FOUND = 1
.



IMPORTING Parameters details for BDT_INSTANCE_ATTRIBUTES_SET

IV_HANDLE - ID of a BDT Instance

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

IV_VALDT - Validity date of changes

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

IV_APPLI_CALL - Application

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

IV_NO_DATA -

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

IV_XUPDTASK -

Data type: BDT_BOOLE_T
Default: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_XARCHIVE -

Data type: BDT_BOOLE_T
Default: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_XSAVE - Indicator: Business partner safeguards himself

Data type: BU_XSAVE
Default: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_XCHECK_ONLY -

Data type: BOOLE_D
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_XRECOM -

Data type: BOOLE_D
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_XCHDOC -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_XEXTRA_SCRSEQ_POPUP -

Data type: BDT_EXTRA_SCRSEQ
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_OBJID - General ID (key) of a BDT application object

Data type: BDT_OBJID
Default: GC_NODATA_STND
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_XLEAVE_SCRSEQ_LASTSCR -

Data type: BDT_LEAVE_SCRSEQ
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_AKTYP - Activity Category

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

IV_ACTION - Step

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

IV_MESSAGE_MODE - Collective Status for Message Handler

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

IV_MESSAGE_MODE_DCHCK -

Data type: BU_COLSTAT
Default: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_DISPLAY_MODE - BDT Display Mode

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

IV_XPASS_REQFIELDS -

Data type: BOOLE_D
Default: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_FRGID - BDT: External Applications

Data type: BU_FRGID
Default: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BDT_INSTANCE_ATTRIBUTES_SET

IT_RLTYP_SEL -

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

IT_RLTGR_SEL -

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

IT_APPLI_SEL -

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

IT_SICHT_SEL -

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

IT_SETID_SEL -

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

EXCEPTIONS details

HANDLE_NOT_FOUND -

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

Copy and paste ABAP code example for BDT_INSTANCE_ATTRIBUTES_SET 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_iv_handle  TYPE BDT_INSTANCE_ID, "   
lt_it_rltyp_sel  TYPE STANDARD TABLE OF BUS0RLTYP, "   
lv_handle_not_found  TYPE BUS0RLTYP, "   
lv_iv_valdt  TYPE BU_VALSTR, "   
lv_iv_appli_call  TYPE BU_APPLI, "   
lv_iv_no_data  TYPE BDT_NO_DATA, "   
lv_iv_xupdtask  TYPE BDT_BOOLE_T, "   '~'
lv_iv_xarchive  TYPE BDT_BOOLE_T, "   '~'
lv_iv_xsave  TYPE BU_XSAVE, "   '~'
lv_iv_xcheck_only  TYPE BOOLE_D, "   ' '
lv_iv_xrecom  TYPE BOOLE_D, "   ' '
lv_iv_xchdoc  TYPE BOOLE_D, "   'X'
lv_iv_xextra_scrseq_popup  TYPE BDT_EXTRA_SCRSEQ, "   ' '
lv_iv_objid  TYPE BDT_OBJID, "   GC_NODATA_STND
lt_it_rltgr_sel  TYPE STANDARD TABLE OF BUS0RLTGR, "   
lv_iv_xleave_scrseq_lastscr  TYPE BDT_LEAVE_SCRSEQ, "   'X'
lv_iv_aktyp  TYPE BU_AKTYP, "   
lt_it_appli_sel  TYPE STANDARD TABLE OF BUS0APPLI, "   
lv_iv_action  TYPE BU_ACTION_TBZ0M, "   
lt_it_sicht_sel  TYPE STANDARD TABLE OF BUS0SICHT, "   
lt_it_setid_sel  TYPE STANDARD TABLE OF BUS0SETID, "   
lv_iv_message_mode  TYPE BU_COLSTAT, "   
lv_iv_message_mode_dchck  TYPE BU_COLSTAT, "   '~'
lv_iv_display_mode  TYPE BDT_DISPLAY_MODE, "   
lv_iv_xpass_reqfields  TYPE BOOLE_D, "   '~'
lv_iv_frgid  TYPE BU_FRGID. "   '~'

  CALL FUNCTION 'BDT_INSTANCE_ATTRIBUTES_SET'  "
    EXPORTING
         IV_HANDLE = lv_iv_handle
         IV_VALDT = lv_iv_valdt
         IV_APPLI_CALL = lv_iv_appli_call
         IV_NO_DATA = lv_iv_no_data
         IV_XUPDTASK = lv_iv_xupdtask
         IV_XARCHIVE = lv_iv_xarchive
         IV_XSAVE = lv_iv_xsave
         IV_XCHECK_ONLY = lv_iv_xcheck_only
         IV_XRECOM = lv_iv_xrecom
         IV_XCHDOC = lv_iv_xchdoc
         IV_XEXTRA_SCRSEQ_POPUP = lv_iv_xextra_scrseq_popup
         IV_OBJID = lv_iv_objid
         IV_XLEAVE_SCRSEQ_LASTSCR = lv_iv_xleave_scrseq_lastscr
         IV_AKTYP = lv_iv_aktyp
         IV_ACTION = lv_iv_action
         IV_MESSAGE_MODE = lv_iv_message_mode
         IV_MESSAGE_MODE_DCHCK = lv_iv_message_mode_dchck
         IV_DISPLAY_MODE = lv_iv_display_mode
         IV_XPASS_REQFIELDS = lv_iv_xpass_reqfields
         IV_FRGID = lv_iv_frgid
    TABLES
         IT_RLTYP_SEL = lt_it_rltyp_sel
         IT_RLTGR_SEL = lt_it_rltgr_sel
         IT_APPLI_SEL = lt_it_appli_sel
         IT_SICHT_SEL = lt_it_sicht_sel
         IT_SETID_SEL = lt_it_setid_sel
    EXCEPTIONS
        HANDLE_NOT_FOUND = 1
. " BDT_INSTANCE_ATTRIBUTES_SET




ABAP code using 7.40 inline data declarations to call FM BDT_INSTANCE_ATTRIBUTES_SET

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_xupdtask) = '~'.
 
DATA(ld_iv_xarchive) = '~'.
 
DATA(ld_iv_xsave) = '~'.
 
DATA(ld_iv_xcheck_only) = ' '.
 
DATA(ld_iv_xrecom) = ' '.
 
DATA(ld_iv_xchdoc) = 'X'.
 
DATA(ld_iv_xextra_scrseq_popup) = ' '.
 
DATA(ld_iv_objid) = GC_NODATA_STND.
 
 
DATA(ld_iv_xleave_scrseq_lastscr) = 'X'.
 
 
 
 
 
 
 
DATA(ld_iv_message_mode_dchck) = '~'.
 
 
DATA(ld_iv_xpass_reqfields) = '~'.
 
DATA(ld_iv_frgid) = '~'.
 


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!