SAP RP_CONVERT_PAY Function Module for
RP_CONVERT_PAY is a standard rp convert pay 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 rp convert pay FM, simply by entering the name RP_CONVERT_PAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: RPIB
Program Name: SAPLRPIB
Main Program: SAPLRPIB
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RP_CONVERT_PAY 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 'RP_CONVERT_PAY'".
EXPORTING
BETRG = "
PERMO = "
IMPORTING
BETRG = "
PERMO = "
IMPORTING Parameters details for RP_CONVERT_PAY
BETRG -
Data type: PC207-BETRGOptional: No
Call by Reference: No ( called with pass by value option)
PERMO -
Data type: T549A-PERMOOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RP_CONVERT_PAY
BETRG -
Data type: PC207-BETRGOptional: No
Call by Reference: No ( called with pass by value option)
PERMO -
Data type: T549A-PERMOOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RP_CONVERT_PAY 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_betrg | TYPE PC207-BETRG, " | |||
| lv_betrg | TYPE PC207-BETRG, " | |||
| lv_permo | TYPE T549A-PERMO, " | |||
| lv_permo | TYPE T549A-PERMO. " |
|   CALL FUNCTION 'RP_CONVERT_PAY' " |
| EXPORTING | ||
| BETRG | = lv_betrg | |
| PERMO | = lv_permo | |
| IMPORTING | ||
| BETRG | = lv_betrg | |
| PERMO | = lv_permo | |
| . " RP_CONVERT_PAY | ||
ABAP code using 7.40 inline data declarations to call FM RP_CONVERT_PAY
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 BETRG FROM PC207 INTO @DATA(ld_betrg). | ||||
| "SELECT single BETRG FROM PC207 INTO @DATA(ld_betrg). | ||||
| "SELECT single PERMO FROM T549A INTO @DATA(ld_permo). | ||||
| "SELECT single PERMO FROM T549A INTO @DATA(ld_permo). | ||||
Search for further information about these or an SAP related objects