SAP MOD_KUN_ACTIVATE Function Module for









MOD_KUN_ACTIVATE is a standard mod kun activate 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 mod kun activate FM, simply by entering the name MOD_KUN_ACTIVATE into the relevant SAP transaction such as SE37 or SE38.

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



Function MOD_KUN_ACTIVATE 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 'MOD_KUN_ACTIVATE'"
EXPORTING
* ACTIVATE = 'X' "
* CALLED_BY_SMOD = ' ' "
* CALLED_BY_TRANSPORT = ' ' "
* DEACTIVATE = ' ' "
* MESSAGE = 'X' "
MODNAME = "
* ACT_TABLES = "
* IGNORE_MIGRATION = SEEX_FALSE "

TABLES
* FAILURES = "
* GENFAILURES = "
* INCLTABS = "

EXCEPTIONS
CALL_ERROR = 1 GENERATE_ERROR = 2 MODATTR_STATUS = 3 MOD_ACTIVE = 4 MOD_ENQUEUED = 5 NOT_ACTIVATED = 6 NO_MODIFICATION = 7 PERMISSION_FAILURE = 8
.



IMPORTING Parameters details for MOD_KUN_ACTIVATE

ACTIVATE -

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

CALLED_BY_SMOD -

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

CALLED_BY_TRANSPORT -

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

DEACTIVATE -

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

MESSAGE -

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

MODNAME -

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

ACT_TABLES -

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

IGNORE_MIGRATION -

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

TABLES Parameters details for MOD_KUN_ACTIVATE

FAILURES -

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

GENFAILURES -

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

INCLTABS -

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

EXCEPTIONS details

CALL_ERROR -

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

GENERATE_ERROR -

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

MODATTR_STATUS -

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

MOD_ACTIVE -

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

MOD_ENQUEUED -

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

NOT_ACTIVATED -

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

NO_MODIFICATION -

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

PERMISSION_FAILURE -

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

Copy and paste ABAP code example for MOD_KUN_ACTIVATE 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_activate  TYPE STRING, "   'X'
lt_failures  TYPE STANDARD TABLE OF STRING, "   
lv_call_error  TYPE STRING, "   
lt_genfailures  TYPE STANDARD TABLE OF STRING, "   
lv_called_by_smod  TYPE STRING, "   SPACE
lv_generate_error  TYPE STRING, "   
lt_incltabs  TYPE STANDARD TABLE OF STRING, "   
lv_modattr_status  TYPE STRING, "   
lv_called_by_transport  TYPE STRING, "   SPACE
lv_deactivate  TYPE STRING, "   SPACE
lv_mod_active  TYPE STRING, "   
lv_message  TYPE STRING, "   'X'
lv_mod_enqueued  TYPE STRING, "   
lv_modname  TYPE MODACT-NAME, "   
lv_not_activated  TYPE MODACT, "   
lv_act_tables  TYPE MODACT, "   
lv_no_modification  TYPE MODACT, "   
lv_ignore_migration  TYPE SEEX_BOOLEAN, "   SEEX_FALSE
lv_permission_failure  TYPE SEEX_BOOLEAN. "   

  CALL FUNCTION 'MOD_KUN_ACTIVATE'  "
    EXPORTING
         ACTIVATE = lv_activate
         CALLED_BY_SMOD = lv_called_by_smod
         CALLED_BY_TRANSPORT = lv_called_by_transport
         DEACTIVATE = lv_deactivate
         MESSAGE = lv_message
         MODNAME = lv_modname
         ACT_TABLES = lv_act_tables
         IGNORE_MIGRATION = lv_ignore_migration
    TABLES
         FAILURES = lt_failures
         GENFAILURES = lt_genfailures
         INCLTABS = lt_incltabs
    EXCEPTIONS
        CALL_ERROR = 1
        GENERATE_ERROR = 2
        MODATTR_STATUS = 3
        MOD_ACTIVE = 4
        MOD_ENQUEUED = 5
        NOT_ACTIVATED = 6
        NO_MODIFICATION = 7
        PERMISSION_FAILURE = 8
. " MOD_KUN_ACTIVATE




ABAP code using 7.40 inline data declarations to call FM MOD_KUN_ACTIVATE

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_activate) = 'X'.
 
 
 
 
DATA(ld_called_by_smod) = ' '.
 
 
 
 
DATA(ld_called_by_transport) = ' '.
 
DATA(ld_deactivate) = ' '.
 
 
DATA(ld_message) = 'X'.
 
 
"SELECT single NAME FROM MODACT INTO @DATA(ld_modname).
 
 
 
 
DATA(ld_ignore_migration) = SEEX_FALSE.
 
 


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!