SAP TR_GET_REQUEST_TYPE Function Module for Determine requests and task type for object









TR_GET_REQUEST_TYPE is a standard tr get request type SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine requests and task type for object 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 tr get request type FM, simply by entering the name TR_GET_REQUEST_TYPE into the relevant SAP transaction such as SE37 or SE38.

Function Group: STRJ
Program Name: SAPLSTRJ
Main Program: SAPLSTRJ
Appliation area: S
Release date: 26-Mar-1998
Mode(Normal, Remote etc): Normal Function Module
Update:



Function TR_GET_REQUEST_TYPE 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 'TR_GET_REQUEST_TYPE'"Determine requests and task type for object
  EXPORTING
   IV_PGMID =  "Program ID
   IV_OBJECT =  "Object type
   IV_OBJ_NAME =  "Object Name

 IMPORTING
   EV_REQUEST_TYPE =  "Request type
   EV_TASK_TYPE =  "Task type
   EV_TARSYSTEM =  "Target System

EXCEPTIONS
   NO_REQUEST_NEEDED = 1    INVALID_OBJECT = 2    SYSTEM_ERROR = 3
.



IMPORTING Parameters details for TR_GET_REQUEST_TYPE

IV_PGMID - Program ID

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

IV_OBJECT - Object type

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

IV_OBJ_NAME - Object Name

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

EXPORTING Parameters details for TR_GET_REQUEST_TYPE

EV_REQUEST_TYPE - Request type

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

EV_TASK_TYPE - Task type

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

EV_TARSYSTEM - Target System

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

EXCEPTIONS details

NO_REQUEST_NEEDED - No request required

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

INVALID_OBJECT - Invalid object

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

SYSTEM_ERROR - System error

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

Copy and paste ABAP code example for TR_GET_REQUEST_TYPE 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_iv_pgmid  TYPE E071-PGMID, "   
lv_ev_request_type  TYPE E070-TRFUNCTION, "   
lv_no_request_needed  TYPE E070, "   
lv_iv_object  TYPE E071-OBJECT, "   
lv_ev_task_type  TYPE E070-TRFUNCTION, "   
lv_invalid_object  TYPE E070, "   
lv_iv_obj_name  TYPE E071-OBJ_NAME, "   
lv_ev_tarsystem  TYPE E070-TARSYSTEM, "   
lv_system_error  TYPE E070. "   

  CALL FUNCTION 'TR_GET_REQUEST_TYPE'  "Determine requests and task type for object
    EXPORTING
         IV_PGMID = lv_iv_pgmid
         IV_OBJECT = lv_iv_object
         IV_OBJ_NAME = lv_iv_obj_name
    IMPORTING
         EV_REQUEST_TYPE = lv_ev_request_type
         EV_TASK_TYPE = lv_ev_task_type
         EV_TARSYSTEM = lv_ev_tarsystem
    EXCEPTIONS
        NO_REQUEST_NEEDED = 1
        INVALID_OBJECT = 2
        SYSTEM_ERROR = 3
. " TR_GET_REQUEST_TYPE




ABAP code using 7.40 inline data declarations to call FM TR_GET_REQUEST_TYPE

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 PGMID FROM E071 INTO @DATA(ld_iv_pgmid).
 
"SELECT single TRFUNCTION FROM E070 INTO @DATA(ld_ev_request_type).
 
 
"SELECT single OBJECT FROM E071 INTO @DATA(ld_iv_object).
 
"SELECT single TRFUNCTION FROM E070 INTO @DATA(ld_ev_task_type).
 
 
"SELECT single OBJ_NAME FROM E071 INTO @DATA(ld_iv_obj_name).
 
"SELECT single TARSYSTEM FROM E070 INTO @DATA(ld_ev_tarsystem).
 
 


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!