Search Results mtl_interface




Overview

APPS.BOM_IMPORT_PUB is the public PL/SQL package body that drives the open interface import of bills of material and routing data into Oracle E-Business Suite. It is the programmatic entry point for loading legacy or external manufacturing structures into the EBS base tables. The package operates on records staged in the BOM open interface tables (the _INTERFACE tables) plus batch and option-set metadata held in the EGO tables, validates and resolves those rows, and then writes the accepted data into the permanent BOM structures and component tables. The header comment identifies BULKLOAD_PVT_PKG.PROCESS_BOM_INTERFACE_LINES as a related worker, confirming a layered bulk-loading design.

The package is documented as a PUB (public) API and is referenced by four other packages, meaning it is intended for direct call by concurrent programs and custom integrations rather than being an internal helper. Its latest documented revision is a 120.94 label, consistent with a long-lived component present in both 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes 32 documented procedures and functions. The principal groups are:

Tables Accessed

The package reads and writes through APPS synonyms. The interface tables are the working set: BOM_BILL_OF_MTLS_INTERFACE, BOM_COMPONENT_OPS_INTERFACE, BOM_INVENTORY_COMPS_INTERFACE, BOM_OP_NETWORKS_INTERFACE, BOM_OP_RESOURCES_INTERFACE, BOM_OP_ROUTINGS_INTERFACE, BOM_OP_SEQUENCES_INTERFACE, BOM_CMP_USR_ATTR_INTERFACE, and BOM_REF_DESGS_INTERFACE. The destination base tables are BOM_STRUCTURES_B, BOM_COMPONENTS_B, BOM_COMPONENTS_EXT_B, and BOM_REFERENCE_DESIGNATORS. Batch control uses EGO_IMPORT_BATCHES_B and EGO_IMPORT_OPTION_SETS, which govern batch identity and processing options. Debug tracing relies on V$PARAMETER.

Usage Notes

BOM_IMPORT_PUB is normally invoked from the Bill of Material open interface concurrent program, which loads staging rows and then calls this package to validate and post them. It may also be called directly from custom PL/SQL after populating the BOM interface tables and an EGO import batch. Because the package spans interface, resolution, and posting logic, callers should populate all required interface tables and option sets before invocation, and should inspect confirmation status output produced through PROPAGATE_CONFIRMATION_STATUS and DATA_UPLOAD_COMPLETE to identify rejected rows.