SAP CS_BC_BOM_CHANGE_BATCH_INPUT Function Module for Transfer BOM changes via batch input









CS_BC_BOM_CHANGE_BATCH_INPUT is a standard cs bc 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 Transfer BOM changes 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 bc bom change batch input FM, simply by entering the name CS_BC_BOM_CHANGE_BATCH_INPUT into the relevant SAP transaction such as SE37 or SE38.

Function Group: CSBC
Program Name: SAPLCSBC
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function CS_BC_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_BC_BOM_CHANGE_BATCH_INPUT'"Transfer BOM changes via batch input
  EXPORTING
*  BDC_FLAG = ' ' "Create flag batch input session or CALL TR_
   BOM_HEADER =  "Changed BOM header data
*  CAD_FLAG = ' ' "
*  CLOSE_GROUP = ' ' "Indicator: close session
*  COMMIT_WORK = ' ' "
   GROUP_DATA =  "General session data
*  NEW_GROUP = ' ' "Indicator: open new session
*  TCODE_MODE = 'N' "Processing mode for transaction
*  TCODE_UPDATE = 'A' "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
   NEW_GROUP_OUT =  "Indicator: open new session

TABLES
   BOM_ITEM =  "Changed BOM items
*  BOM_SUB_ITEM =  "Changed BOM sub-items
.



IMPORTING Parameters details for CS_BC_BOM_CHANGE_BATCH_INPUT

BDC_FLAG - Create flag batch input session or CALL TR_

Data type: CSDATA-XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

BOM_HEADER - Changed BOM header data

Data type: BICSK
Optional: No
Call by Reference: No ( called with pass by value option)

CAD_FLAG -

Data type: CSDATA-XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CLOSE_GROUP - Indicator: close session

Data type: CSDATA-XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

COMMIT_WORK -

Data type: CSDATA-XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

GROUP_DATA - General session data

Data type: BGR00
Optional: No
Call by Reference: No ( called with pass by value option)

NEW_GROUP - Indicator: open new session

Data type: CSDATA-XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TCODE_MODE - Processing mode for transaction

Data type: CSDATA-XFELD
Default: 'N'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TCODE_UPDATE - Update mode for transaction

Data type: CSDATA-XFELD
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CS_BC_BOM_CHANGE_BATCH_INPUT

MSGID - Message ID

Data type: T100-ARBGB
Optional: No
Call by Reference: No ( called with pass by value option)

MSGNO - Message number

Data type: T100-MSGNR
Optional: No
Call by Reference: No ( called with pass by value option)

MSGTY - Message type

Data type: SY-MSGTY
Optional: No
Call by Reference: No ( called with pass by value option)

MSGV1 - Message variable 1

Data type: SY-MSGV1
Optional: No
Call by Reference: No ( called with pass by value option)

MSGV2 - Message variable 2

Data type: SY-MSGV2
Optional: No
Call by Reference: No ( called with pass by value option)

MSGV3 - Message variable 3

Data type: SY-MSGV3
Optional: No
Call by Reference: No ( called with pass by value option)

MSGV4 - Message variable 4

Data type: SY-MSGV4
Optional: No
Call by Reference: No ( called with pass by value option)

NEW_GROUP_OUT - Indicator: open new session

Data type: CSDATA-XFELD
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for CS_BC_BOM_CHANGE_BATCH_INPUT

BOM_ITEM - Changed BOM items

Data type: BICSP
Optional: No
Call by Reference: No ( called with pass by value option)

BOM_SUB_ITEM - Changed BOM sub-items

Data type: BICSU
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CS_BC_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 CSDATA-XFELD, "   SPACE
lt_bom_item  TYPE STANDARD TABLE OF BICSP, "   
lv_msgno  TYPE T100-MSGNR, "   
lv_bom_header  TYPE BICSK, "   
lt_bom_sub_item  TYPE STANDARD TABLE OF BICSU, "   
lv_msgty  TYPE SY-MSGTY, "   
lv_cad_flag  TYPE CSDATA-XFELD, "   SPACE
lv_msgv1  TYPE SY-MSGV1, "   
lv_close_group  TYPE CSDATA-XFELD, "   SPACE
lv_msgv2  TYPE SY-MSGV2, "   
lv_commit_work  TYPE CSDATA-XFELD, "   SPACE
lv_msgv3  TYPE SY-MSGV3, "   
lv_group_data  TYPE BGR00, "   
lv_msgv4  TYPE SY-MSGV4, "   
lv_new_group  TYPE CSDATA-XFELD, "   SPACE
lv_tcode_mode  TYPE CSDATA-XFELD, "   'N'
lv_new_group_out  TYPE CSDATA-XFELD, "   
lv_tcode_update  TYPE CSDATA-XFELD. "   'A'

  CALL FUNCTION 'CS_BC_BOM_CHANGE_BATCH_INPUT'  "Transfer BOM changes via batch input
    EXPORTING
         BDC_FLAG = lv_bdc_flag
         BOM_HEADER = lv_bom_header
         CAD_FLAG = lv_cad_flag
         CLOSE_GROUP = lv_close_group
         COMMIT_WORK = lv_commit_work
         GROUP_DATA = lv_group_data
         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
         NEW_GROUP_OUT = lv_new_group_out
    TABLES
         BOM_ITEM = lt_bom_item
         BOM_SUB_ITEM = lt_bom_sub_item
. " CS_BC_BOM_CHANGE_BATCH_INPUT




ABAP code using 7.40 inline data declarations to call FM CS_BC_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).
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_bdc_flag).
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_cad_flag).
DATA(ld_cad_flag) = ' '.
 
"SELECT single MSGV1 FROM SY INTO @DATA(ld_msgv1).
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_close_group).
DATA(ld_close_group) = ' '.
 
"SELECT single MSGV2 FROM SY INTO @DATA(ld_msgv2).
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_commit_work).
DATA(ld_commit_work) = ' '.
 
"SELECT single MSGV3 FROM SY INTO @DATA(ld_msgv3).
 
 
"SELECT single MSGV4 FROM SY INTO @DATA(ld_msgv4).
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_new_group).
DATA(ld_new_group) = ' '.
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_tcode_mode).
DATA(ld_tcode_mode) = 'N'.
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_new_group_out).
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_tcode_update).
DATA(ld_tcode_update) = 'A'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!