SAP BAPI_COSTESTIMATE_GETLIST Function Module for Determine Cost Estimate Lists
BAPI_COSTESTIMATE_GETLIST is a standard bapi costestimate getlist SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Cost Estimate Lists 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 costestimate getlist FM, simply by entering the name BAPI_COSTESTIMATE_GETLIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: 2044
Program Name: SAPL2044
Main Program: SAPL2044
Appliation area: K
Release date: 14-Jul-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_COSTESTIMATE_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 'BAPI_COSTESTIMATE_GETLIST'"Determine Cost Estimate Lists.
EXPORTING
* COST_ESTIMATE = '01' "Costing
* MAXROWS = 999999999 "Maximum Number of Lines of Hits
IMPORTING
RETURN = "Confirmations
TABLES
* COSTING_VARIANT = "Costing Variant
* MATERIAL = "Material
* PLANT = "Plant
* VALIDITY_FROM = "Valid from
* COSTING_STATUS = "Costing Status
* COSTING_VERSION = "Costing Version
COST_ESTIMATE_LIST = "Cost Estimate List
* COSTINGRUN = "Costing Run
* COSTINGRUN_DATE = "Costing Run Date
IMPORTING Parameters details for BAPI_COSTESTIMATE_GETLIST
COST_ESTIMATE - Costing
Data type: BAPICOSTES-COSESTIMATDefault: '01'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MAXROWS - Maximum Number of Lines of Hits
Data type: BAPIMAXROWDefault: 999999999
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_COSTESTIMATE_GETLIST
RETURN - Confirmations
Data type: BAPIRETURNOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_COSTESTIMATE_GETLIST
COSTING_VARIANT - Costing Variant
Data type: BAPICSTGVAOptional: Yes
Call by Reference: No ( called with pass by value option)
MATERIAL - Material
Data type: BAPIMATERIOptional: Yes
Call by Reference: No ( called with pass by value option)
PLANT - Plant
Data type: BAPIPLANTOptional: Yes
Call by Reference: No ( called with pass by value option)
VALIDITY_FROM - Valid from
Data type: BAPIVALIDIOptional: Yes
Call by Reference: No ( called with pass by value option)
COSTING_STATUS - Costing Status
Data type: BAPICSTGSTOptional: Yes
Call by Reference: No ( called with pass by value option)
COSTING_VERSION - Costing Version
Data type: BAPICOSTINGVERSIONOptional: Yes
Call by Reference: No ( called with pass by value option)
COST_ESTIMATE_LIST - Cost Estimate List
Data type: BAPICOLISTOptional: No
Call by Reference: No ( called with pass by value option)
COSTINGRUN - Costing Run
Data type: BAPICOSTINGRUNOptional: Yes
Call by Reference: Yes
COSTINGRUN_DATE - Costing Run Date
Data type: BAPICOSTINGRUN_DATEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_COSTESTIMATE_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_return | TYPE BAPIRETURN, " | |||
| lv_cost_estimate | TYPE BAPICOSTES-COSESTIMAT, " '01' | |||
| lt_costing_variant | TYPE STANDARD TABLE OF BAPICSTGVA, " | |||
| lv_maxrows | TYPE BAPIMAXROW, " 999999999 | |||
| lt_material | TYPE STANDARD TABLE OF BAPIMATERI, " | |||
| lt_plant | TYPE STANDARD TABLE OF BAPIPLANT, " | |||
| lt_validity_from | TYPE STANDARD TABLE OF BAPIVALIDI, " | |||
| lt_costing_status | TYPE STANDARD TABLE OF BAPICSTGST, " | |||
| lt_costing_version | TYPE STANDARD TABLE OF BAPICOSTINGVERSION, " | |||
| lt_cost_estimate_list | TYPE STANDARD TABLE OF BAPICOLIST, " | |||
| lt_costingrun | TYPE STANDARD TABLE OF BAPICOSTINGRUN, " | |||
| lt_costingrun_date | TYPE STANDARD TABLE OF BAPICOSTINGRUN_DATE. " |
|   CALL FUNCTION 'BAPI_COSTESTIMATE_GETLIST' "Determine Cost Estimate Lists |
| EXPORTING | ||
| COST_ESTIMATE | = lv_cost_estimate | |
| MAXROWS | = lv_maxrows | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| COSTING_VARIANT | = lt_costing_variant | |
| MATERIAL | = lt_material | |
| PLANT | = lt_plant | |
| VALIDITY_FROM | = lt_validity_from | |
| COSTING_STATUS | = lt_costing_status | |
| COSTING_VERSION | = lt_costing_version | |
| COST_ESTIMATE_LIST | = lt_cost_estimate_list | |
| COSTINGRUN | = lt_costingrun | |
| COSTINGRUN_DATE | = lt_costingrun_date | |
| . " BAPI_COSTESTIMATE_GETLIST | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_COSTESTIMATE_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 COSESTIMAT FROM BAPICOSTES INTO @DATA(ld_cost_estimate). | ||||
| DATA(ld_cost_estimate) | = '01'. | |||
| DATA(ld_maxrows) | = 999999999. | |||
Search for further information about these or an SAP related objects