SAP QM06_SEND_REPLY_STEP2 Function Module for Obsolet - Versenden eines Dokuments (2.Schritt)









QM06_SEND_REPLY_STEP2 is a standard qm06 send reply step2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Obsolet - Versenden eines Dokuments (2.Schritt) 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 qm06 send reply step2 FM, simply by entering the name QM06_SEND_REPLY_STEP2 into the relevant SAP transaction such as SE37 or SE38.

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



Function QM06_SEND_REPLY_STEP2 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 'QM06_SEND_REPLY_STEP2'"Obsolet - Versenden eines Dokuments (2.Schritt)
  EXPORTING
   I_VIQMEL =  "Notification data
   I_MANUM =  "Sequence number of task to be created
*  I_AUFGABE = ' ' "Workflow task for container

TABLES
   TI_IVIQMFE =  "Defect items (table will not be exorted)
   TI_IVIQMUR =  "Causes (table will not be exported)
   TI_IVIQMSM =  "Tasks (table will not be exported)
   TI_IVIQMMA =  "Activity (table will not be exported)
   TI_IHPAD =  "Partners (table will not be exported)
*  T_CONTAINER =  "Container contents for workflow
.



IMPORTING Parameters details for QM06_SEND_REPLY_STEP2

I_VIQMEL - Notification data

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

I_MANUM - Sequence number of task to be created

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

I_AUFGABE - Workflow task for container

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

TABLES Parameters details for QM06_SEND_REPLY_STEP2

TI_IVIQMFE - Defect items (table will not be exorted)

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

TI_IVIQMUR - Causes (table will not be exported)

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

TI_IVIQMSM - Tasks (table will not be exported)

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

TI_IVIQMMA - Activity (table will not be exported)

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

TI_IHPAD - Partners (table will not be exported)

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

T_CONTAINER - Container contents for workflow

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

Copy and paste ABAP code example for QM06_SEND_REPLY_STEP2 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, "   
lt_ti_iviqmfe  TYPE STANDARD TABLE OF WQMFE, "   
lv_i_manum  TYPE QMSM-MANUM, "   
lt_ti_iviqmur  TYPE STANDARD TABLE OF WQMUR, "   
lv_i_aufgabe  TYPE SWW_TASK, "   SPACE
lt_ti_iviqmsm  TYPE STANDARD TABLE OF WQMSM, "   
lt_ti_iviqmma  TYPE STANDARD TABLE OF WQMMA, "   
lt_ti_ihpad  TYPE STANDARD TABLE OF IHPAD, "   
lt_t_container  TYPE STANDARD TABLE OF SWCONT. "   

  CALL FUNCTION 'QM06_SEND_REPLY_STEP2'  "Obsolet - Versenden eines Dokuments (2.Schritt)
    EXPORTING
         I_VIQMEL = lv_i_viqmel
         I_MANUM = lv_i_manum
         I_AUFGABE = lv_i_aufgabe
    TABLES
         TI_IVIQMFE = lt_ti_iviqmfe
         TI_IVIQMUR = lt_ti_iviqmur
         TI_IVIQMSM = lt_ti_iviqmsm
         TI_IVIQMMA = lt_ti_iviqmma
         TI_IHPAD = lt_ti_ihpad
         T_CONTAINER = lt_t_container
. " QM06_SEND_REPLY_STEP2




ABAP code using 7.40 inline data declarations to call FM QM06_SEND_REPLY_STEP2

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).
 
 
DATA(ld_i_aufgabe) = ' '.
 
 
 
 
 


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!