SAP BOM_BOMOK_PROVIDE Function Module for NOTRANSL: BOMOK bereitstellen









BOM_BOMOK_PROVIDE is a standard bom bomok provide 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: BOMOK bereitstellen 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 bom bomok provide FM, simply by entering the name BOM_BOMOK_PROVIDE into the relevant SAP transaction such as SE37 or SE38.

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



Function BOM_BOMOK_PROVIDE 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 'BOM_BOMOK_PROVIDE'"NOTRANSL: BOMOK  bereitstellen
EXPORTING
I_STLTY = "BOM Category
* I_VBPOS = "Sales Order Item
* I_PSPNR = "Work Breakdown Structure Element (WBS Element)
* I_STOBJ = "Standard Object
* I_SEPARATOR = ' ' "Separator
* I_MATNR = "Material Number
* I_DOKAR = "Document Type
* I_DOKNR = "Document Number
* I_DOKTL = "Document Part
* I_DOKVR = "Document Version
* I_EQUNR = "Equipment Number
* I_TPLNR = "Functional Location
* I_VBELN = "Sales Order

IMPORTING
E_BOMOK = "BOM object
.



IMPORTING Parameters details for BOM_BOMOK_PROVIDE

I_STLTY - BOM Category

Data type: BOM_CLASS_DATA-STLTY
Optional: No
Call by Reference: Yes

I_VBPOS - Sales Order Item

Data type: KDST-VBPOS
Optional: Yes
Call by Reference: Yes

I_PSPNR - Work Breakdown Structure Element (WBS Element)

Data type: PRST-PSPNR
Optional: Yes
Call by Reference: Yes

I_STOBJ - Standard Object

Data type: STST-STOBJ
Optional: Yes
Call by Reference: Yes

I_SEPARATOR - Separator

Data type: CSDATA-CHAR1
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_MATNR - Material Number

Data type: MBM_CLASS_DATA-MATNR
Optional: Yes
Call by Reference: Yes

I_DOKAR - Document Type

Data type: DOST-DOKAR
Optional: Yes
Call by Reference: Yes

I_DOKNR - Document Number

Data type: DOST-DOKNR
Optional: Yes
Call by Reference: Yes

I_DOKTL - Document Part

Data type: DOST-DOKTL
Optional: Yes
Call by Reference: Yes

I_DOKVR - Document Version

Data type: DOST-DOKVR
Optional: Yes
Call by Reference: Yes

I_EQUNR - Equipment Number

Data type: EQST-EQUNR
Optional: Yes
Call by Reference: Yes

I_TPLNR - Functional Location

Data type: TPST-TPLNR
Optional: Yes
Call by Reference: Yes

I_VBELN - Sales Order

Data type: KDST-VBELN
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BOM_BOMOK_PROVIDE

E_BOMOK - BOM object

Data type: RC29K-BOMOK
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BOM_BOMOK_PROVIDE 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_e_bomok  TYPE RC29K-BOMOK, "   
lv_i_stlty  TYPE BOM_CLASS_DATA-STLTY, "   
lv_i_vbpos  TYPE KDST-VBPOS, "   
lv_i_pspnr  TYPE PRST-PSPNR, "   
lv_i_stobj  TYPE STST-STOBJ, "   
lv_i_separator  TYPE CSDATA-CHAR1, "   SPACE
lv_i_matnr  TYPE MBM_CLASS_DATA-MATNR, "   
lv_i_dokar  TYPE DOST-DOKAR, "   
lv_i_doknr  TYPE DOST-DOKNR, "   
lv_i_doktl  TYPE DOST-DOKTL, "   
lv_i_dokvr  TYPE DOST-DOKVR, "   
lv_i_equnr  TYPE EQST-EQUNR, "   
lv_i_tplnr  TYPE TPST-TPLNR, "   
lv_i_vbeln  TYPE KDST-VBELN. "   

  CALL FUNCTION 'BOM_BOMOK_PROVIDE'  "NOTRANSL: BOMOK bereitstellen
    EXPORTING
         I_STLTY = lv_i_stlty
         I_VBPOS = lv_i_vbpos
         I_PSPNR = lv_i_pspnr
         I_STOBJ = lv_i_stobj
         I_SEPARATOR = lv_i_separator
         I_MATNR = lv_i_matnr
         I_DOKAR = lv_i_dokar
         I_DOKNR = lv_i_doknr
         I_DOKTL = lv_i_doktl
         I_DOKVR = lv_i_dokvr
         I_EQUNR = lv_i_equnr
         I_TPLNR = lv_i_tplnr
         I_VBELN = lv_i_vbeln
    IMPORTING
         E_BOMOK = lv_e_bomok
. " BOM_BOMOK_PROVIDE




ABAP code using 7.40 inline data declarations to call FM BOM_BOMOK_PROVIDE

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 BOMOK FROM RC29K INTO @DATA(ld_e_bomok).
 
"SELECT single STLTY FROM BOM_CLASS_DATA INTO @DATA(ld_i_stlty).
 
"SELECT single VBPOS FROM KDST INTO @DATA(ld_i_vbpos).
 
"SELECT single PSPNR FROM PRST INTO @DATA(ld_i_pspnr).
 
"SELECT single STOBJ FROM STST INTO @DATA(ld_i_stobj).
 
"SELECT single CHAR1 FROM CSDATA INTO @DATA(ld_i_separator).
DATA(ld_i_separator) = ' '.
 
"SELECT single MATNR FROM MBM_CLASS_DATA INTO @DATA(ld_i_matnr).
 
"SELECT single DOKAR FROM DOST INTO @DATA(ld_i_dokar).
 
"SELECT single DOKNR FROM DOST INTO @DATA(ld_i_doknr).
 
"SELECT single DOKTL FROM DOST INTO @DATA(ld_i_doktl).
 
"SELECT single DOKVR FROM DOST INTO @DATA(ld_i_dokvr).
 
"SELECT single EQUNR FROM EQST INTO @DATA(ld_i_equnr).
 
"SELECT single TPLNR FROM TPST INTO @DATA(ld_i_tplnr).
 
"SELECT single VBELN FROM KDST INTO @DATA(ld_i_vbeln).
 


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!