Search Results ml_imploder_cad




Overview
Explore in AI Chat

Overview

APPS.BOM_IMPLODER_PUB is the public wrapper package for the Bill of Materials implosion engine in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Implosion is the inverse of explosion: rather than expanding an assembly downward into its components, it traces an item upward through the bill of materials to identify every parent assembly in which the item is used. This "where-used" capability is fundamental to engineering change management, cost rollup, component substitution analysis, and impact assessment before a revision or obsolescence decision is approved.

The package exposes the same implementation invoked by the standard Bills of Material responsibility when a user launches an implosion inquiry. It supports single-level and multi-level implosion, honors engineering versus manufacturing bills, filters implemented versus unimplemented components, and permits scoping across the current organization, an organization hierarchy, or all organizations to which the user has access. Because it is a PUB-classified API, Oracle documents it as a supported integration point for external and custom callers, though the historical header comment indicates the source has been dormant since 2006.

Key Procedures and Functions

  • IMPLODER_USEREXIT — The principal user entry point and the object referenced by the search term "imploder_userexit." It drives the implosion according to a caller-supplied sequence identifier, engineering/manufacturing flag, organization, implementation flag, display option, levels to implode, assembly identifier, and implosion date. Parameters documented in the source include obj_name (defaulting to EGO_ITEM) and pk1_value/pk2_value/pk3_value key-value pairs used to identify the starting assembly. It returns an error message buffer and an error code, including a value of 9999 when a loop is detected in the structure.
  • IMPLOSION_CAD — Performs CAD-oriented implosion processing, typically for integration with computer-aided design or engineering data exchange flows where parent-child usage must be resolved against CAD structures.
  • ML_IMPLODER_CAD — The multi-level variant of the CAD implosion routine; the source history records that the formerly separate sl_imploder_cad procedure was removed in February 2006, consolidating CAD implosion logic.
  • CHECK_USER_VIEW_PRIV — Validates that the invoking user holds the item or organization view privilege required to see the returned structure, enforcing access control on implosion results.
  • CALCULATE_COMP_COUNT — Computes the number of components associated with a parent, supporting quantity and rollup calculations used during implosion output generation.

Tables Accessed

The package works primarily against the BOM and item master schemas. BOM_COMPONENTS_B, BOM_STRUCTURES_B, and BOM_STRUCTURE_TYPES_B supply the parent-component relationships traversed during implosion. BOM_RULES_B and BOM_EXCLUSION_RULE_DEF provide the rule and exclusion logic that governs which components are visible. BOM_PARAMETERS and MTL_PARAMETERS supply organization-level setup defaults, while MTL_SYSTEM_ITEMS_B and MTL_ITEM_REVISIONS_B resolve item and revision attributes, including the revision filter added in the November 2005 revision. Results and working sets are staged in BOM_SMALL_IMPL_TEMP and BOM_IMPLOSION_TEMP_S, the latter keyed by the sequence_id passed to IMPLODER_USEREXIT. FND_USER supports the privilege check, and DUAL is used for scalar evaluation.

Usage Notes

BOM_IMPLODER_PUB is normally invoked indirectly from the Bills of Material inquiry forms and from concurrent programs that report where-used information. Custom integrations should call IMPLODER_USEREXIT rather than the private implosion routines, supplying a unique sequence identifier consistent with BOM_IMPLOSION_TEMP_S and reading the staged rows back through the temporary table. Because two other packages reference this API, direct modification is not advised. Callers must be prepared to handle the loop-detection error code and to observe organization access restrictions, since the package enforces user view privileges before returning structure data.