SAP RTP_RPUS_EVENT_FMOD Function Module for Field modification for screen fields
RTP_RPUS_EVENT_FMOD is a standard rtp rpus event fmod SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Field modification for screen fields 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 rpus event fmod FM, simply by entering the name RTP_RPUS_EVENT_FMOD into the relevant SAP transaction such as SE37 or SE38.
Function Group: RTP_RPUS_FPLAN
Program Name: SAPLRTP_RPUS_FPLAN
Main Program: SAPLRTP_RPUS_FPLAN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RTP_RPUS_EVENT_FMOD 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_RPUS_EVENT_FMOD'"Field modification for screen fields.
EXPORTING
FLDGR = "Field Group
IN_STATUS = "Field status
IMPORTING
OUT_STATUS = "Field status
IMPORTING Parameters details for RTP_RPUS_EVENT_FMOD
FLDGR - Field Group
Data type: TBZ3W-FLDGROptional: No
Call by Reference: No ( called with pass by value option)
IN_STATUS - Field status
Data type: TRTP_US_FSTAT-FIELD_STATUSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RTP_RPUS_EVENT_FMOD
OUT_STATUS - Field status
Data type: TRTP_US_FSTAT-FIELD_STATUSOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RTP_RPUS_EVENT_FMOD 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_fldgr | TYPE TBZ3W-FLDGR, " | |||
| lv_out_status | TYPE TRTP_US_FSTAT-FIELD_STATUS, " | |||
| lv_in_status | TYPE TRTP_US_FSTAT-FIELD_STATUS. " |
|   CALL FUNCTION 'RTP_RPUS_EVENT_FMOD' "Field modification for screen fields |
| EXPORTING | ||
| FLDGR | = lv_fldgr | |
| IN_STATUS | = lv_in_status | |
| IMPORTING | ||
| OUT_STATUS | = lv_out_status | |
| . " RTP_RPUS_EVENT_FMOD | ||
ABAP code using 7.40 inline data declarations to call FM RTP_RPUS_EVENT_FMOD
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 FLDGR FROM TBZ3W INTO @DATA(ld_fldgr). | ||||
| "SELECT single FIELD_STATUS FROM TRTP_US_FSTAT INTO @DATA(ld_out_status). | ||||
| "SELECT single FIELD_STATUS FROM TRTP_US_FSTAT INTO @DATA(ld_in_status). | ||||
Search for further information about these or an SAP related objects