SAP BOM_REMOVE Function Module for NOTRANSL: Material aus BOM ausbauen

Search SAP Function Modules

BOM_REMOVE is a standard bom remove 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: Material aus BOM ausbauen 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 remove FM, simply by entering the name BOM_REMOVE into the relevant SAP transaction such as SE37 or SE38.

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

Function BOM_REMOVE 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_REMOVE'"NOTRANSL: Material aus BOM ausbauen
  EXPORTING
   IV_SIMULATION =  "
*  IV_NO_CHECK = ' ' "
   IV_MATNR =  "Material Number
*  IV_FUNCID =  "FID (Function Identifier)
   IV_QUANT =  "Quantity in Unit of Entry
   IV_QUNIT =  "Unit of Entry
   IV_HEQUI =  "Superordinate Equipment
   IV_HPLNT =  "
   IV_BOMUS =  "BOM Usage

 IMPORTING
   ES_BOM_ITEM =  "

CHANGING
*  CS_IPW4_COM =  "Commun. Structure for Equipment Install/Dismantle Trans.
*  CT_LOGHNDL =  "Application Log: Log Handle Table
*  CS_HEQUI =  "Generated Table for View V_EQUI
*  CS_GOODSMVT_HEADER =  "
*  CS_GOODSMVT_ITEM =  "
*  CS_GOODSMVT_CODE =  "MMIM: New Key Assignment GM_CODE to Transaction of Inv. Mgmt

EXCEPTIONS
   NO_ITEM = 1    QUANT_ERROR = 2    LOG_ERROR = 3    BOM_UPD_ERROR = 4    LOCK_ERROR = 5    CHK_ERROR_DISM = 6 

.

IMPORTING Parameters details for BOM_REMOVE

IV_SIMULATION -

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

IV_NO_CHECK -

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

IV_MATNR - Material Number

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

IV_FUNCID - FID (Function Identifier)

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

IV_QUANT - Quantity in Unit of Entry

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

IV_QUNIT - Unit of Entry

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

IV_HEQUI - Superordinate Equipment

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

IV_HPLNT -

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

IV_BOMUS - BOM Usage

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

EXPORTING Parameters details for BOM_REMOVE

ES_BOM_ITEM -

Data type: STPOB
Optional: No
Call by Reference: Yes

CHANGING Parameters details for BOM_REMOVE

CS_IPW4_COM - Commun. Structure for Equipment Install/Dismantle Trans.

Data type: IPW4_COM
Optional: Yes
Call by Reference: Yes

CT_LOGHNDL - Application Log: Log Handle Table

Data type: BAL_T_LOGH
Optional: Yes
Call by Reference: Yes

CS_HEQUI - Generated Table for View V_EQUI

Data type: V_EQUI
Optional: Yes
Call by Reference: Yes

CS_GOODSMVT_HEADER -

Data type: BAPI2017_GM_HEAD_01
Optional: Yes
Call by Reference: Yes

CS_GOODSMVT_ITEM -

Data type: BAPI2017_GM_ITEM_CREATE
Optional: Yes
Call by Reference: Yes

CS_GOODSMVT_CODE - MMIM: New Key Assignment GM_CODE to Transaction of Inv. Mgmt

Data type: BAPI2017_GM_CODE
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_ITEM -

Data type:
Optional: No
Call by Reference: Yes

QUANT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

LOG_ERROR -

Data type:
Optional: No
Call by Reference: Yes

BOM_UPD_ERROR -

Data type:
Optional: No
Call by Reference: Yes

LOCK_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CHK_ERROR_DISM -

Data type:
Optional: No
Call by Reference: Yes

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

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