Scribd
Upload
252 views5 pages

Interface and Respective Tables Used in Oracle BOM and

This document discusses the interfaces and tables used in Oracle Bill of Materials (BOM) and Work in Process (WIP). It provides the names of the five BOM interfaces and their corresponding tables. It also lists the four routing interfaces and associated tables. The document then describes the mandatory columns needed to insert data into the two main BOM interface tables to create a BOM, along with example INSERT statements. It concludes by noting that after loading data, a concurrent program should be run to upload the interface data to the base tables.

Uploaded by

Atul Ramteke
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
252 views5 pages

Interface and Respective Tables Used in Oracle BOM and

This document discusses the interfaces and tables used in Oracle Bill of Materials (BOM) and Work in Process (WIP). It provides the names of the five BOM interfaces and their corresponding tables. It also lists the four routing interfaces and associated tables. The document then describes the mandatory columns needed to insert data into the two main BOM interface tables to create a BOM, along with example INSERT statements. It concludes by noting that after loading data, a concurrent program should be run to upload the interface data to the base tables.

Uploaded by

Atul Ramteke
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Interface and respective Tables Used in Oracle BOM and WIP

Posted on November 15, 2007 by Ahmad Bilal


Following are Interface and their respective tables Used in Oracle BOM and WIP 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

Mandatory columns needed to insert data into BOM Interface tables. Here is a snippet of code which tells about the mandatory columns needed to insert the data into BOM Interface tables.

There are two BOM Interface tables, which needs to be populated in order to create BOM. BOM_BILL_OF_MTLS_INTERFACE BOM_INVENTORY_COMPS_INTERFACE Insert command :
INSERT INTO bom_bill_of_mtls_interface( assembly_item_id ,organization_id ,bill_sequence_id ,item_number ,item_description ,last_update_date ,last_updated_by ,creation_date ,created_by ,last_update_login ,transaction_type ,process_flag ) VALUES( <assembly_item_id> ,<organization_id> ,<bill_sequence_id> ,<assembly_item_number> ,<description> ,SYSDATE ,<user_id> ,SYSDATE ,user_id ,user_id ,<CREATE or UPDATE> -- If it is update, then bill sequence id is required, else NULL ,1 ); INSERT INTO BOM_INVENTORY_COMPS_INTERFACE ( component_item_id ,assembly_item_id ,organization_id ,item_num ,operation_seq_num ,effectivity_date ,transaction_type ,process_flag

,bill_sequence_id ,component_sequence_id ,item_description ,basis_type ,component_quantity ,component_yield_factor ,implementation_date ,supply_subinventory ,wip_supply_type ,so_basis ,check_atp ,planning_factor ,low_quantity ,high_quantity ,last_update_date ,last_updated_by ,creation_date ,created_by ,last_update_login ,component_remarks ) values ( <component_item_id> ,<assembly_item_id> ,<organization_id> ,<item_seq_num> ,<operation_sequence> ,SYSDATE ,<CREATE or UPDATE> -- If it is update, then Component sequence id is required, else NULL ,1 ,<bill_sequence_id> -- If transaction type is UPDATE, then this value is required else NULL ,<comp_sequence_id> -- If transaction type is UPDATE, then this value is required else NULL ,<com_description> ,DECODE(basis_type,1,NULL,2) ,<component_quantity> ,<component_yield_factor> ,<implementation_date> ,<supply_subinventory> ,<l_wip_supply_type> -- lookup code from MFG_LOOKUPS where lookup_type = 'WIP_SUPPLY' ,<so_basis> ,DECODE(check_atp,'Y',1,'N',2) ,<planning_factor> ,<low_quantity> ,<high_quantity> ,SYSDATE ,user_id

,SYSDATE ,user_id ,user_id ,'BOM Migration' );

Once data is successfully loaded, then call the standard oracle concurrent program : Bill and Routing Interface to upload the data from interface tables to Base tables.

You might also like