Search Results get_top_bill

Overview

APPS.BOMDELEX is a packaged PL/SQL specification within the Oracle E-Business Suite Bills of Material module. Its purpose is to manage the lifecycle of bill of material explosion data held in the BOM_EXPLOSIONS table, specifically by removing records that have been flagged for regeneration. The package header carries the source identifier BOMDEXPS.pls and was originally created on 23-JUN-03 by the developer Sangeetha, with the last recorded revision dated 2005/06/21. The header comment describes the file as a specification for deleting records from the bom_explosions table where the rexplode flag is set to 1.

The business problem addressed by this package is the controlled cleanup of denormalized explosion results. When a bill of material is exploded, the application stores the resulting component structure in BOM_EXPLOSIONS. When an engineering change or structural update invalidates that stored explosion, the record is marked with the rexplode flag rather than being deleted immediately. BOMDELEX provides the mechanism to identify and purge those marked rows, keeping the explosion table synchronized with current bill definitions. The package is classified as OTHER in the ETRM registry, indicating it is not a formal public API but an internal utility.

Key Procedures and Functions

• DELETE_BOM_EXPLOSIONS — The primary procedure of the package. It deletes the targeted rows from BOM_EXPLOSIONS based on a top bill sequence identifier and an explosion type. It also exposes standard concurrent-program style error handling parameters, returning an error code and error message so that callers can detect and report failures.
• GET_TOP_BILL — A supporting procedure that resolves the top-level bill entry from the inputs of item, organization, and alternate bill designator. It returns a status indicator along with an error buffer, allowing the caller to obtain the bill header information needed before a delete operation can be performed.

Both procedures adhere to the Oracle EBS convention of returning status and error information through output parameters rather than relying solely on exceptions, which makes them suitable for use from concurrent programs and forms that require user-readable diagnostics.

Tables Accessed

The package performs its work against the BOM_EXPLOSIONS table, accessed through the APPS synonym. This table stores the flattened, exploded component structure generated for a bill of material, including quantities, operation sequences, and the rexplode indicator. DELETE_BOM_EXPLOSIONS removes rows from this table where the rexplode flag is set to 1, applying the supplied top bill sequence identifier and explosion type as filters. GET_TOP_BILL provides the lookup necessary to determine the correct bill context prior to deletion. No other tables are documented as referenced by this package.

Usage Notes

BOMDELEX is an internal utility rather than a published interface. It is not referenced by any other documented package, meaning callers invoke it directly rather than through a layered API. Typical invocation scenarios include concurrent programs responsible for purging stale explosion records, Oracle Forms logic that refreshes bill structures after maintenance, and custom PL/SQL scripts that need to clear invalidated explosion data. Because the parameters follow the ERRBUF and RETCODE pattern, the package can be registered as a concurrent program executable with relatively little wrapper code. Developers integrating with it should verify that the rexplode flags on the target rows are correctly set before invocation, since the procedure removes data rather than archiving it.