BAPI_MATERIAL_BOM_GROUP_CREATE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below are the pattern details for this FM showing its interface including any import, export parameters etc and for your convenience any standard documentation available. All this information and more can be viewed if you enter the function module name BAPI_MATERIAL_BOM_GROUP_CREATE into the relevant SAP transaction such as SE37 or SE80.
Contribute (Add Comments)
Within the comments section below there is also an opportunity for you to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BAPI_MATERIAL_BOM_GROUP_CREATE or its description.
Pattern for FM BAPI_MATERIAL_BOM_GROUP_CREATE - BAPI MATERIAL BOM GROUP CREATE
SAP Documentation for FM BAPI_MATERIAL_BOM_GROUP_CREATE
Associated Function Group:
CALL FUNCTION 'BAPI_MATERIAL_BOM_GROUP_CREATE' "Creation of a Material BOM Group
* testrun = SPACE " bapiflag Switch to Simulation Session for Write BAPIs
* all_error = SPACE " xflag Output All Errors
bomgroup = " bapi1080_bgr_c BOM group CREATE-/CHANGE BAPI material BOM
variants = " bapi1080_bom_c Alternative/Variant CREATE-/CHANGE BAPI Material BOM
* items = " bapi1080_itm_c Components CREATE-/CHANGE BAPI Material BOM
* subitems = " bapi1080_sui_c Sub item CREATE-/CHANGE BAPI Material BOM
materialrelations = " bapi1080_mbm_c Material assignment CREATE-/CHANGE BAPI Material BOM
* itemassignments = " bapi1080_rel_itm_bom_c Assignments CREATE-/CHANGE BAPI ITM/BOM material BOMs
* subitemassignments = " bapi1080_rel_sui_itm_c Assignments CREATE-/CHANGE BAPI SUI/ITM Mat.BOMs
* texts = " bapi1080_txt_c Long text line: CREATE-/CHANGE BAPI for material BOMs
return = " bapiret2 Return parameter
. " BAPI_MATERIAL_BOM_GROUP_CREATE
This method enables you to create a material BOM with all its assigned
In extreme case, the entire BOM group can be transferred, that means
All variants of a variant BOM or alternatives of a multiple BOM
The entire history
All material assignments
This enables the the data to be transferred from the non-SAP system in
Make sure that a BOM can not be transferred several times. That
also means that you can not first transfer a part of the BOM group,
such as part of the variants or items (particularly with regard to
history) and then in a second run, transfer the rest (additional
variants, assignments, other historical statuses and so on).>
A prerequisite for the successful transfer of a BOM, is that all
business objects, to which a BOM refer have first been transferred into
the SAP System. These are>
Document info records, provided document items exist in the BOM >
Classes, provided class items are to be transferred>
Change numbers tha control the change status of the BOMs >
Standard texts, provided they are to be included in the long text
of the BOM group, variants or items >
You want to transfer several (entire) BOM groups with complete history.
In other words, the variants (in the case of variant BOMs) or
alternatives (in the case of multiple BOMs) with their history and
assigned long texts.
The assignment of assembly materials - possibly from different plants -
The corresponding items with their historical statuses and their long
The sub items of these items
For this you generate entries in the following tables, which are
organized into three categories.
Tables that define objects
BOMGROUP,,,,,,-,,,,Basic data for the entire BOM group
VARIANTS,,,,,,,,-,,,,Variant or alternative data
Tables that define the relationship between objects
MATERIALRELATIONS,,,,-,,Assignment of the header materials to the BOM
groups, with the relevant requirements
ITEMASSIGNMENTS,,,,-,,Assignment requirements of the components to the
variants or alternatives
SUBITEMASSIGNMENTS,,,,-,,Assignments of subitems to items
Tables with other assigned attributes
TEXTS,,,,-,,Long texts for individual objects
The BOM groups are cumulated within the running transfer with a unique
group definition of up to 32 characters (BOM_GROUP_IDENTIFICATION).
This is entered in all table entries. Provided an external (unique) BOM
group is to be placed in the SAP System, this can be used for
Each object can be uniquely identified within a BOM group in the field
OBJECT_ID. In order to be able to easily recognize the object in the
data stream of the import, the field OBJECT_TYPE is also filled with
BOM,,,,in the table VARIANTS
BGR,,,,in the table BOMGROUP
ITM,,,,in the table ITEMS
SUI,,,,in the table SUBITEMS
In addition to this general data, the tables are individually created
Contains the essential basic characteristics of a BOM group such as
BOM usage (BOM_USAGE)
Authorization group (AUTH_GROUP)
and so on.
Contain the variant specific data such as
Base quantity to which the component quantities refer (BASE_QTY)
Validity entries such as change number (CHANGE_NO) and/or key date
In the field FUNCTION you place the value
NEW,,,,if the variant runs in on a specified key date
DEL ,,,,if the variant runs out on a specified key date
Contains the component attributes. Competing attributes that refer to
primary objects, such as component material (COMPONENT), document
number (DOCUMENT_NUMBER), class number (CLASS_NUM) are determined by
the item category (ITEM_CAT). Read the information in SAP Customizing
about the relevant item types and about the other attributes related to
the specified primary objects.
Contains the sub item data
Installation location (INSTALLATION_POINT)
and so on.
Contains - by entering the variant BOM number - the assignments of the
assembly materials to the BOM with the requirements
Lot size area for multiple BOMs (LOT_SIZE_FROM, LOT_SIZE_TO)
Assigns the components of the individual variants/alternatives to BOM
In the fields SUB_OBJECT_TYPE, SUB_OBJECT_ID you enter the BOM
components and in the fields SUPER_OBJECT_TYPE, SUPER_OBJECT_ID you
enter the variants/alternatives. This means, you deposit the values
from the fields OBJECT_TYPE and OBJECT_ID from the table ITEMS in the
field SUB_OBJECT_TYPE, SUB_OBJECT_ID and the values from the fields
OBJECT_TYPE and OBJECT_ID from the table VARIANTS in the fields
SUPER_OBJECT_TYPE, SUPER_OBJECT_ID .
The validity of the assignments is determined by the valid-from date
(VALID_FROM_DATE) or change number (CHANGE_NO)
The field FUNCTION has to be scheduled with a value
NEW,,,,component created with this validity
DEL,,,,component deleted with this validity.
SUBITEM ASSIGNMENTS >
Assigns the sub items to the components
You enter the subitem in the fields SUB_OBJECT_TYPE, SUB_OBJECT_ID the
components in the fields SUPER_OBJECT_TYPE, SUPER_OBJECT_ID. That
means, you deposit the values from the fields OBJECT_TYPE and OBJECT_ID
of table SUBITEMS into the fields SUB_OBJECT_TYPE, SUB_OBJECT_ID and
the values from the fields OBJECT_TYPE and OBJECT_ID from table ITEMS
into the fields SUPER_OBJECT_TYPE, SUPER_OBJECT_ID .
The table TEXTS contains the individual long text lines for all the
objects whose long texts can be assigned. The assignment to the
relevant objects is produced in the fields OBJECT_TYP and OBJECT_ID.
To secure the data in the database, you have to carry out a COMMIT WORK
for each BOM group.
All errors that occur are logged in the export parameter RETURN. In the
case of inconsistencies, the entire BOM group to be generated is
The messages specified in the export parameter RETURN, are arranged as
Messages with the message Id BAPI provide information about the general
results when processing the input.
000,,Processing was successful
Messages with the message Id BAPI1080 provide detailed information
about the processing.
The detail messages fall into two groups:
Message 028> highlights errors or warnings that result from the
analysis of the structure of the transferred BOM data. In the case that
only warnings are given then the processing has been continued and
finished successfully provided no other error messages occur. Still, in
this case, the warning should be followed.
Message 029> highlights errors in the data of the individual
imported objects (variants, items and so on). The process is
In addition to messages 028 and 029, other (error) messages are given,
which better describe the affected sub-objects (variants, items and so
on) or their relationship with each other. The identification of the
object takes place using the message variable BOM_GROUP_IDENTIFICATION
to identify the addected BOM group, and OBJECT_TYP and OBJECT_ID to
identify the objects (variants, items and so on) within a group.
Also (if available) the application log and/or the relevant internal
message last set in the API are given in the export parameter RETURN.
Documentation extract taken from SAP system, Copyright (c) SAP AG