SAP HRPY_READ_T511K Function Module for
HRPY_READ_T511K is a standard hrpy read t511k 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 hrpy read t511k FM, simply by entering the name HRPY_READ_T511K into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRPY_LOAN
Program Name: SAPLHRPY_LOAN
Main Program: SAPLHRPY_LOAN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRPY_READ_T511K 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 'HRPY_READ_T511K'".
EXPORTING
PF_MOLGA = "
PF_CONST = "
PF_DATE = "
IMPORTING
PF_KWERT = "
EXCEPTIONS
NO_ENTRY_FOUND_T511K = 1
IMPORTING Parameters details for HRPY_READ_T511K
PF_MOLGA -
Data type: MOLGAOptional: No
Call by Reference: Yes
PF_CONST -
Data type: PAYCOOptional: No
Call by Reference: Yes
PF_DATE -
Data type: DATSOptional: No
Call by Reference: Yes
EXPORTING Parameters details for HRPY_READ_T511K
PF_KWERT -
Data type: ABRWTOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_ENTRY_FOUND_T511K -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for HRPY_READ_T511K 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_pf_kwert | TYPE ABRWT, " | |||
| lv_pf_molga | TYPE MOLGA, " | |||
| lv_no_entry_found_t511k | TYPE MOLGA, " | |||
| lv_pf_const | TYPE PAYCO, " | |||
| lv_pf_date | TYPE DATS. " |
|   CALL FUNCTION 'HRPY_READ_T511K' " |
| EXPORTING | ||
| PF_MOLGA | = lv_pf_molga | |
| PF_CONST | = lv_pf_const | |
| PF_DATE | = lv_pf_date | |
| IMPORTING | ||
| PF_KWERT | = lv_pf_kwert | |
| EXCEPTIONS | ||
| NO_ENTRY_FOUND_T511K = 1 | ||
| . " HRPY_READ_T511K | ||
ABAP code using 7.40 inline data declarations to call FM HRPY_READ_T511K
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