SAP EXIT_SAPLRHBX_003 Function Module for User-Defined Enhancement of 'Employee' List
EXIT_SAPLRHBX_003 is a standard exit saplrhbx 003 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for User-Defined Enhancement of 'Employee' List 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 exit saplrhbx 003 FM, simply by entering the name EXIT_SAPLRHBX_003 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XPMC
Program Name: SAPLXPMC
Main Program:
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function EXIT_SAPLRHBX_003 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 'EXIT_SAPLRHBX_003'"User-Defined Enhancement of 'Employee' List.
EXPORTING
PLVAR = "Plan version of object selected
OTYPE = "Object type of object selected
OBJID = "Object ID of object selected
BEGDA = "Start date of object selected
ENDDA = "End date of object selected
ISTAT = "Status of object selected
TABLES
MORE_INFO_TAB = "Table containing additional information
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.RH_PM_BUDGET_STRUCTURE_SORT
RH_PM_CHECK_BUDGET_PURPOSE
RH_PM_CHECK_EXISTING_PURPOSE
RH_PM_CREATE_BUDGET_PURPOSE
RH_PM_DISPLAY_BUDGET_PURPOSE
RH_PM_EMPLOYEE_CARD_MAINTAIN
RH_PM_EMPLOYEE_CARD_START
RH_PM_SEARCH_MODE_FOR_POSITION
RH_PM_SELECT_WITH_PURPOSE
IMPORTING Parameters details for EXIT_SAPLRHBX_003
PLVAR - Plan version of object selected
Data type: P1000-PLVAROptional: No
Call by Reference: No ( called with pass by value option)
OTYPE - Object type of object selected
Data type: P1000-OTYPEOptional: No
Call by Reference: No ( called with pass by value option)
OBJID - Object ID of object selected
Data type: P1000-OBJIDOptional: No
Call by Reference: No ( called with pass by value option)
BEGDA - Start date of object selected
Data type: P1000-BEGDAOptional: No
Call by Reference: No ( called with pass by value option)
ENDDA - End date of object selected
Data type: P1000-ENDDAOptional: No
Call by Reference: No ( called with pass by value option)
ISTAT - Status of object selected
Data type: P1000-ISTATOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPLRHBX_003
MORE_INFO_TAB - Table containing additional information
Data type: STREEATTROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLRHBX_003 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_plvar | TYPE P1000-PLVAR, " | |||
| lt_more_info_tab | TYPE STANDARD TABLE OF STREEATTR, " | |||
| lv_otype | TYPE P1000-OTYPE, " | |||
| lv_objid | TYPE P1000-OBJID, " | |||
| lv_begda | TYPE P1000-BEGDA, " | |||
| lv_endda | TYPE P1000-ENDDA, " | |||
| lv_istat | TYPE P1000-ISTAT. " |
|   CALL FUNCTION 'EXIT_SAPLRHBX_003' "User-Defined Enhancement of 'Employee' List |
| EXPORTING | ||
| PLVAR | = lv_plvar | |
| OTYPE | = lv_otype | |
| OBJID | = lv_objid | |
| BEGDA | = lv_begda | |
| ENDDA | = lv_endda | |
| ISTAT | = lv_istat | |
| TABLES | ||
| MORE_INFO_TAB | = lt_more_info_tab | |
| . " EXIT_SAPLRHBX_003 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLRHBX_003
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 PLVAR FROM P1000 INTO @DATA(ld_plvar). | ||||
| "SELECT single OTYPE FROM P1000 INTO @DATA(ld_otype). | ||||
| "SELECT single OBJID FROM P1000 INTO @DATA(ld_objid). | ||||
| "SELECT single BEGDA FROM P1000 INTO @DATA(ld_begda). | ||||
| "SELECT single ENDDA FROM P1000 INTO @DATA(ld_endda). | ||||
| "SELECT single ISTAT FROM P1000 INTO @DATA(ld_istat). | ||||
Search for further information about these or an SAP related objects