SAP TRINT_SELECT_REQUESTS Function Module for Selection of Requests









TRINT_SELECT_REQUESTS is a standard trint select requests SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Selection of Requests 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 trint select requests FM, simply by entering the name TRINT_SELECT_REQUESTS into the relevant SAP transaction such as SE37 or SE38.

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



Function TRINT_SELECT_REQUESTS 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 'TRINT_SELECT_REQUESTS'"Selection of Requests
EXPORTING
* IV_USERNAME_PATTERN = SY-UNAME "User selecting requests
* IS_SELECTION = "Other request/task parameters
* IV_COMPLETE_PROJECTS = 'X' "'X': STRKORR relationships are traced
* IV_VIA_SELSCREEN = ' ' "
* IS_POPUP = "
* IV_TITLE = "Title for selection screen

IMPORTING
ET_REQUESTS = "Table

CHANGING
* CS_RANGES = "

EXCEPTIONS
ACTION_ABORTED_BY_USER = 1
.



IMPORTING Parameters details for TRINT_SELECT_REQUESTS

IV_USERNAME_PATTERN - User selecting requests

Data type:
Default: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

IS_SELECTION - Other request/task parameters

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

IV_COMPLETE_PROJECTS - 'X': STRKORR relationships are traced

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

IV_VIA_SELSCREEN -

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

IS_POPUP -

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

IV_TITLE - Title for selection screen

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

EXPORTING Parameters details for TRINT_SELECT_REQUESTS

ET_REQUESTS - Table

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

CHANGING Parameters details for TRINT_SELECT_REQUESTS

CS_RANGES -

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

EXCEPTIONS details

ACTION_ABORTED_BY_USER -

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

Copy and paste ABAP code example for TRINT_SELECT_REQUESTS 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_cs_ranges  TYPE TRSEL_TS_RANGES, "   
lv_et_requests  TYPE TRWBO_REQUEST_HEADERS, "   
lv_iv_username_pattern  TYPE TRWBO_REQUEST_HEADERS, "   SY-UNAME
lv_action_aborted_by_user  TYPE TRWBO_REQUEST_HEADERS, "   
lv_is_selection  TYPE TRWBO_SELECTION, "   
lv_iv_complete_projects  TYPE C, "   'X'
lv_iv_via_selscreen  TYPE C, "   ' '
lv_is_popup  TYPE STRHI_POPUP, "   
lv_iv_title  TYPE TRWBO_TITLE. "   

  CALL FUNCTION 'TRINT_SELECT_REQUESTS'  "Selection of Requests
    EXPORTING
         IV_USERNAME_PATTERN = lv_iv_username_pattern
         IS_SELECTION = lv_is_selection
         IV_COMPLETE_PROJECTS = lv_iv_complete_projects
         IV_VIA_SELSCREEN = lv_iv_via_selscreen
         IS_POPUP = lv_is_popup
         IV_TITLE = lv_iv_title
    IMPORTING
         ET_REQUESTS = lv_et_requests
    CHANGING
         CS_RANGES = lv_cs_ranges
    EXCEPTIONS
        ACTION_ABORTED_BY_USER = 1
. " TRINT_SELECT_REQUESTS




ABAP code using 7.40 inline data declarations to call FM TRINT_SELECT_REQUESTS

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.

 
 
DATA(ld_iv_username_pattern) = SY-UNAME.
 
 
 
DATA(ld_iv_complete_projects) = 'X'.
 
DATA(ld_iv_via_selscreen) = ' '.
 
 
 


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!