SAP CS_OV_BOM_EDIT Function Module for NOTRANSL: Anlegen oder Ändern eines Stücklistenkopfes

Search SAP Function Modules

CS_OV_BOM_EDIT is a standard cs ov bom edit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Anlegen oder Ändern eines Stücklistenkopfes 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 ov bom edit FM, simply by entering the name CS_OV_BOM_EDIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: CSOV
Program Name: SAPLCSOV
Main Program: SAPLCSOV
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CS_OV_BOM_EDIT 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_OV_BOM_EDIT'"NOTRANSL: Anlegen oder Ändern eines Stücklistenkopfes
  EXPORTING
   I_STLTY =  "BOM Category
*  I_MARK_DOC_UPDATE = ' ' "
   I_KEY_DATE =  "Valid-From Date
   I_ECN =  "Change Number
   I_STLNR =  "Bill of Materials No.
   I_STLAL =  "Alternative BOM
*  I_MATNR = ' ' "
*  I_WERKS = ' ' "
*  I_VBELN = ' ' "
*  I_VBPOS = ' ' "
*  I_MARK_BOM_TXT_UPDATE = ' ' "
*  I_MARK_BGR_TXT_UPDATE = ' ' "

.

IMPORTING Parameters details for CS_OV_BOM_EDIT

I_STLTY - BOM Category

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

I_MARK_DOC_UPDATE -

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

I_KEY_DATE - Valid-From Date

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

I_ECN - Change Number

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

I_STLNR - Bill of Materials No.

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

I_STLAL - Alternative BOM

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

I_MATNR -

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

I_WERKS -

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

I_VBELN -

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

I_VBPOS -

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

I_MARK_BOM_TXT_UPDATE -

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

I_MARK_BGR_TXT_UPDATE -

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

Copy and paste ABAP code example for CS_OV_BOM_EDIT 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.

ABAP code using 7.40 inline data declarations to call FM CS_OV_BOM_EDIT

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