SAP BAPI_COSTESTIMATE_ITEMIZATION Function Module for Determine Itemization for a Cost Estimate
BAPI_COSTESTIMATE_ITEMIZATION is a standard bapi costestimate itemization 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 Itemization for a Cost Estimate 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 itemization FM, simply by entering the name BAPI_COSTESTIMATE_ITEMIZATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: 2044
Program Name: SAPL2044
Main Program: SAPL2044
Appliation area: K
Release date: 20-Sep-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_COSTESTIMATE_ITEMIZATION 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_ITEMIZATION'"Determine Itemization for a Cost Estimate.
EXPORTING
REFERENCEOBJECT = "Reference Object
COSTINGNUMBER = "Cost Estimate Number
COSTINGTYPE = "Costing Type
COSTINGDATE = "Costing Date
COSTINGVERSION = "Costing Version
VALUATIONVARIANT = "Valuation Variant
ENTEREDMANUALLY = "Additive Costs
IMPORTING
ITEMIZATION_HEADER = "Itemization Header
RETURN = "Confirmations
TABLES
ITEMIZATION_LIST = "List of Items in Itemization
IMPORTING Parameters details for BAPI_COSTESTIMATE_ITEMIZATION
REFERENCEOBJECT - Reference Object
Data type: BAPICOSTRE-REF_OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
COSTINGNUMBER - Cost Estimate Number
Data type: BAPICOSTRE-CSTG_NUMOptional: No
Call by Reference: No ( called with pass by value option)
COSTINGTYPE - Costing Type
Data type: BAPICOSTRE-CSTG_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
COSTINGDATE - Costing Date
Data type: BAPICOSTRE-CSTG_DATEOptional: No
Call by Reference: No ( called with pass by value option)
COSTINGVERSION - Costing Version
Data type: BAPICOSTRE-VERSIONOptional: No
Call by Reference: No ( called with pass by value option)
VALUATIONVARIANT - Valuation Variant
Data type: BAPICOSTRE-VLTN_VRNTOptional: No
Call by Reference: No ( called with pass by value option)
ENTEREDMANUALLY - Additive Costs
Data type: BAPICOSTRE-ENTER_MANOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_COSTESTIMATE_ITEMIZATION
ITEMIZATION_HEADER - Itemization Header
Data type: BAPIITEMIZATIONHEADEROptional: No
Call by Reference: No ( called with pass by value option)
RETURN - Confirmations
Data type: BAPIRETURNOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_COSTESTIMATE_ITEMIZATION
ITEMIZATION_LIST - List of Items in Itemization
Data type: BAPIITEMIZATIONLISTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_COSTESTIMATE_ITEMIZATION 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_referenceobject | TYPE BAPICOSTRE-REF_OBJECT, " | |||
| lt_itemization_list | TYPE STANDARD TABLE OF BAPIITEMIZATIONLIST, " | |||
| lv_itemization_header | TYPE BAPIITEMIZATIONHEADER, " | |||
| lv_return | TYPE BAPIRETURN, " | |||
| lv_costingnumber | TYPE BAPICOSTRE-CSTG_NUM, " | |||
| lv_costingtype | TYPE BAPICOSTRE-CSTG_TYPE, " | |||
| lv_costingdate | TYPE BAPICOSTRE-CSTG_DATE, " | |||
| lv_costingversion | TYPE BAPICOSTRE-VERSION, " | |||
| lv_valuationvariant | TYPE BAPICOSTRE-VLTN_VRNT, " | |||
| lv_enteredmanually | TYPE BAPICOSTRE-ENTER_MAN. " |
|   CALL FUNCTION 'BAPI_COSTESTIMATE_ITEMIZATION' "Determine Itemization for a Cost Estimate |
| EXPORTING | ||
| REFERENCEOBJECT | = lv_referenceobject | |
| COSTINGNUMBER | = lv_costingnumber | |
| COSTINGTYPE | = lv_costingtype | |
| COSTINGDATE | = lv_costingdate | |
| COSTINGVERSION | = lv_costingversion | |
| VALUATIONVARIANT | = lv_valuationvariant | |
| ENTEREDMANUALLY | = lv_enteredmanually | |
| IMPORTING | ||
| ITEMIZATION_HEADER | = lv_itemization_header | |
| RETURN | = lv_return | |
| TABLES | ||
| ITEMIZATION_LIST | = lt_itemization_list | |
| . " BAPI_COSTESTIMATE_ITEMIZATION | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_COSTESTIMATE_ITEMIZATION
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 REF_OBJECT FROM BAPICOSTRE INTO @DATA(ld_referenceobject). | ||||
| "SELECT single CSTG_NUM FROM BAPICOSTRE INTO @DATA(ld_costingnumber). | ||||
| "SELECT single CSTG_TYPE FROM BAPICOSTRE INTO @DATA(ld_costingtype). | ||||
| "SELECT single CSTG_DATE FROM BAPICOSTRE INTO @DATA(ld_costingdate). | ||||
| "SELECT single VERSION FROM BAPICOSTRE INTO @DATA(ld_costingversion). | ||||
| "SELECT single VLTN_VRNT FROM BAPICOSTRE INTO @DATA(ld_valuationvariant). | ||||
| "SELECT single ENTER_MAN FROM BAPICOSTRE INTO @DATA(ld_enteredmanually). | ||||
Search for further information about these or an SAP related objects