SAP PT_ARQ_REQUEST_EXECUTE Function Module for









PT_ARQ_REQUEST_EXECUTE is a standard pt arq request execute 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 pt arq request execute FM, simply by entering the name PT_ARQ_REQUEST_EXECUTE into the relevant SAP transaction such as SE37 or SE38.

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



Function PT_ARQ_REQUEST_EXECUTE 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 'PT_ARQ_REQUEST_EXECUTE'"
  EXPORTING
   IM_REQUEST_ID =  "GUID in 'CHAR' Format in Uppercase
*  IM_COMMAND =  "ESS Command
   IM_PERNR =  "Personnel Number
   IM_MODUS =  "Application Mode of Leave Request
*  IM_DEBUG =  "Boolean Variable (X=True, -=False, Space=Unknown)

 IMPORTING
   EX_REQUEST =  "Leave Request: Entry in Request List
   EX_HAS_ERRORS =  "Errors Exist
   EX_SHOW_CHANGE =  "Boolean Variable (X=True, -=False, Space=Unknown)

TABLES
   EX_MESSAGES =  "Return Parameter(s)
   EX_COMMANDS =  "Leave Request: UI Commands
.



IMPORTING Parameters details for PT_ARQ_REQUEST_EXECUTE

IM_REQUEST_ID - GUID in 'CHAR' Format in Uppercase

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

IM_COMMAND - ESS Command

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

IM_PERNR - Personnel Number

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

IM_MODUS - Application Mode of Leave Request

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

IM_DEBUG - Boolean Variable (X=True, -=False, Space=Unknown)

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

EXPORTING Parameters details for PT_ARQ_REQUEST_EXECUTE

EX_REQUEST - Leave Request: Entry in Request List

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

EX_HAS_ERRORS - Errors Exist

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

EX_SHOW_CHANGE - Boolean Variable (X=True, -=False, Space=Unknown)

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

TABLES Parameters details for PT_ARQ_REQUEST_EXECUTE

EX_MESSAGES - Return Parameter(s)

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

EX_COMMANDS - Leave Request: UI Commands

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

Copy and paste ABAP code example for PT_ARQ_REQUEST_EXECUTE 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_ex_request  TYPE PTARQ_UIA_REQUEST, "   
lt_ex_messages  TYPE STANDARD TABLE OF PTARQ_UIA_MESSAGES_TAB, "   
lv_im_request_id  TYPE TIM_REQ_ID, "   
lv_im_command  TYPE PTREQ_COMMAND, "   
lt_ex_commands  TYPE STANDARD TABLE OF PTARQ_UIA_COMMAND_TAB, "   
lv_ex_has_errors  TYPE PTREQ_HAS_ERROR_FLAG, "   
lv_im_pernr  TYPE P_PERNR, "   
lv_ex_show_change  TYPE BOOLEAN, "   
lv_im_modus  TYPE PT_ARQ_MODE, "   
lv_im_debug  TYPE BOOLEAN. "   

  CALL FUNCTION 'PT_ARQ_REQUEST_EXECUTE'  "
    EXPORTING
         IM_REQUEST_ID = lv_im_request_id
         IM_COMMAND = lv_im_command
         IM_PERNR = lv_im_pernr
         IM_MODUS = lv_im_modus
         IM_DEBUG = lv_im_debug
    IMPORTING
         EX_REQUEST = lv_ex_request
         EX_HAS_ERRORS = lv_ex_has_errors
         EX_SHOW_CHANGE = lv_ex_show_change
    TABLES
         EX_MESSAGES = lt_ex_messages
         EX_COMMANDS = lt_ex_commands
. " PT_ARQ_REQUEST_EXECUTE




ABAP code using 7.40 inline data declarations to call FM PT_ARQ_REQUEST_EXECUTE

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.

 
 
 
 
 
 
 
 
 
 


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!