SAP CS_BI_BOM_CHANGE_BATCH_INPUT Function Module for Change bill of material via batch input
CS_BI_BOM_CHANGE_BATCH_INPUT is a standard cs bi bom change 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 Change bill of material 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 change batch input FM, simply by entering the name CS_BI_BOM_CHANGE_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_CHANGE_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_CHANGE_BATCH_INPUT'"Change bill of material via batch input.
EXPORTING
* BDC_FLAG = ' ' "Create flag batch input session or CALL TR_
BOM_HEADER = "Changed BOM header data
* CLOSE_GROUP = 'X' "
* COMMIT_WORK = ' ' "
GROUP_DATA = "General session data
* INTERNAL_FIELDS = ' ' "'X': Fields transferred in internal format
* NEW_GROUP = 'X' "
* TCODE_MODE = 'N' "Processing mode for transaction
* TCODE_UPDATE = 'S' "Update mode for transaction
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_ITEM = "Changed BOM items
* BOM_SUB_ITEM = "Changed BOM sub-items
IMPORTING Parameters details for CS_BI_BOM_CHANGE_BATCH_INPUT
BDC_FLAG - Create flag batch input session or CALL TR_
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
BOM_HEADER - Changed BOM header data
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CLOSE_GROUP -
Data type: CSDATA-XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
COMMIT_WORK -
Data type: CSDATA-XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
GROUP_DATA - General session data
Data type: BGR00Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_FIELDS - 'X': Fields transferred in internal format
Data type: CSDATA-XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NEW_GROUP -
Data type: CSDATA-XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TCODE_MODE - Processing mode for transaction
Data type:Default: 'N'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TCODE_UPDATE - Update mode for transaction
Data type:Default: 'S'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CS_BI_BOM_CHANGE_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_CHANGE_BATCH_INPUT
BOM_ITEM - Changed BOM items
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
BOM_SUB_ITEM - Changed BOM sub-items
Data type: BICSUOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CS_BI_BOM_CHANGE_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_item | TYPE STANDARD TABLE OF T100, " | |||
| lv_msgno | TYPE T100-MSGNR, " | |||
| lv_bom_header | TYPE T100, " | |||
| lt_bom_sub_item | TYPE STANDARD TABLE OF BICSU, " | |||
| lv_msgty | TYPE SY-MSGTY, " | |||
| lv_close_group | TYPE CSDATA-XFELD, " 'X' | |||
| lv_msgv1 | TYPE SY-MSGV1, " | |||
| lv_commit_work | TYPE CSDATA-XFELD, " SPACE | |||
| lv_msgv2 | TYPE SY-MSGV2, " | |||
| lv_group_data | TYPE BGR00, " | |||
| lv_msgv3 | TYPE SY-MSGV3, " | |||
| lv_internal_fields | TYPE CSDATA-XFELD, " SPACE | |||
| lv_msgv4 | TYPE SY-MSGV4, " | |||
| lv_new_group | TYPE CSDATA-XFELD, " 'X' | |||
| lv_tcode_mode | TYPE CSDATA, " 'N' | |||
| lv_tcode_update | TYPE CSDATA. " 'S' |
|   CALL FUNCTION 'CS_BI_BOM_CHANGE_BATCH_INPUT' "Change bill of material via batch input |
| EXPORTING | ||
| BDC_FLAG | = lv_bdc_flag | |
| BOM_HEADER | = lv_bom_header | |
| CLOSE_GROUP | = lv_close_group | |
| COMMIT_WORK | = lv_commit_work | |
| GROUP_DATA | = lv_group_data | |
| INTERNAL_FIELDS | = lv_internal_fields | |
| NEW_GROUP | = lv_new_group | |
| 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_ITEM | = lt_bom_item | |
| BOM_SUB_ITEM | = lt_bom_sub_item | |
| . " CS_BI_BOM_CHANGE_BATCH_INPUT | ||
ABAP code using 7.40 inline data declarations to call FM CS_BI_BOM_CHANGE_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 MSGTY FROM SY INTO @DATA(ld_msgty). | ||||
| "SELECT single XFELD FROM CSDATA INTO @DATA(ld_close_group). | ||||
| DATA(ld_close_group) | = 'X'. | |||
| "SELECT single MSGV1 FROM SY INTO @DATA(ld_msgv1). | ||||
| "SELECT single XFELD FROM CSDATA INTO @DATA(ld_commit_work). | ||||
| DATA(ld_commit_work) | = ' '. | |||
| "SELECT single MSGV2 FROM SY INTO @DATA(ld_msgv2). | ||||
| "SELECT single MSGV3 FROM SY INTO @DATA(ld_msgv3). | ||||
| "SELECT single XFELD FROM CSDATA INTO @DATA(ld_internal_fields). | ||||
| DATA(ld_internal_fields) | = ' '. | |||
| "SELECT single MSGV4 FROM SY INTO @DATA(ld_msgv4). | ||||
| "SELECT single XFELD FROM CSDATA INTO @DATA(ld_new_group). | ||||
| DATA(ld_new_group) | = 'X'. | |||
| DATA(ld_tcode_mode) | = 'N'. | |||
| DATA(ld_tcode_update) | = 'S'. | |||
Search for further information about these or an SAP related objects