The Bill of Materials (BOM) functional area enables you to determine the profit margin of the components that comprise the finished goods. BOM enables you to keep up with the most viable vendors in terms of cost and profit, and to keep your sales organization aware of product delivery status, including shortages.
To deploy objects in E-Business Suite for exploding the BOM, ensure that the E-Business Suite source environment meets the minimum patch level for your version, as follows:
Customers with Oracle EBS version R12.2.x must be at or above patch level 19128532:R12.BOM.D.
Customers with Oracle EBS version R12.0.x or OPI patch set A must be at or above patch level 19072195:R12.OPI.A.
Customers with Oracle EBS version R12.1.x or OPI patch set B must be at or above patch level 19072195:R12.OPI.B.
Customers with Oracle EBS version 11i must be at or above patch level 14259515.
For complete information about supported patch levels for your source system, see the System Requirements and Supported Platforms for Oracle Business Intelligence Applications.
Note: Systems at or above these minimum patch levels, but below R12.2, include the package OPI_OBIA_BOMPEXPL_WRAPPER_K in the APPS schema, and include the following tables in the OPI schema with alias tables in the APPS schema:
OPI_OBIA_W_BOM_HEADER_DS
OPI_OBIA_BOM_EXPLOSION
OBIA_BOM_EXPLOSION_TEMP_G
R12.2.x systems at or above these minimum patch levels include the package OBIA_BOMPEXPL_WRAPPER_K in the APPS schema, and include the following tables in the BOM schema with alias tables in the APPS schema:
OBIA_W_BOM_HEADER_DS
OBIA_BOM_EXPLOSION
OBIA_BOM_EXPLOSION_TEMP_G
How to Configure the Bill of Materials Explosion Options
The Bill of Materials (BOM) functional area enables you to analyze the components that comprise the finished goods. BOM enables you to determine how many products use a particular component. It also enables you to get visibility into the complete BOM hierarchy for a finished product. To explode BOM structures, certain objects must be deployed in your EBS system.
Note: To run the ETL as the apps_read_only user, you must first run the following DCL commands from the APPS schema:
Grant insert on opi.opi_obia_w_bom_header_ds to &read_only_user; Grant analyze any to &read_only_user;
Or, for R12.2.x:
Grant insert on bom.obia_w_bom_header_ds to &read_only_user; Grant analyze any to &read_only_user;
You can explode the BOM structure with three different options:
All. All the BOM components are exploded regardless of their effective date or disable date. To explode a BOM component is to expand the BOM tree structure.
Current. The incremental extract logic considers any changed components that are currently effective, any components that are effective after the last extraction date, or any components that are disabled after the last extraction date.
Current and Future. All the BOM components that are effective now or in the future are exploded. The disabled components are left out.
These options are controlled by the EXPLODE_OPTION variable. The EXPLODE_OPTION variable is preconfigured with a value of 2, explode Current BOM structure.
There are five different BOM types in a source system: 1- Model, 2 - Option Class, 3 - Planning, 4 - Standard, and 5 - Product Family. By default, only the Standard BOM type is extracted and exploded. You can control this selection using the EBS_BOM_TYPE parameter.
The SDE_ORA_BOMItemFact_Header mapping invokes the OPI_OBIA_BOMPEXPL_WRAPPER_K or OBIA_BOMPEXPL_WRAPPER_K package in the EBS database to explode the BOM structure. The following table lists the variables used to control the stored procedure.
| Input Variable | Preconfigured Value | Description |
|---|---|---|
|
BOM_OR_ENG |
1 |
1—BOM 2—ENG |
|
COMMIT_POINT |
5000 |
Number of records to trigger a Commit. |
|
COMP_CODE |
Not applicable. |
This parameter is deprecated and no longer affects the functionality of the procedure. |
|
CST_TYPE_ID |
0 |
This parameter is deprecated and no longer affects the functionality of the procedure. |
|
EXPLODE_OPTION |
2 |
1—All 2—Current 3—Current and Future |
|
EXPL_QTY |
1 |
Explosion quantity. |
|
IMPL_FLAG |
1 |
1—Implemented Only 2—Implemented and Non-implemented |
|
LEVELS_TO_EXPLODE |
10 |
Number of levels to explode. |
|
MODULE |
2 |
1—Costing 2—BOM 3—Order Entry 4—ATO 5—WSM |
|
ORDER_BY |
1 |
Controls the order of the records. 1—Operation Sequence Number, Item Number. 2—Item Number, Operation Sequence Number. |
|
PLAN_FACTOR_FLAG |
2 |
1—Yes 2—No |
|
RELEASE_OPTION |
0 |
Option to use released items. |
|
STD_COMP_FLAG |
0 |
1 – Explode only standard components 2 – Explode all components |
|
UNIT_NUMBER |
Not applicable. |
When entered, limits the components exploded to the specified Unit. |
|
VERIFY_FLAG |
0 |
This parameter is deprecated and no longer affects the functionality of the procedure. |
|
BOM_THREAD_COUNT |
1 |
Controls how many BOM Explosion threads run in parallel to accomplish the explosion task. |