SAP RTP_US_API_READ_STANDARD_ROLE Function Module for Reads and buffers standard roles for specified category
RTP_US_API_READ_STANDARD_ROLE is a standard rtp us api read standard role SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Reads and buffers standard roles for specified category 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 rtp us api read standard role FM, simply by entering the name RTP_US_API_READ_STANDARD_ROLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RTP_US_API_PLAN
Program Name: SAPLRTP_US_API_PLAN
Main Program: SAPLRTP_US_API_PLAN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RTP_US_API_READ_STANDARD_ROLE 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 'RTP_US_API_READ_STANDARD_ROLE'"Reads and buffers standard roles for specified category.
EXPORTING
I_ROLE_CATEGORY = "
IMPORTING
E_STND_ROLE = "
IMPORTING Parameters details for RTP_US_API_READ_STANDARD_ROLE
I_ROLE_CATEGORY -
Data type: BU_PARTNERROLECATOptional: No
Call by Reference: Yes
EXPORTING Parameters details for RTP_US_API_READ_STANDARD_ROLE
E_STND_ROLE -
Data type: BU_PARTNERROLEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for RTP_US_API_READ_STANDARD_ROLE 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_e_stnd_role | TYPE BU_PARTNERROLE, " | |||
| lv_i_role_category | TYPE BU_PARTNERROLECAT. " |
|   CALL FUNCTION 'RTP_US_API_READ_STANDARD_ROLE' "Reads and buffers standard roles for specified category |
| EXPORTING | ||
| I_ROLE_CATEGORY | = lv_i_role_category | |
| IMPORTING | ||
| E_STND_ROLE | = lv_e_stnd_role | |
| . " RTP_US_API_READ_STANDARD_ROLE | ||
ABAP code using 7.40 inline data declarations to call FM RTP_US_API_READ_STANDARD_ROLE
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