SAP ISR_ACTIVITY_EXECUTE_TASKDOC Function Module for









ISR_ACTIVITY_EXECUTE_TASKDOC is a standard isr activity execute taskdoc 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 isr activity execute taskdoc FM, simply by entering the name ISR_ACTIVITY_EXECUTE_TASKDOC into the relevant SAP transaction such as SE37 or SE38.

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



Function ISR_ACTIVITY_EXECUTE_TASKDOC 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 'ISR_ACTIVITY_EXECUTE_TASKDOC'"
  EXPORTING
   I_VIQMEL =  "
   I_CUSTOMIZING =  "
   I_MANUM =  "
   I_FBCALL =  "

 IMPORTING
   E_QNQMASM0 =  "
   E_QNQMAQMEL0 =  "
   E_BUCH =  "

TABLES
   TI_IVIQMFE =  "
   TI_IVIQMUR =  "
   TI_IVIQMSM =  "
   TI_IVIQMMA =  "
   TI_IHPA =  "
*  TE_CONTAINER =  "
*  TE_LINES =  "

EXCEPTIONS
   ACTION_STOPPED = 1
.



IMPORTING Parameters details for ISR_ACTIVITY_EXECUTE_TASKDOC

I_VIQMEL -

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

I_CUSTOMIZING -

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

I_MANUM -

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

I_FBCALL -

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

EXPORTING Parameters details for ISR_ACTIVITY_EXECUTE_TASKDOC

E_QNQMASM0 -

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

E_QNQMAQMEL0 -

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

E_BUCH -

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

TABLES Parameters details for ISR_ACTIVITY_EXECUTE_TASKDOC

TI_IVIQMFE -

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

TI_IVIQMUR -

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

TI_IVIQMSM -

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

TI_IVIQMMA -

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

TI_IHPA -

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

TE_CONTAINER -

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

TE_LINES -

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

EXCEPTIONS details

ACTION_STOPPED -

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

Copy and paste ABAP code example for ISR_ACTIVITY_EXECUTE_TASKDOC 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_i_viqmel  TYPE VIQMEL, "   
lv_e_qnqmasm0  TYPE QNQMASM0, "   
lt_ti_iviqmfe  TYPE STANDARD TABLE OF WQMFE, "   
lv_action_stopped  TYPE WQMFE, "   
lt_ti_iviqmur  TYPE STANDARD TABLE OF WQMUR, "   
lv_e_qnqmaqmel0  TYPE QNQMAQMEL0, "   
lv_i_customizing  TYPE V_TQ85, "   
lv_e_buch  TYPE QKZ, "   
lv_i_manum  TYPE QMSM-MANUM, "   
lt_ti_iviqmsm  TYPE STANDARD TABLE OF WQMSM, "   
lv_i_fbcall  TYPE WQMSM, "   
lt_ti_iviqmma  TYPE STANDARD TABLE OF WQMMA, "   
lt_ti_ihpa  TYPE STANDARD TABLE OF IHPA, "   
lt_te_container  TYPE STANDARD TABLE OF SWCONT, "   
lt_te_lines  TYPE STANDARD TABLE OF TLINE. "   

  CALL FUNCTION 'ISR_ACTIVITY_EXECUTE_TASKDOC'  "
    EXPORTING
         I_VIQMEL = lv_i_viqmel
         I_CUSTOMIZING = lv_i_customizing
         I_MANUM = lv_i_manum
         I_FBCALL = lv_i_fbcall
    IMPORTING
         E_QNQMASM0 = lv_e_qnqmasm0
         E_QNQMAQMEL0 = lv_e_qnqmaqmel0
         E_BUCH = lv_e_buch
    TABLES
         TI_IVIQMFE = lt_ti_iviqmfe
         TI_IVIQMUR = lt_ti_iviqmur
         TI_IVIQMSM = lt_ti_iviqmsm
         TI_IVIQMMA = lt_ti_iviqmma
         TI_IHPA = lt_ti_ihpa
         TE_CONTAINER = lt_te_container
         TE_LINES = lt_te_lines
    EXCEPTIONS
        ACTION_STOPPED = 1
. " ISR_ACTIVITY_EXECUTE_TASKDOC




ABAP code using 7.40 inline data declarations to call FM ISR_ACTIVITY_EXECUTE_TASKDOC

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 MANUM FROM QMSM INTO @DATA(ld_i_manum).
 
 
 
 
 
 
 


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!