SAP CS_BI_BOM_CREATE_BATCH_INPUT Function Module for Create BOM Via Batch Input
CS_BI_BOM_CREATE_BATCH_INPUT is a standard cs bi bom create batch input SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create BOM Via Batch Input 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 cs bi bom create batch input FM, simply by entering the name CS_BI_BOM_CREATE_BATCH_INPUT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CSBI
Program Name: SAPLCSBI
Main Program: SAPLCSBI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CS_BI_BOM_CREATE_BATCH_INPUT 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 'CS_BI_BOM_CREATE_BATCH_INPUT'"Create BOM Via Batch Input.
EXPORTING
* BDC_FLAG = ' ' "' ' CALL TRANSACTION USING, 'X' Create session
* COMMIT_FLAG = ' ' "Indicator: perform COMMIT WORK
GROUP_DATA = "Folder Data
* TCODE_MODE = 'N' "Processing mode for CALL TRANSACTION USING
* TCODE_UPDATE = 'S' "Synchronous or asynchronous update
IMPORTING
MSGID = "Message ID
MSGNO = "Message number
MSGTY = "Message type
MSGV1 = "Message variable 1
MSGV2 = "Message variable 2
MSGV3 = "Message variable 3
MSGV4 = "Message variable 4
TABLES
BOM_HEADER = "BOM header data
BOM_ITEM = "BOM item data
BOM_SUB_ITEM = "BOM sub-item data
IMPORTING Parameters details for CS_BI_BOM_CREATE_BATCH_INPUT
BDC_FLAG - ' ' CALL TRANSACTION USING, 'X' Create session
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
COMMIT_FLAG - Indicator: perform COMMIT WORK
Data type: CSDATA-XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
GROUP_DATA - Folder Data
Data type: BGR00Optional: No
Call by Reference: No ( called with pass by value option)
TCODE_MODE - Processing mode for CALL TRANSACTION USING
Data type:Default: 'N'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TCODE_UPDATE - Synchronous or asynchronous update
Data type:Default: 'S'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CS_BI_BOM_CREATE_BATCH_INPUT
MSGID - Message ID
Data type: T100-ARBGBOptional: No
Call by Reference: No ( called with pass by value option)
MSGNO - Message number
Data type: T100-MSGNROptional: No
Call by Reference: No ( called with pass by value option)
MSGTY - Message type
Data type: SY-MSGTYOptional: No
Call by Reference: No ( called with pass by value option)
MSGV1 - Message variable 1
Data type: SY-MSGV1Optional: No
Call by Reference: No ( called with pass by value option)
MSGV2 - Message variable 2
Data type: SY-MSGV2Optional: No
Call by Reference: No ( called with pass by value option)
MSGV3 - Message variable 3
Data type: SY-MSGV3Optional: No
Call by Reference: No ( called with pass by value option)
MSGV4 - Message variable 4
Data type: SY-MSGV4Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CS_BI_BOM_CREATE_BATCH_INPUT
BOM_HEADER - BOM header data
Data type: BICSKOptional: No
Call by Reference: No ( called with pass by value option)
BOM_ITEM - BOM item data
Data type: BICSPOptional: No
Call by Reference: No ( called with pass by value option)
BOM_SUB_ITEM - BOM sub-item data
Data type: BICSUOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CS_BI_BOM_CREATE_BATCH_INPUT 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_msgid | TYPE T100-ARBGB, " | |||
| lv_bdc_flag | TYPE T100, " SPACE | |||
| lt_bom_header | TYPE STANDARD TABLE OF BICSK, " | |||
| lv_msgno | TYPE T100-MSGNR, " | |||
| lt_bom_item | TYPE STANDARD TABLE OF BICSP, " | |||
| lv_commit_flag | TYPE CSDATA-XFELD, " SPACE | |||
| lv_msgty | TYPE SY-MSGTY, " | |||
| lv_group_data | TYPE BGR00, " | |||
| lt_bom_sub_item | TYPE STANDARD TABLE OF BICSU, " | |||
| lv_msgv1 | TYPE SY-MSGV1, " | |||
| lv_tcode_mode | TYPE SY, " 'N' | |||
| lv_msgv2 | TYPE SY-MSGV2, " | |||
| lv_tcode_update | TYPE SY, " 'S' | |||
| lv_msgv3 | TYPE SY-MSGV3, " | |||
| lv_msgv4 | TYPE SY-MSGV4. " |
|   CALL FUNCTION 'CS_BI_BOM_CREATE_BATCH_INPUT' "Create BOM Via Batch Input |
| EXPORTING | ||
| BDC_FLAG | = lv_bdc_flag | |
| COMMIT_FLAG | = lv_commit_flag | |
| GROUP_DATA | = lv_group_data | |
| TCODE_MODE | = lv_tcode_mode | |
| TCODE_UPDATE | = lv_tcode_update | |
| IMPORTING | ||
| MSGID | = lv_msgid | |
| MSGNO | = lv_msgno | |
| MSGTY | = lv_msgty | |
| MSGV1 | = lv_msgv1 | |
| MSGV2 | = lv_msgv2 | |
| MSGV3 | = lv_msgv3 | |
| MSGV4 | = lv_msgv4 | |
| TABLES | ||
| BOM_HEADER | = lt_bom_header | |
| BOM_ITEM | = lt_bom_item | |
| BOM_SUB_ITEM | = lt_bom_sub_item | |
| . " CS_BI_BOM_CREATE_BATCH_INPUT | ||
ABAP code using 7.40 inline data declarations to call FM CS_BI_BOM_CREATE_BATCH_INPUT
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 ARBGB FROM T100 INTO @DATA(ld_msgid). | ||||
| DATA(ld_bdc_flag) | = ' '. | |||
| "SELECT single MSGNR FROM T100 INTO @DATA(ld_msgno). | ||||
| "SELECT single XFELD FROM CSDATA INTO @DATA(ld_commit_flag). | ||||
| DATA(ld_commit_flag) | = ' '. | |||
| "SELECT single MSGTY FROM SY INTO @DATA(ld_msgty). | ||||
| "SELECT single MSGV1 FROM SY INTO @DATA(ld_msgv1). | ||||
| DATA(ld_tcode_mode) | = 'N'. | |||
| "SELECT single MSGV2 FROM SY INTO @DATA(ld_msgv2). | ||||
| DATA(ld_tcode_update) | = 'S'. | |||
| "SELECT single MSGV3 FROM SY INTO @DATA(ld_msgv3). | ||||
| "SELECT single MSGV4 FROM SY INTO @DATA(ld_msgv4). | ||||
Search for further information about these or an SAP related objects