Search Results get_change_policy_val

Overview

BOM_EXPLODER_PUB is a public PL/SQL package in the APPS schema that provides the bill-of-material explosion engine for Oracle E-Business Suite. It supplies the core logic used to traverse a bill of materials structure from a top assembly through its components, resolve component revisions and effectivity, apply inclusion and exclusion rules, and materialize the resulting rows in the BOM_EXPLOSIONS_ALL interface table. The package is registered as a published (PUB) API in the ETRM repository for releases 12.1.1 and 12.2.2 and carries a VALID status in the APPS schema.

Functionally, BOM_EXPLODER_PUB is the programmatic counterpart to the Oracle Bills of Material explosion forms and concurrent programs. It encapsulates the rules that govern multilevel versus single-level explosions, effectivity date control, revision selection, unit number resolution, and category-based exclusion, ensuring that every consumer — whether a form, a concurrent request, or a custom integration — produces a consistent explosion result.

Key Procedures and Functions

The package documents 28 callable subprograms. They fall into several functional groups:

• Explosion control and setup: EXPLODER_USEREXIT, GET_EXPLODE_OPTION, GET_EXPLOSION_DATE, GET_GROUP_ID, GET_TOP_BILL_SEQUENCE_ID, and GET_COMP_BILL_SEQ_ID establish the parameters that drive a given explosion run, including the explode option, the effective date, the grouping identifier, and the sequence identifiers of the top assembly and individual components.
• Effectivity and change policy: GET_TOP_EFFECTIVITY_CONTROL, GET_CHANGE_POLICY_VAL, and GET_REVISION_HIGHDATE resolve which change policy applies and which revision is effective for a component on a given date.
• Revision resolution: GET_EXPL_END_ITEM_REV, GET_EXPL_END_ITEM_REV_CODE, GET_COMPONENT_REVISION, GET_COMPONENT_REVISION_ID, GET_COMPONENT_REVISION_LABEL, and GET_REVISION_CODE return the revision identifiers and display labels for both the exploded end item and its components.
• Unit and access resolution: GET_EXPL_UNIT_NUMBER retrieves the unit number associated with the exploded assembly; GET_COMPONENT_ACCESS_FLAG and GET_EGO_USER evaluate access privileges and the EGO (Engineering) user context, which is relevant where engineering change objects are involved.
• Exclusion handling: APPLY_NEW_EXCLUSION_RULES, SET_REAPPLY_EXCLUSION_FLAG, and the BOM_EXCLUSION_RULE_DEF-driven routines determine whether a component is suppressed from the explosion and whether previously applied exclusion rules should be reapplied.

Parameter lists are not reproduced here per documentation scope; callers should consult the package specification in the APPS schema.

Tables Accessed

Through APPS synonyms the package reads and writes a set of core BOM and engineering tables. BOM_STRUCTURES_B, BOM_COMPONENTS_B, and BOM_STRUCTURE_TYPES_B supply the structural definition of the bill. BOM_EXPLOSIONS_ALL and its sequence BOM_EXPLOSIONS_ALL_S hold the generated explosion output. BOM_OPERATIONAL_ROUTINGS and BOM_OPERATION_SEQUENCES associate routing and operation detail. BOM_RULES_B, BOM_EXCLUSION_RULE_DEF, and BOM_PARAMETERS provide rule definitions and system parameters. EGO_MINOR_REVISIONS, EGO_OBJ_TYPE_LIFECYCLES, and BOM_ITEM_ATTACH_CATEGORY_ASSOC support revision and lifecycle resolution. FND_ATTACHED_DOCUMENTS and FND_DOCUMENTS_TL support attachment references.

Usage Notes

The package is referenced by eight other packages and views, including BOMPCCLT, BOM_COPY_BILL, BOM_COPY_EXPLOSIONS_V, BOM_EXPLOSIONS_ALL_V, BOM_EXPLOSIONS_V, and EGO_ITEM_ASSOCIATIONS_PUB. This dependency pattern indicates that BOM_EXPLODER_PUB is invoked indirectly by BOM inquiry and copy forms, by the explosion views used in reporting, and by engineering item association logic. Custom code should call it to obtain the same explosion results presented in the standard application; direct manipulation of BOM_EXPLOSIONS_ALL is discouraged. Because the package participates in high-volume explosion processing, callers should supply the correct group identifier and explosion date to avoid cross-run contamination of the explosion table.