SAP DD_DOMA_SET_ACT_TEST Function Module for









DD_DOMA_SET_ACT_TEST is a standard dd doma set act test 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 dd doma set act test FM, simply by entering the name DD_DOMA_SET_ACT_TEST into the relevant SAP transaction such as SE37 or SE38.

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



Function DD_DOMA_SET_ACT_TEST 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_DOMA_SET_ACT_TEST'"
EXPORTING
* TIMER_ON = ' ' "
* POINTER = ' ' "Field Name
* OFF = 0 "Obsolete
* LEN = 0 "Obsolete
* TRACE = 0 "
* ACT_MODE = 9 "
* LOGPATH = 'ACT&DATE&&TIME&' "
* LOGDEF = 'MNS1' "

TABLES
DOMANAMES = "
ACT_RESULTS = "
CTRL_TABL_RES = "

EXCEPTIONS
ACT_REFUSED = 1 ILLEGAL_VALUE = 2 ACT_UNLOCK_FAILURE = 3 OP_FAILURE = 4
.



IMPORTING Parameters details for DD_DOMA_SET_ACT_TEST

TIMER_ON -

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

POINTER - Field Name

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

OFF - Obsolete

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

LEN - Obsolete

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

TRACE -

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

ACT_MODE -

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

LOGPATH -

Data type:
Default: 'ACT&DATE&&TIME&'
Optional: Yes
Call by Reference: No ( called with pass by value option)

LOGDEF -

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

TABLES Parameters details for DD_DOMA_SET_ACT_TEST

DOMANAMES -

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

ACT_RESULTS -

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

CTRL_TABL_RES -

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

EXCEPTIONS details

ACT_REFUSED -

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

ILLEGAL_VALUE -

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

ACT_UNLOCK_FAILURE -

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

OP_FAILURE -

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

Copy and paste ABAP code example for DD_DOMA_SET_ACT_TEST 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_timer_on  TYPE DDREFSTRUC-STATE, "   ' '
lt_domanames  TYPE STANDARD TABLE OF DDREFSTRUC, "   
lv_act_refused  TYPE DDREFSTRUC, "   
lv_pointer  TYPE FNAM_____4, "   ' '
lt_act_results  TYPE STANDARD TABLE OF DDDOACTRES, "   
lv_illegal_value  TYPE DDDOACTRES, "   
lv_off  TYPE SY-FDPOS, "   0
lt_ctrl_tabl_res  TYPE STANDARD TABLE OF DCTABLRES, "   
lv_act_unlock_failure  TYPE DCTABLRES, "   
lv_len  TYPE SY-FDPOS, "   0
lv_op_failure  TYPE SY, "   
lv_trace  TYPE SY-TABIX, "   0
lv_act_mode  TYPE DDREFSTRUC-MODE, "   9
lv_logpath  TYPE DDREFSTRUC, "   'ACT&DATE&&TIME&'
lv_logdef  TYPE DDLOGDEF. "   'MNS1'

  CALL FUNCTION 'DD_DOMA_SET_ACT_TEST'  "
    EXPORTING
         TIMER_ON = lv_timer_on
         POINTER = lv_pointer
         OFF = lv_off
         LEN = lv_len
         TRACE = lv_trace
         ACT_MODE = lv_act_mode
         LOGPATH = lv_logpath
         LOGDEF = lv_logdef
    TABLES
         DOMANAMES = lt_domanames
         ACT_RESULTS = lt_act_results
         CTRL_TABL_RES = lt_ctrl_tabl_res
    EXCEPTIONS
        ACT_REFUSED = 1
        ILLEGAL_VALUE = 2
        ACT_UNLOCK_FAILURE = 3
        OP_FAILURE = 4
. " DD_DOMA_SET_ACT_TEST




ABAP code using 7.40 inline data declarations to call FM DD_DOMA_SET_ACT_TEST

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 STATE FROM DDREFSTRUC INTO @DATA(ld_timer_on).
DATA(ld_timer_on) = ' '.
 
 
 
DATA(ld_pointer) = ' '.
 
 
 
"SELECT single FDPOS FROM SY INTO @DATA(ld_off).
 
 
 
"SELECT single FDPOS FROM SY INTO @DATA(ld_len).
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_trace).
 
"SELECT single MODE FROM DDREFSTRUC INTO @DATA(ld_act_mode).
DATA(ld_act_mode) = 9.
 
DATA(ld_logpath) = 'ACT&DATE&&TIME&'.
 
DATA(ld_logdef) = 'MNS1'.
 


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!