Bills Of Material (BOM)

BOM Interfaces

Oracle Bill of Material

Open Bills of Material Interface

1. BOM_BILL_OF_MTLS_INTERFACE

2. BOM_INVENTORY_COMPS_INTERFACE

3. BOM_REF_DESGS_INTERFACE

4. BOM_SUB_COMPS_INTERFACE

5. MTL_ITEM_REVISIONS_INTERFACE

Open Bills of Material Tables

1. bom_bill_of_materials

2. bom_inventory_components

3. bom_reference_designators

4. bom_substitute_components

5. mtl_item_revisions

Oracle Routing

Open Routing Interface

1. BOM_OP_ROUTINGS_INTERFACE

2. BOM_OP_SEQUENCES_INTERFACE

3. BOM_OP_RESOURCES_INTERFACE

4. MTL_RTG_ITEM_REVS_INTERFACE

Open Routing Tables

1. bom_operational_routings

2. bom_operation_sequences

3. bom_operation_resources

What are MTO and MTS in Oracle E-Business Suite and what are there decision factor?

Make to Order (MTO)

Some manufacturing units manufacture products only against customer orders in other words job is directly associated with Sale order.

This is an example of make to order scenario. In case of make to order products manufacturing lead time need to be low enough to meet the customer requirements. Organizations may stock sub assemblies / Factory made items used in multiple finished products to enable them to satisfy customer demand within a reasonable time.

Make to Stock (MTS)

Some time Products are manufactured in advance expecting future customer orders.

This is the example of make to stock scenario. Organizations making make to stock products are almost totally dependent on planning forecast. In such cases forecast accuracy is a very important factor to maintain cost effective operations.

There are manufacturing units which has both MTO and MTS type of products

MTO & MTS Decision Factors

Depending on different factors like manufacturing lead time, product cost, market demand, competitor’s capability, storage space, change over time, change over cost etc. manufacturing organizations decide to operate the plant as MTO or MTS. The item parameters are to be set accordingly so that the recommendations provided by Advance Supply Chain Planning support MTO or MTS strategy.

BOM Main Reports

• BOM Structure Report --- to report for all levels of a manufacturing BOM
• BOM Comparison Report --- to compare two manufacturing bills
• BOM Loop Report --- to check loop i.e. if an assy is assigned as component to itself
• BOM Parameters Report --- to report default parameters of BOM
• Consolidated BOM Report --- to summarize component usage at all levels
• Resource where used report
• Routing report

API for BOM Creation
===============================================================
bom_bo_pub.process_bom
(p_bo_identifier => 'BOM',
-- This parameter is required. It is used by the API to compare the version number of
-- incoming calls to its current version number.
p_api_version_number => 1.0 ,
-- This parameter is set to TRUE, allows callers to request that the API do the
--initialization of message list on their behalf.
p_init_msg_list => TRUE,
-- This is a set of data structures that represent the incoming business objects. This is a
--record that holds the Bill of Materials header for the BOM
p_bom_header_rec => v_bom_header_rec,
-- All the p*_tbl parameters are data structure that represent incoming business objects
-- They are PL/SQL tables of records that hold for each of the other entities.
p_bom_revision_tbl => v_bom_revision_tbl , p_bom_component_tbl => v_bom_component_tbl, p_bom_ref_designator_tbl => v_bom_ref_designator_tbl, p_bom_sub_component_tbl => v_bom_sub_component_tbl,
-- All the x*_tbl parameters are data structure that represent outgoing business objects
-- They are PL/SQL tables of records that hold records for each of the other entities except
-- now they have all the changes that the import program made to it through all the
-- steps.
x_bom_header_rec => v_bom_hdr_rec , x_bom_revision_tbl => v_bom_rev_tbl,
x_bom_component_tbl => v_bom_comp_tbl,
x_bom_ref_designator_tbl => v_bom_ref_desig_tbl, x_bom_sub_component_tbl => v_bom_sub_comp_tbl,
-- This is a flag that indicates the state of the whole business object after the
-- import. 'S' - Success, 'E' - Error, 'F' - Fatal Error, 'U' - Unexpected Error ,
x_return_status => v_return_status ,
-- This holds the number of messages in the API message stack after
--the import.
x_msg_count => v_msg_count
p_debug => 'N',
p_output_dir => '',
p_debug_filename => '' );
=========================================================