SAP BAPI_WAGE_COMP_EXT_GET_LIST Function Module for List of Keys for External Wage Components
BAPI_WAGE_COMP_EXT_GET_LIST is a standard bapi wage comp ext get list SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for List of Keys for External Wage Components 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 bapi wage comp ext get list FM, simply by entering the name BAPI_WAGE_COMP_EXT_GET_LIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: PCIF_EXTSALARY
Program Name: SAPLPCIF_EXTSALARY
Main Program: SAPLPCIF_EXTSALARY
Appliation area:
Release date: 18-May-2001
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_WAGE_COMP_EXT_GET_LIST 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 'BAPI_WAGE_COMP_EXT_GET_LIST'"List of Keys for External Wage Components.
EXPORTING
ORIGIN = "Origin of Data
* EMPLOYEENUMBER = "Personnel Number
* REFERENCENUMBER = "Reference Number
* FROMDATE = '19900101' "Start of Time Interval for Selection
* TODATE = '99991231' "End of Time Interval for Selection
TABLES
KEY = "Key for External Wage Component
RETURN = "Return Parameter
* EXTENSIONIN = "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
IMPORTING Parameters details for BAPI_WAGE_COMP_EXT_GET_LIST
ORIGIN - Origin of Data
Data type: BAPI_WAGE_COMP_DATA-ORIGINOptional: No
Call by Reference: No ( called with pass by value option)
EMPLOYEENUMBER - Personnel Number
Data type: BAPI_WAGE_COMP_KEY-EMPLOYEENUMBEROptional: Yes
Call by Reference: No ( called with pass by value option)
REFERENCENUMBER - Reference Number
Data type: BAPI_WAGE_COMP_DATA-REFERENCE_NROptional: Yes
Call by Reference: No ( called with pass by value option)
FROMDATE - Start of Time Interval for Selection
Data type: BAPI_WAGE_COMP_KEY-VALIDITYBEGINDefault: '19900101'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TODATE - End of Time Interval for Selection
Data type: BAPI_WAGE_COMP_KEY-VALIDITYENDDefault: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_WAGE_COMP_EXT_GET_LIST
KEY - Key for External Wage Component
Data type: BAPI_WAGE_COMP_KEYOptional: No
Call by Reference: Yes
RETURN - Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: Yes
EXTENSIONIN - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_WAGE_COMP_EXT_GET_LIST 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: | ||||
| lt_key | TYPE STANDARD TABLE OF BAPI_WAGE_COMP_KEY, " | |||
| lv_origin | TYPE BAPI_WAGE_COMP_DATA-ORIGIN, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_employeenumber | TYPE BAPI_WAGE_COMP_KEY-EMPLOYEENUMBER, " | |||
| lt_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lv_referencenumber | TYPE BAPI_WAGE_COMP_DATA-REFERENCE_NR, " | |||
| lv_fromdate | TYPE BAPI_WAGE_COMP_KEY-VALIDITYBEGIN, " '19900101' | |||
| lv_todate | TYPE BAPI_WAGE_COMP_KEY-VALIDITYEND. " '99991231' |
|   CALL FUNCTION 'BAPI_WAGE_COMP_EXT_GET_LIST' "List of Keys for External Wage Components |
| EXPORTING | ||
| ORIGIN | = lv_origin | |
| EMPLOYEENUMBER | = lv_employeenumber | |
| REFERENCENUMBER | = lv_referencenumber | |
| FROMDATE | = lv_fromdate | |
| TODATE | = lv_todate | |
| TABLES | ||
| KEY | = lt_key | |
| RETURN | = lt_return | |
| EXTENSIONIN | = lt_extensionin | |
| . " BAPI_WAGE_COMP_EXT_GET_LIST | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_WAGE_COMP_EXT_GET_LIST
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 ORIGIN FROM BAPI_WAGE_COMP_DATA INTO @DATA(ld_origin). | ||||
| "SELECT single EMPLOYEENUMBER FROM BAPI_WAGE_COMP_KEY INTO @DATA(ld_employeenumber). | ||||
| "SELECT single REFERENCE_NR FROM BAPI_WAGE_COMP_DATA INTO @DATA(ld_referencenumber). | ||||
| "SELECT single VALIDITYBEGIN FROM BAPI_WAGE_COMP_KEY INTO @DATA(ld_fromdate). | ||||
| DATA(ld_fromdate) | = '19900101'. | |||
| "SELECT single VALIDITYEND FROM BAPI_WAGE_COMP_KEY INTO @DATA(ld_todate). | ||||
| DATA(ld_todate) | = '99991231'. | |||
Search for further information about these or an SAP related objects