SAP BAPI_BOM_UPLOAD_SAVE Function Module for Main Module for BOM Update (Upload from CRM)
BAPI_BOM_UPLOAD_SAVE is a standard bapi bom upload save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Main Module for BOM Update (Upload from CRM) 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 bom upload save FM, simply by entering the name BAPI_BOM_UPLOAD_SAVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CSUL
Program Name: SAPLCSUL
Main Program:
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_BOM_UPLOAD_SAVE 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_BOM_UPLOAD_SAVE'"Main Module for BOM Update (Upload from CRM).
EXPORTING
IS_MAST = "Communication Structure MAST
IS_STZU = "Communication Structure STZU
IMPORTING
ES_RETURN = "BAPI Return Structure
TABLES
IT_STKO = "Table for Communication Structure STKO
IT_STPO = "Table for Communication Structure STPO
IT_STAS = "Table for Communication Structure STAS
IMPORTING Parameters details for BAPI_BOM_UPLOAD_SAVE
IS_MAST - Communication Structure MAST
Data type: BAPIBOMMSTOptional: No
Call by Reference: No ( called with pass by value option)
IS_STZU - Communication Structure STZU
Data type: BAPIBOMSTZOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_BOM_UPLOAD_SAVE
ES_RETURN - BAPI Return Structure
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_BOM_UPLOAD_SAVE
IT_STKO - Table for Communication Structure STKO
Data type: BAPIBOMSTKOptional: No
Call by Reference: No ( called with pass by value option)
IT_STPO - Table for Communication Structure STPO
Data type: BAPIBOMSTPOptional: No
Call by Reference: No ( called with pass by value option)
IT_STAS - Table for Communication Structure STAS
Data type: BAPIBOMSTAOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_BOM_UPLOAD_SAVE 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_is_mast | TYPE BAPIBOMMST, " | |||
| lt_it_stko | TYPE STANDARD TABLE OF BAPIBOMSTK, " | |||
| lv_es_return | TYPE BAPIRET2, " | |||
| lv_is_stzu | TYPE BAPIBOMSTZ, " | |||
| lt_it_stpo | TYPE STANDARD TABLE OF BAPIBOMSTP, " | |||
| lt_it_stas | TYPE STANDARD TABLE OF BAPIBOMSTA. " |
|   CALL FUNCTION 'BAPI_BOM_UPLOAD_SAVE' "Main Module for BOM Update (Upload from CRM) |
| EXPORTING | ||
| IS_MAST | = lv_is_mast | |
| IS_STZU | = lv_is_stzu | |
| IMPORTING | ||
| ES_RETURN | = lv_es_return | |
| TABLES | ||
| IT_STKO | = lt_it_stko | |
| IT_STPO | = lt_it_stpo | |
| IT_STAS | = lt_it_stas | |
| . " BAPI_BOM_UPLOAD_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_BOM_UPLOAD_SAVE
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.Search for further information about these or an SAP related objects