SAP K_COSTELEM_BAPI_GETLIST Function Module for
K_COSTELEM_BAPI_GETLIST is a standard k costelem bapi getlist 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 k costelem bapi getlist FM, simply by entering the name K_COSTELEM_BAPI_GETLIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: KMA4
Program Name: SAPLKMA4
Main Program: SAPLKMA4
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function K_COSTELEM_BAPI_GETLIST 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 'K_COSTELEM_BAPI_GETLIST'".
EXPORTING
CONTROLLINGAREA = "
* COSTELEMENT = "
* COSTELEMENTTO = "
* DATE = "
* DATETO = "
* COSTELEMENTGROUP = "
* CATEGORY = "
* CATEGORYTO = "
TABLES
COSTELEMENTLIST = "
RETURN = "
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLKMA4_001 Flow Logic PBO
EXIT_SAPLKMA4_002 Flow Logic PAI
IMPORTING Parameters details for K_COSTELEM_BAPI_GETLIST
CONTROLLINGAREA -
Data type: BAPI1030_GEN-CO_AREAOptional: No
Call by Reference: No ( called with pass by value option)
COSTELEMENT -
Data type: BAPI1030_GEN-COST_ELEMOptional: Yes
Call by Reference: No ( called with pass by value option)
COSTELEMENTTO -
Data type: BAPI1030_GEN-COST_ELEMOptional: Yes
Call by Reference: No ( called with pass by value option)
DATE -
Data type: BAPI1030_GEN-SOME_DATEOptional: Yes
Call by Reference: No ( called with pass by value option)
DATETO -
Data type: BAPI1030_GEN-SOME_DATEOptional: Yes
Call by Reference: No ( called with pass by value option)
COSTELEMENTGROUP -
Data type: BAPI1030_GEN-COST_ELEM_GRPOptional: Yes
Call by Reference: No ( called with pass by value option)
CATEGORY -
Data type: BAPI1030_GEN-CE_CATEGORYOptional: Yes
Call by Reference: No ( called with pass by value option)
CATEGORYTO -
Data type: BAPI1030_GEN-CE_CATEGORYOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for K_COSTELEM_BAPI_GETLIST
COSTELEMENTLIST -
Data type: BAPI1030_CELISTOptional: No
Call by Reference: No ( called with pass by value option)
RETURN -
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for K_COSTELEM_BAPI_GETLIST 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_controllingarea | TYPE BAPI1030_GEN-CO_AREA, " | |||
| lt_costelementlist | TYPE STANDARD TABLE OF BAPI1030_CELIST, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_costelement | TYPE BAPI1030_GEN-COST_ELEM, " | |||
| lv_costelementto | TYPE BAPI1030_GEN-COST_ELEM, " | |||
| lv_date | TYPE BAPI1030_GEN-SOME_DATE, " | |||
| lv_dateto | TYPE BAPI1030_GEN-SOME_DATE, " | |||
| lv_costelementgroup | TYPE BAPI1030_GEN-COST_ELEM_GRP, " | |||
| lv_category | TYPE BAPI1030_GEN-CE_CATEGORY, " | |||
| lv_categoryto | TYPE BAPI1030_GEN-CE_CATEGORY. " |
|   CALL FUNCTION 'K_COSTELEM_BAPI_GETLIST' " |
| EXPORTING | ||
| CONTROLLINGAREA | = lv_controllingarea | |
| COSTELEMENT | = lv_costelement | |
| COSTELEMENTTO | = lv_costelementto | |
| DATE | = lv_date | |
| DATETO | = lv_dateto | |
| COSTELEMENTGROUP | = lv_costelementgroup | |
| CATEGORY | = lv_category | |
| CATEGORYTO | = lv_categoryto | |
| TABLES | ||
| COSTELEMENTLIST | = lt_costelementlist | |
| RETURN | = lt_return | |
| . " K_COSTELEM_BAPI_GETLIST | ||
ABAP code using 7.40 inline data declarations to call FM K_COSTELEM_BAPI_GETLIST
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 CO_AREA FROM BAPI1030_GEN INTO @DATA(ld_controllingarea). | ||||
| "SELECT single COST_ELEM FROM BAPI1030_GEN INTO @DATA(ld_costelement). | ||||
| "SELECT single COST_ELEM FROM BAPI1030_GEN INTO @DATA(ld_costelementto). | ||||
| "SELECT single SOME_DATE FROM BAPI1030_GEN INTO @DATA(ld_date). | ||||
| "SELECT single SOME_DATE FROM BAPI1030_GEN INTO @DATA(ld_dateto). | ||||
| "SELECT single COST_ELEM_GRP FROM BAPI1030_GEN INTO @DATA(ld_costelementgroup). | ||||
| "SELECT single CE_CATEGORY FROM BAPI1030_GEN INTO @DATA(ld_category). | ||||
| "SELECT single CE_CATEGORY FROM BAPI1030_GEN INTO @DATA(ld_categoryto). | ||||
Search for further information about these or an SAP related objects