SAP TMS_QAS_QA_STATUS_REQ Function Module for









TMS_QAS_QA_STATUS_REQ is a standard tms qas qa status req 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 tms qas qa status req FM, simply by entering the name TMS_QAS_QA_STATUS_REQ into the relevant SAP transaction such as SE37 or SE38.

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



Function TMS_QAS_QA_STATUS_REQ 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 'TMS_QAS_QA_STATUS_REQ'"
EXPORTING
IV_QA_SYSNAM = "TMS: System Name
IV_QA_CLIENT = "Target client for the request
IV_TRKORR = "Request/Task
IV_CLIENT = "Target client for the request
IV_AS4DATE = "Date of Last Change
IV_AS4TIME = "Last changed at
IV_LANGU_QASTEPS = "SAP R/3 System, Current Language

IMPORTING
ES_TMSQWL = "TMS QA: Worklist

TABLES
TT_TMSQWLF = "TMS QA: Worklist - QA Flags for Requests
TT_TMSQASTEPS = "TMS QA: Request Approval Steps
TT_TMSQASTEPT = "TMS QA: Short Texts for the QA Approval Steps
.



IMPORTING Parameters details for TMS_QAS_QA_STATUS_REQ

IV_QA_SYSNAM - TMS: System Name

Data type: TMSSYSNAM
Optional: No
Call by Reference: Yes

IV_QA_CLIENT - Target client for the request

Data type: TRTARCLI
Optional: No
Call by Reference: Yes

IV_TRKORR - Request/Task

Data type: TRKORR
Optional: No
Call by Reference: Yes

IV_CLIENT - Target client for the request

Data type: TRTARCLI
Optional: No
Call by Reference: Yes

IV_AS4DATE - Date of Last Change

Data type: AS4DATE
Optional: No
Call by Reference: Yes

IV_AS4TIME - Last changed at

Data type: AS4TIME
Optional: No
Call by Reference: Yes

IV_LANGU_QASTEPS - SAP R/3 System, Current Language

Data type: SY-LANGU
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for TMS_QAS_QA_STATUS_REQ

ES_TMSQWL - TMS QA: Worklist

Data type: TMSQWL
Optional: No
Call by Reference: Yes

TABLES Parameters details for TMS_QAS_QA_STATUS_REQ

TT_TMSQWLF - TMS QA: Worklist - QA Flags for Requests

Data type: TMSQWLF
Optional: No
Call by Reference: Yes

TT_TMSQASTEPS - TMS QA: Request Approval Steps

Data type: TMSQASTEPS
Optional: No
Call by Reference: Yes

TT_TMSQASTEPT - TMS QA: Short Texts for the QA Approval Steps

Data type: TMSQASTEPT
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TMS_QAS_QA_STATUS_REQ 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_es_tmsqwl  TYPE TMSQWL, "   
lt_tt_tmsqwlf  TYPE STANDARD TABLE OF TMSQWLF, "   
lv_iv_qa_sysnam  TYPE TMSSYSNAM, "   
lv_iv_qa_client  TYPE TRTARCLI, "   
lt_tt_tmsqasteps  TYPE STANDARD TABLE OF TMSQASTEPS, "   
lv_iv_trkorr  TYPE TRKORR, "   
lt_tt_tmsqastept  TYPE STANDARD TABLE OF TMSQASTEPT, "   
lv_iv_client  TYPE TRTARCLI, "   
lv_iv_as4date  TYPE AS4DATE, "   
lv_iv_as4time  TYPE AS4TIME, "   
lv_iv_langu_qasteps  TYPE SY-LANGU. "   

  CALL FUNCTION 'TMS_QAS_QA_STATUS_REQ'  "
    EXPORTING
         IV_QA_SYSNAM = lv_iv_qa_sysnam
         IV_QA_CLIENT = lv_iv_qa_client
         IV_TRKORR = lv_iv_trkorr
         IV_CLIENT = lv_iv_client
         IV_AS4DATE = lv_iv_as4date
         IV_AS4TIME = lv_iv_as4time
         IV_LANGU_QASTEPS = lv_iv_langu_qasteps
    IMPORTING
         ES_TMSQWL = lv_es_tmsqwl
    TABLES
         TT_TMSQWLF = lt_tt_tmsqwlf
         TT_TMSQASTEPS = lt_tt_tmsqasteps
         TT_TMSQASTEPT = lt_tt_tmsqastept
. " TMS_QAS_QA_STATUS_REQ




ABAP code using 7.40 inline data declarations to call FM TMS_QAS_QA_STATUS_REQ

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 LANGU FROM SY INTO @DATA(ld_iv_langu_qasteps).
 


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!