SAP CS_BC_COMPARE_TWO_BOM_VARIANTS Function Module for Compare two variant BOMs to determine non-variable parts









CS_BC_COMPARE_TWO_BOM_VARIANTS is a standard cs bc compare two bom variants SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Compare two variant BOMs to determine non-variable parts 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 compare two bom variants FM, simply by entering the name CS_BC_COMPARE_TWO_BOM_VARIANTS 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): Normal Function Module
Update:



Function CS_BC_COMPARE_TWO_BOM_VARIANTS 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_COMPARE_TWO_BOM_VARIANTS'"Compare two variant BOMs to determine non-variable parts
EXPORTING
BOM_HEADER = "BOM header data

IMPORTING
MSGID = "Message ID
MSGNO = "Message number
MSGTY = "Message type
MSGV1 = "Variable 1
MSGV2 = "Variable 2
MSGV3 = "Variable 3
MSGV4 = "Variable 4

TABLES
BOM_ITEM = "BOM items
BOM_SUB_ITEM = "BOM sub-items
NON_VARIANT_ITEMS = "Non-variable items
.



IMPORTING Parameters details for CS_BC_COMPARE_TWO_BOM_VARIANTS

BOM_HEADER - BOM header data

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

EXPORTING Parameters details for CS_BC_COMPARE_TWO_BOM_VARIANTS

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 - Variable 1

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

MSGV2 - Variable 2

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

MSGV3 - Variable 3

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

MSGV4 - Variable 4

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

TABLES Parameters details for CS_BC_COMPARE_TWO_BOM_VARIANTS

BOM_ITEM - BOM items

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

BOM_SUB_ITEM - BOM sub-items

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

NON_VARIANT_ITEMS - Non-variable items

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

Copy and paste ABAP code example for CS_BC_COMPARE_TWO_BOM_VARIANTS 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, "   
lt_bom_item  TYPE STANDARD TABLE OF BICSP, "   
lv_bom_header  TYPE BICSK, "   
lv_msgno  TYPE T100-MSGNR, "   
lt_bom_sub_item  TYPE STANDARD TABLE OF BICSU, "   
lv_msgty  TYPE SY-MSGTY, "   
lt_non_variant_items  TYPE STANDARD TABLE OF SY, "   
lv_msgv1  TYPE SY-MSGV1, "   
lv_msgv2  TYPE SY-MSGV2, "   
lv_msgv3  TYPE SY-MSGV3, "   
lv_msgv4  TYPE SY-MSGV4. "   

  CALL FUNCTION 'CS_BC_COMPARE_TWO_BOM_VARIANTS'  "Compare two variant BOMs to determine non-variable parts
    EXPORTING
         BOM_HEADER = lv_bom_header
    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
         NON_VARIANT_ITEMS = lt_non_variant_items
. " CS_BC_COMPARE_TWO_BOM_VARIANTS




ABAP code using 7.40 inline data declarations to call FM CS_BC_COMPARE_TWO_BOM_VARIANTS

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 MSGNR FROM T100 INTO @DATA(ld_msgno).
 
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_msgty).
 
 
"SELECT single MSGV1 FROM SY INTO @DATA(ld_msgv1).
 
"SELECT single MSGV2 FROM SY INTO @DATA(ld_msgv2).
 
"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



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!