SAP HR_COMBINED_SELECTION Function Module for









HR_COMBINED_SELECTION is a standard hr combined selection 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 hr combined selection FM, simply by entering the name HR_COMBINED_SELECTION into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRBAS00GENERICSELECTION
Program Name: SAPLHRBAS00GENERICSELECTION
Main Program: SAPLHRBAS00GENERICSELECTION
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function HR_COMBINED_SELECTION 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_COMBINED_SELECTION'"
EXPORTING
* SELID = "
* BEGDA = '18000101' "
* ENDDA = '99991231' "
* PLVAR = "
* OTYPE = "
* NO_POPUP = ' ' "
* AUTHORITY_CHECK = 'X' "
* NO_MESSAGE = ' ' "

TABLES
* TABLECONDITIONS = "
* STRUCCONDITIONS = "
* COMBINECONDITIONS = "
* FUNCCONDITIONS = "
* OBJECTS_IN = "
OBJECTS_FOUND = "
* PARAMS_IN = "
* PARAMS_OUT = "

EXCEPTIONS
WRONG_DEFINITION = 1 SELID_NOT_FOUND = 2 MISSING_OTYPE = 3
.



IMPORTING Parameters details for HR_COMBINED_SELECTION

SELID -

Data type: HRSEL_IDS-SELID
Optional: Yes
Call by Reference: No ( called with pass by value option)

BEGDA -

Data type: D
Default: '18000101'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ENDDA -

Data type: D
Default: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PLVAR -

Data type: PLVAR
Optional: Yes
Call by Reference: Yes

OTYPE -

Data type: OTYPE
Optional: Yes
Call by Reference: Yes

NO_POPUP -

Data type: FLAG_X
Default: SPACE
Optional: Yes
Call by Reference: Yes

AUTHORITY_CHECK -

Data type: FLAG_X
Default: 'X'
Optional: Yes
Call by Reference: Yes

NO_MESSAGE -

Data type: FLAG_X
Default: ' '
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for HR_COMBINED_SELECTION

TABLECONDITIONS -

Data type: HRTABLECONDITION_T
Optional: Yes
Call by Reference: Yes

STRUCCONDITIONS -

Data type: HRSTRUCCONDITION_TAB
Optional: Yes
Call by Reference: Yes

COMBINECONDITIONS -

Data type: HRCOMBINECONDITIONS_TAB
Optional: Yes
Call by Reference: Yes

FUNCCONDITIONS -

Data type: HRFUNCCONDITION_TAB
Optional: Yes
Call by Reference: Yes

OBJECTS_IN -

Data type: HRSOBID
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECTS_FOUND -

Data type: HRSOBID
Optional: No
Call by Reference: No ( called with pass by value option)

PARAMS_IN -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

PARAMS_OUT -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

WRONG_DEFINITION -

Data type:
Optional: No
Call by Reference: Yes

SELID_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

MISSING_OTYPE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for HR_COMBINED_SELECTION 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_selid  TYPE HRSEL_IDS-SELID, "   
lt_tableconditions  TYPE STANDARD TABLE OF HRTABLECONDITION_T, "   
lv_wrong_definition  TYPE HRTABLECONDITION_T, "   
lv_begda  TYPE D, "   '18000101'
lv_selid_not_found  TYPE D, "   
lt_strucconditions  TYPE STANDARD TABLE OF HRSTRUCCONDITION_TAB, "   
lv_endda  TYPE D, "   '99991231'
lv_missing_otype  TYPE D, "   
lt_combineconditions  TYPE STANDARD TABLE OF HRCOMBINECONDITIONS_TAB, "   
lv_plvar  TYPE PLVAR, "   
lt_funcconditions  TYPE STANDARD TABLE OF HRFUNCCONDITION_TAB, "   
lv_otype  TYPE OTYPE, "   
lt_objects_in  TYPE STANDARD TABLE OF HRSOBID, "   
lv_no_popup  TYPE FLAG_X, "   SPACE
lt_objects_found  TYPE STANDARD TABLE OF HRSOBID, "   
lt_params_in  TYPE STANDARD TABLE OF HRSOBID, "   
lv_authority_check  TYPE FLAG_X, "   'X'
lv_no_message  TYPE FLAG_X, "   ' '
lt_params_out  TYPE STANDARD TABLE OF FLAG_X. "   

  CALL FUNCTION 'HR_COMBINED_SELECTION'  "
    EXPORTING
         SELID = lv_selid
         BEGDA = lv_begda
         ENDDA = lv_endda
         PLVAR = lv_plvar
         OTYPE = lv_otype
         NO_POPUP = lv_no_popup
         AUTHORITY_CHECK = lv_authority_check
         NO_MESSAGE = lv_no_message
    TABLES
         TABLECONDITIONS = lt_tableconditions
         STRUCCONDITIONS = lt_strucconditions
         COMBINECONDITIONS = lt_combineconditions
         FUNCCONDITIONS = lt_funcconditions
         OBJECTS_IN = lt_objects_in
         OBJECTS_FOUND = lt_objects_found
         PARAMS_IN = lt_params_in
         PARAMS_OUT = lt_params_out
    EXCEPTIONS
        WRONG_DEFINITION = 1
        SELID_NOT_FOUND = 2
        MISSING_OTYPE = 3
. " HR_COMBINED_SELECTION




ABAP code using 7.40 inline data declarations to call FM HR_COMBINED_SELECTION

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 SELID FROM HRSEL_IDS INTO @DATA(ld_selid).
 
 
 
DATA(ld_begda) = '18000101'.
 
 
 
DATA(ld_endda) = '99991231'.
 
 
 
 
 
 
 
DATA(ld_no_popup) = ' '.
 
 
 
DATA(ld_authority_check) = 'X'.
 
DATA(ld_no_message) = ' '.
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!