OracleFree worksheetPDF, Excel, Word exportOracle E-Business SuiteDiscrete Manufacturing

Oracle EBS BOM Interface Load Worksheet

Loading bills of material into Oracle EBS is usually done through the BOM open interface tables. This worksheet helps you stage and sanity-check component rows in Excel before they ever reach the interface.

Download:

ASSEMBLY_ITEM_NUMBER	ORGANIZATION_CODE	COMPONENT_ITEM_NUMBER	ITEM_NUM	OPERATION_SEQ_NUM	COMPONENT_QUANTITY	Unit cost (check)	Extended cost	TRANSACTION_TYPE	EFFECTIVITY_DATE
							$43
							$19
							$6
							$3
							$2

Total component quantity

Rolled-up component cost

$72

Average cost per component line

$14

Component columns follow BOM_INVENTORY_COMPS_INTERFACE and the header columns follow BOM_BILL_OF_MTLS_INTERFACE. The load also needs PROCESS_FLAG set to 1 and a batch or group identifier, then you run the Bill and Routing import program. Column requirements vary by release, so validate in a test instance. The unit cost column is only a local check and is not loaded.

BOM conversion review

Optional: we can review your conversion mapping and test load plan for Oracle EBS.

Optional. The tool and every export work without this. No spam.

How to use this worksheet

Replace the sample rows with your assembly, organization and component data. Choose CREATE for new components, UPDATE or DELETE for changes. Use the extended cost column and totals to spot a component with a wildly wrong quantity before load. Export to Excel, convert to a CSV or SQL loader file, and populate the interface tables through your standard conversion process.

Header and component tables

The interface has a header table for the bill itself and a component table for each line. Rows in both are matched by assembly, organization and a transaction identifier. After loading with PROCESS_FLAG set to pending, run the Bills and Routings import program, then check the error table for rows that failed validation and fix them in the staging data.

Header: BOM_BILL_OF_MTLS_INTERFACE
Components: BOM_INVENTORY_COMPS_INTERFACE
Errors: MTL_INTERFACE_ERRORS
Run the import program after the load

Pre-load validation tips

Confirm that every assembly and component already exists as an item in the target organization with BOM Allowed enabled. Check that operation sequence numbers match the routing if one exists, and that the item sequence numbers are unique within the bill. Look for duplicate component lines and zero quantities, which are the most common reasons for rejected rows.

Common mistakes

Loading components before the items are assigned to the organization causes mass failures. Reusing the same effectivity date for engineering and production changes can create overlapping effectivity. Finally, running an import twice without clearing earlier rows duplicates components. Always reconcile counts after load.

Frequently Asked Questions

Which tables does the Oracle BOM open interface use?

The header goes into BOM_BILL_OF_MTLS_INTERFACE and components into BOM_INVENTORY_COMPS_INTERFACE. Revisions and routing have their own interface tables. Errors are recorded in MTL_INTERFACE_ERRORS.

What does ACD_TYPE do?

It marks whether a component row adds, changes or disables a component through a change order. For a plain bill load the TRANSACTION_TYPE column such as CREATE or UPDATE is the main control.

Can I load a multi-level BOM?

Yes. Each level is its own bill with its own assembly. Load the child assemblies first or in the same batch so that every referenced item and bill exists.

How do I check what failed?

Query MTL_INTERFACE_ERRORS for the transaction identifiers of your batch. Fix the staging data and reset the rows to pending before running the import again.

If you are migrating bills of material from SyteLine, Baan or a legacy system into Oracle, we can help build and test the conversion scripts.

Talk to an Expert Explore More Free Tools

Related Tools

Oracle

More Oracle tools

See all

Back to All Tools