Search Results sl_imploder

Overview

BOM_BOMRWUIT_XMLP_PKG is a PL/SQL package owned by the APPS schema that supports the Oracle Bills of Material "Bill of Material Report – Where Used/Implosion" concurrent program. The suffix "XMLP_PKG" identifies it as the generated report helper package associated with an Oracle XML Publisher (XMLP) report definition. Its principal business role is to drive multi-level where-used implosion logic, allowing planners and engineers to determine which parent assemblies, at which levels, require a given component or item. The package resolves organization, item, category, and revision criteria supplied at runtime, invokes the recursive implosion engine, and formats the resulting rows for the XML Publisher template.

The package exposes numerous package-level variables (for example P_ORG_ID, P_ITEM_FROM, P_ITEM_TO, P_SET_ID, P_CAT_FROM, P_CAT_TO, P_IMPLEMENTED, P_DATE, P_DATE_1, P_DATE_OPTION, P_LEVEL, P_ITEM_ID, P_ITEM_REV, P_ENG_BILL_FLAG, P_CATEGORY_STRUCTURE_ID, P_ITEM_STRUCTURE_ID, P_CONC_REQUEST_ID, P_SEQUENCE_ID, P_SPECIFIC_ITEM, P_QTY_PRECISION, and P_ALL_ORGS). These parameters are populated by the Oracle Reports/XML Publisher runtime before the report logic executes.

Key Procedures and Functions

• BEFOREREPORT – Initialization entry point invoked prior to report execution; establishes session context and parameter defaults.
• AFTERREPORT – Cleanup entry point invoked after report completion.
• GET_STATUS – Derives a display status value from a revised item sequence, an implemented flag, and a notice description, producing the status text shown on the report output.
• GET_ORGCODE – Returns the organization code for a supplied organization identifier.
• CF_ALL_ORGSFORMULA – Report formula column function that returns a character indicator governing the "all organizations" behavior.
• GET_PRECISION – Returns a formatted quantity precision descriptor based on the supplied numeric precision value.
• IMPLODER_USEREXIT – User exit hook that accepts implosion criteria (sequence ID, engineering/manufacturing flag, organization, implemented flag, display option, levels to implode, item, implosion date) and returns error message and error code outputs.
• IMPLOSION – Core procedure performing the implosion query for a given sequence, organization, and level depth, returning error status through its output parameters.
• SL_IMPLODER – Single-level imploder variant. This is the procedure most frequently referenced by users searching for "sl_imploder"; it performs the single-level where-used expansion for a report run.
• ML_IMPLODER – Multi-level imploder variant, extending the expansion across multiple bill levels according to the levels-to-implode parameter.

Tables Accessed

• BOM_IMPLOSION_TEMP and BOM_IMPLOSION_TEMP_S – Temporary staging tables that hold implosion results (and their sequence shadow) as the where-used hierarchy is built and consumed by the report.
• ENG_REVISED_ITEMS – Source of engineering change order and revised item information used for status and revision context.
• MTL_PARAMETERS – Provides organization-level defaults such as quantity precision for the operating organization.
• FND_ID_FLEX_STRUCTURES – Supplies key flexfield structure definitions used to resolve item and category structure identifiers.
• DUAL – Utility queries for single-row computations.
• DBMS_SQL and PLITBLM – Dynamic SQL and PL/SQL table utilities used to build and execute variable implosion statements.

Usage Notes

BOM_BOMRWUIT_XMLP_PKG is not intended for direct invocation by end users or custom code. It is invoked by the Oracle XML Publisher runtime when the "Bill of Material Report – Where Used/Implosion" concurrent program is submitted from the Submit Requests window. Parameter values entered on the concurrent program's parameter form populate the package variables, and the before/after report functions bracket execution. Because the package is documented as referenced by zero other packages, it is effectively a leaf consumer in the dependency graph. Any customization should be performed through the report definition and its parameters rather than by modifying this generated helper, since it is regenerated whenever the XML Publisher report definition is recompiled.