Search Results bom_open_interface_api




Overview
Explore in AI Chat

Overview

The APPS.BOM_OPEN_INTERFACE_API package provides the public PL/SQL entry point for importing bill of material (BOM) structures into Oracle E-Business Suite from the open interface tables. It is the programmatic engine behind the standard BOM open interface load, converting staged interface rows into validated production BOM, component, and reference designator records. The package is owned by APPS and is classified as a public API, declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema. Its header file, BOMPBOIS.pls, carries the revision identifier 120.1 and an original creation date of 22-NOV-2002, with a modification in June 2005 adding batch identifier support. In the context of Oracle EBS 12.1.1 and 12.2.2, this package is relevant to users searching for import_bom functionality, since its single documented function is named IMPORT_BOM.

Key Procedures and Functions

The ETRM metadata documents a single function name, IMPORT_BOM, exposed through two overloaded signatures:

  • IMPORT_BOM (null batch id variant) — Processes interface records without restricting to a particular batch identifier, effectively importing all eligible pending rows for the target organization.
  • IMPORT_BOM (batch id variant) — Adds a p_batch_id parameter so that import processing can be scoped to a specific group of staged records previously loaded into the interface tables.

Both variants return an integer status code and accept organization scope, user and login context, concurrent program context (application, program, and request identifiers), a deletion flag controlling whether successfully processed interface rows are removed, and an err_text output parameter for returning error detail. The overloads share the same core parameter set; the batch-aware version merely appends the batch identifier.

Tables Accessed

The package reads and writes the BOM open interface tables through APPS synonyms:

Together these tables constitute the inbound staging area that the API consumes and reconciles into the production BOM schema.

Usage Notes

IMPORT_BOM is typically invoked from the concurrent program that drives the BOM open interface, which loads flat-file data into the interface tables and then calls this API to perform validation and transfer. It may also be called directly from custom PL/SQL when automated or batch-driven BOM loading is required, in which case callers must populate the interface tables first and supply appropriate organization, user, and program context values. The optional batch identifier allows multiple import runs to be isolated and re-driven independently. Because the package is an APPS-owned public API referenced by two other packages, it should be treated as a supported interface rather than a private implementation detail, and error output should be captured via the err_text parameter for diagnostics.