SAP DD_MX_TABL_DEP_ACT Function Module for DD: activation of tables with MULTIPLEX = 'D'









DD_MX_TABL_DEP_ACT is a standard dd mx tabl dep act SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DD: activation of tables with MULTIPLEX = 'D' processing and below is the pattern details for this FM, 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 dd mx tabl dep act FM, simply by entering the name DD_MX_TABL_DEP_ACT into the relevant SAP transaction such as SE37 or SE38.

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



Function DD_MX_TABL_DEP_ACT 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 'DD_MX_TABL_DEP_ACT'"DD: activation of tables with MULTIPLEX = 'D'
  EXPORTING
   MX_TABNAME =  "
   TABNAME =  "
*  ACT_MODE = 1 "
*  NTAB_PUTSTATE = 'A' "
*  AUTH_CHK = 'X' "
*  EXCOMMIT = 'X' "
*  UPGRMODE = ' ' "
*  SET_MX = 'X' "
*  PRID = 0 "

 IMPORTING
   ACT_RESULT =  "

EXCEPTIONS
   ILLEGAL_VALUE = 1
.



IMPORTING Parameters details for DD_MX_TABL_DEP_ACT

MX_TABNAME -

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

TABNAME -

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

ACT_MODE -

Data type: DDREFSTRUC-MODE
Default: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)

NTAB_PUTSTATE -

Data type: DDXTT-MODEFLAG
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

AUTH_CHK -

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

EXCOMMIT -

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

UPGRMODE -

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

SET_MX -

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

PRID -

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

EXPORTING Parameters details for DD_MX_TABL_DEP_ACT

ACT_RESULT -

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

EXCEPTIONS details

ILLEGAL_VALUE -

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

Copy and paste ABAP code example for DD_MX_TABL_DEP_ACT 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_act_result  TYPE SY-TABIX, "   
lv_mx_tabname  TYPE DD02V-TABNAME, "   
lv_illegal_value  TYPE DD02V, "   
lv_tabname  TYPE DD02V-TABNAME, "   
lv_act_mode  TYPE DDREFSTRUC-MODE, "   1
lv_ntab_putstate  TYPE DDXTT-MODEFLAG, "   'A'
lv_auth_chk  TYPE DDREFSTRUC-BOOL, "   'X'
lv_excommit  TYPE DCTABLACT-EXCOMMIT, "   'X'
lv_upgrmode  TYPE DCTABLACT-UPGRMODE, "   ' '
lv_set_mx  TYPE DDREFSTRUC-BOOL, "   'X'
lv_prid  TYPE SY-TABIX. "   0

  CALL FUNCTION 'DD_MX_TABL_DEP_ACT'  "DD: activation of tables with MULTIPLEX = 'D'
    EXPORTING
         MX_TABNAME = lv_mx_tabname
         TABNAME = lv_tabname
         ACT_MODE = lv_act_mode
         NTAB_PUTSTATE = lv_ntab_putstate
         AUTH_CHK = lv_auth_chk
         EXCOMMIT = lv_excommit
         UPGRMODE = lv_upgrmode
         SET_MX = lv_set_mx
         PRID = lv_prid
    IMPORTING
         ACT_RESULT = lv_act_result
    EXCEPTIONS
        ILLEGAL_VALUE = 1
. " DD_MX_TABL_DEP_ACT




ABAP code using 7.40 inline data declarations to call FM DD_MX_TABL_DEP_ACT

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.

"SELECT single TABIX FROM SY INTO @DATA(ld_act_result).
 
"SELECT single TABNAME FROM DD02V INTO @DATA(ld_mx_tabname).
 
 
"SELECT single TABNAME FROM DD02V INTO @DATA(ld_tabname).
 
"SELECT single MODE FROM DDREFSTRUC INTO @DATA(ld_act_mode).
DATA(ld_act_mode) = 1.
 
"SELECT single MODEFLAG FROM DDXTT INTO @DATA(ld_ntab_putstate).
DATA(ld_ntab_putstate) = 'A'.
 
"SELECT single BOOL FROM DDREFSTRUC INTO @DATA(ld_auth_chk).
DATA(ld_auth_chk) = 'X'.
 
"SELECT single EXCOMMIT FROM DCTABLACT INTO @DATA(ld_excommit).
DATA(ld_excommit) = 'X'.
 
"SELECT single UPGRMODE FROM DCTABLACT INTO @DATA(ld_upgrmode).
DATA(ld_upgrmode) = ' '.
 
"SELECT single BOOL FROM DDREFSTRUC INTO @DATA(ld_set_mx).
DATA(ld_set_mx) = 'X'.
 
"SELECT single TABIX FROM SY INTO @DATA(ld_prid).
 


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!