SAP QST06_CHANGE_MPOS Function Module for NOTRANSL: Ändern Wartungsposition per Batch-Input









QST06_CHANGE_MPOS is a standard qst06 change mpos SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Ändern Wartungsposition per Batch-Input 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 qst06 change mpos FM, simply by entering the name QST06_CHANGE_MPOS into the relevant SAP transaction such as SE37 or SE38.

Function Group: QST06
Program Name: SAPLQST06
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function QST06_CHANGE_MPOS 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 'QST06_CHANGE_MPOS'"NOTRANSL: Ändern Wartungsposition per Batch-Input
  EXPORTING
*  CTU = 'X' "Queue PUTQ active flag
   LOW_002 =  "BDC Field Value
   LOW_003 =  "BDC Field Value
   ABREA_004 =  "BDC Field Value
   STATA_005 =  "BDC Field Value
   PSTXT_006 =  "BDC Field Value
   PHYNR_007 =  "BDC Field Value
   ART_008 =  "BDC Field Value
   PLNNR_009 =  "BDC Field Value
   PLNAL_010 =  "BDC Field Value
*  MODE = 'N' "Queue PUTQ active flag
*  UPDATE = 'L' "Queue PUTQ active flag
*  GROUP =  "Group name: Batch input session name
*  USER =  "Queue user ID / for historical reasons
*  KEEP =  "Queue deletion indicator for processed sessions
*  HOLDDATE =  "Queue start date
*  NODATA = '/' "Queue PUTQ active flag
   LOW_001 =  "BDC Field Value

 IMPORTING
   SUBRC =  "ABAP System Field: Return Code of ABAP Statements

TABLES
*  MESSTAB =  "Collecting messages in the SAP System
.



IMPORTING Parameters details for QST06_CHANGE_MPOS

CTU - Queue PUTQ active flag

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

LOW_002 - BDC Field Value

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

LOW_003 - BDC Field Value

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

ABREA_004 - BDC Field Value

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

STATA_005 - BDC Field Value

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

PSTXT_006 - BDC Field Value

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

PHYNR_007 - BDC Field Value

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

ART_008 - BDC Field Value

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

PLNNR_009 - BDC Field Value

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

PLNAL_010 - BDC Field Value

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

MODE - Queue PUTQ active flag

Data type: APQI-PUTACTIVE
Default: 'N'
Optional: Yes
Call by Reference: No ( called with pass by value option)

UPDATE - Queue PUTQ active flag

Data type: APQI-PUTACTIVE
Default: 'L'
Optional: Yes
Call by Reference: No ( called with pass by value option)

GROUP - Group name: Batch input session name

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

USER - Queue user ID / for historical reasons

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

KEEP - Queue deletion indicator for processed sessions

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

HOLDDATE - Queue start date

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

NODATA - Queue PUTQ active flag

Data type: APQI-PUTACTIVE
Default: '/'
Optional: Yes
Call by Reference: No ( called with pass by value option)

LOW_001 - BDC Field Value

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

EXPORTING Parameters details for QST06_CHANGE_MPOS

SUBRC - ABAP System Field: Return Code of ABAP Statements

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

TABLES Parameters details for QST06_CHANGE_MPOS

MESSTAB - Collecting messages in the SAP System

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

Copy and paste ABAP code example for QST06_CHANGE_MPOS 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_ctu  TYPE APQI-PUTACTIVE, "   'X'
lv_subrc  TYPE SYST-SUBRC, "   
lt_messtab  TYPE STANDARD TABLE OF BDCMSGCOLL, "   
lv_low_002  TYPE BDC_FVAL, "   
lv_low_003  TYPE BDC_FVAL, "   
lv_abrea_004  TYPE BDC_FVAL, "   
lv_stata_005  TYPE BDC_FVAL, "   
lv_pstxt_006  TYPE BDC_FVAL, "   
lv_phynr_007  TYPE BDC_FVAL, "   
lv_art_008  TYPE BDC_FVAL, "   
lv_plnnr_009  TYPE BDC_FVAL, "   
lv_plnal_010  TYPE BDC_FVAL, "   
lv_mode  TYPE APQI-PUTACTIVE, "   'N'
lv_update  TYPE APQI-PUTACTIVE, "   'L'
lv_group  TYPE APQI-GROUPID, "   
lv_user  TYPE APQI-USERID, "   
lv_keep  TYPE APQI-QERASE, "   
lv_holddate  TYPE APQI-STARTDATE, "   
lv_nodata  TYPE APQI-PUTACTIVE, "   '/'
lv_low_001  TYPE BDC_FVAL. "   

  CALL FUNCTION 'QST06_CHANGE_MPOS'  "NOTRANSL: Ändern Wartungsposition per Batch-Input
    EXPORTING
         CTU = lv_ctu
         LOW_002 = lv_low_002
         LOW_003 = lv_low_003
         ABREA_004 = lv_abrea_004
         STATA_005 = lv_stata_005
         PSTXT_006 = lv_pstxt_006
         PHYNR_007 = lv_phynr_007
         ART_008 = lv_art_008
         PLNNR_009 = lv_plnnr_009
         PLNAL_010 = lv_plnal_010
         MODE = lv_mode
         UPDATE = lv_update
         GROUP = lv_group
         USER = lv_user
         KEEP = lv_keep
         HOLDDATE = lv_holddate
         NODATA = lv_nodata
         LOW_001 = lv_low_001
    IMPORTING
         SUBRC = lv_subrc
    TABLES
         MESSTAB = lt_messtab
. " QST06_CHANGE_MPOS




ABAP code using 7.40 inline data declarations to call FM QST06_CHANGE_MPOS

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 PUTACTIVE FROM APQI INTO @DATA(ld_ctu).
DATA(ld_ctu) = 'X'.
 
"SELECT single SUBRC FROM SYST INTO @DATA(ld_subrc).
 
 
 
 
 
 
 
 
 
 
 
"SELECT single PUTACTIVE FROM APQI INTO @DATA(ld_mode).
DATA(ld_mode) = 'N'.
 
"SELECT single PUTACTIVE FROM APQI INTO @DATA(ld_update).
DATA(ld_update) = 'L'.
 
"SELECT single GROUPID FROM APQI INTO @DATA(ld_group).
 
"SELECT single USERID FROM APQI INTO @DATA(ld_user).
 
"SELECT single QERASE FROM APQI INTO @DATA(ld_keep).
 
"SELECT single STARTDATE FROM APQI INTO @DATA(ld_holddate).
 
"SELECT single PUTACTIVE FROM APQI INTO @DATA(ld_nodata).
DATA(ld_nodata) = '/'.
 
 


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!