SAP HR_ECM_READ_INFOTYPE Function Module for Read Several Records of an Employee Infotype
HR_ECM_READ_INFOTYPE is a standard hr ecm read infotype SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Several Records of an Employee Infotype 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 hr ecm read infotype FM, simply by entering the name HR_ECM_READ_INFOTYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRECM00INFTYACCESS
Program Name: SAPLHRECM00INFTYACCESS
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_ECM_READ_INFOTYPE 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 'HR_ECM_READ_INFOTYPE'"Read Several Records of an Employee Infotype.
EXPORTING
PERNR = "Personnel Number
INFTY = "Infotype
* SUBTY = '*' "Subtype
* OBJPS = '*' "Object Identification
* SPRPS = ' ' "Lock Indicator for HR Master Data Record
* BEGDA = '18000101' "Start Date
* ENDDA = '99991231' "End Date
* NO_AUTH_CHECK = ' ' "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
MESSAGE_HANDLER = "HR Master Data: Messages
IMPORTING
INFOTYPE_TAB = "
IS_OK = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
IMPORTING Parameters details for HR_ECM_READ_INFOTYPE
PERNR - Personnel Number
Data type: PSKEY-PERNROptional: No
Call by Reference: Yes
INFTY - Infotype
Data type: PSKEY-INFTYOptional: No
Call by Reference: Yes
SUBTY - Subtype
Data type: PSKEY-SUBTYDefault: '*'
Optional: Yes
Call by Reference: Yes
OBJPS - Object Identification
Data type: OBJPSDefault: '*'
Optional: Yes
Call by Reference: Yes
SPRPS - Lock Indicator for HR Master Data Record
Data type: PSKEY-SPRPSDefault: ' '
Optional: Yes
Call by Reference: Yes
BEGDA - Start Date
Data type: PSKEY-BEGDADefault: '18000101'
Optional: Yes
Call by Reference: Yes
ENDDA - End Date
Data type: PSKEY-ENDDADefault: '99991231'
Optional: Yes
Call by Reference: Yes
NO_AUTH_CHECK - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DDefault: ' '
Optional: Yes
Call by Reference: Yes
MESSAGE_HANDLER - HR Master Data: Messages
Data type: IF_HRPA_MESSAGE_HANDLEROptional: No
Call by Reference: Yes
EXPORTING Parameters details for HR_ECM_READ_INFOTYPE
INFOTYPE_TAB -
Data type: STANDARD TABLEOptional: No
Call by Reference: Yes
IS_OK - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for HR_ECM_READ_INFOTYPE 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_pernr | TYPE PSKEY-PERNR, " | |||
| lv_infotype_tab | TYPE STANDARD TABLE, " | |||
| lv_infty | TYPE PSKEY-INFTY, " | |||
| lv_is_ok | TYPE BOOLE_D, " | |||
| lv_subty | TYPE PSKEY-SUBTY, " '*' | |||
| lv_objps | TYPE OBJPS, " '*' | |||
| lv_sprps | TYPE PSKEY-SPRPS, " ' ' | |||
| lv_begda | TYPE PSKEY-BEGDA, " '18000101' | |||
| lv_endda | TYPE PSKEY-ENDDA, " '99991231' | |||
| lv_no_auth_check | TYPE BOOLE_D, " ' ' | |||
| lv_message_handler | TYPE IF_HRPA_MESSAGE_HANDLER. " |
|   CALL FUNCTION 'HR_ECM_READ_INFOTYPE' "Read Several Records of an Employee Infotype |
| EXPORTING | ||
| PERNR | = lv_pernr | |
| INFTY | = lv_infty | |
| SUBTY | = lv_subty | |
| OBJPS | = lv_objps | |
| SPRPS | = lv_sprps | |
| BEGDA | = lv_begda | |
| ENDDA | = lv_endda | |
| NO_AUTH_CHECK | = lv_no_auth_check | |
| MESSAGE_HANDLER | = lv_message_handler | |
| IMPORTING | ||
| INFOTYPE_TAB | = lv_infotype_tab | |
| IS_OK | = lv_is_ok | |
| . " HR_ECM_READ_INFOTYPE | ||
ABAP code using 7.40 inline data declarations to call FM HR_ECM_READ_INFOTYPE
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 PERNR FROM PSKEY INTO @DATA(ld_pernr). | ||||
| "SELECT single INFTY FROM PSKEY INTO @DATA(ld_infty). | ||||
| "SELECT single SUBTY FROM PSKEY INTO @DATA(ld_subty). | ||||
| DATA(ld_subty) | = '*'. | |||
| DATA(ld_objps) | = '*'. | |||
| "SELECT single SPRPS FROM PSKEY INTO @DATA(ld_sprps). | ||||
| DATA(ld_sprps) | = ' '. | |||
| "SELECT single BEGDA FROM PSKEY INTO @DATA(ld_begda). | ||||
| DATA(ld_begda) | = '18000101'. | |||
| "SELECT single ENDDA FROM PSKEY INTO @DATA(ld_endda). | ||||
| DATA(ld_endda) | = '99991231'. | |||
| DATA(ld_no_auth_check) | = ' '. | |||
Search for further information about these or an SAP related objects