Search Results cz_imp_ps_node




Overview

BOM_COMMON_DEFINITIONS is a shared utility package in the APPS schema that centralizes low-level lookup logic used throughout Oracle E-Business Suite's Bills of Material module. It is not an end-user facing API; rather, it provides reusable helper routines that other BOM, order entry, configuration, and flow manufacturing packages call to resolve common code values and sort keys without duplicating that logic. The package status is VALID in the referenced environment, and its API classification in the ETRM repository is OTHER, indicating it is an internal support package rather than a documented public interface.

The package is a dependency hub. According to the ETRM metadata, BOM_COMMON_DEFINITIONS references the APPS synonym BOM_EXPLOSIONS and the SYS STANDARD package, and it is referenced by seventeen other packages, including BOMPBEXP, BOMPBXIN, BOMPEXPL, BOM_EXPLODER_PUB, BOM_OE_EXPLODER_PKG, OE_CONFIG_PVT, CSI_ITEM_INSTANCE_PVT, FLM_EXECUTION_UTIL, FLM_SUPPLY_DEMAND, and CZ_IMP_PS_NODE. Because these callers span Bill of Materials explosion, order entry configuration, install base, and flow manufacturing, the routines here are deliberately generic.

Key Procedures and Functions

Two procedures or functions are documented for this package in the ETRM 12.2.2 metadata:

  • GET_INITIAL_SORT_CODE — Returns an initial sort code value used when ordering or sequencing records. Callers that build exploded bill structures or ranked component lists invoke this routine to obtain a consistent starting sort key rather than hard-coding one.
  • GET_PDH_SRCSYS_CODE — Resolves the source system code associated with a planning or demand header context (the PDH prefix). This is used by downstream packages that must tag exploded or configured data with the correct originating source system.

No parameter lists are documented in the ETRM extract, so signatures are not reproduced here. Both routines are implemented in the package body, and the package also exposes a [Package] specification and [Package Body] section in the source metadata.

Tables Accessed

The only table documented as referenced by BOM_COMMON_DEFINITIONS is BOM_EXPLOSIONS, accessed through an APPS synonym. BOM_EXPLOSIONS holds the materialized result set of a bill of materials explosion, including the hierarchical component structure, levels, and related attributes. The package reads from this structure to derive the sort codes and source-system codes returned by its two routines. The package additionally relies on the SYS.STANDARD package for base PL/SQL types and built-ins; no other application tables appear in the documented dependency list.

Usage Notes

BOM_COMMON_DEFINITIONS is invoked indirectly rather than directly by end users. Typical call paths include bill explosion concurrent programs and forms driven by BOM_EXPLODER_PUB and BOM_OE_EXPLODER_PKG, order entry configuration flows through OE_CONFIG_PVT, install base processing through CSI_ITEM_INSTANCE_PVT, and flow manufacturing execution and supply/demand planning through FLM_EXECUTION_UTIL and FLM_SUPPLY_DEMAND. The reference to CZ_IMP_PS_NODE is significant because that package belongs to Oracle's configurator/model import area, so the routines here also back configuration model node importing. Because it is an internal helper rather than a certified public API, customizations should avoid calling BOM_COMMON_DEFINITIONS directly; instead, use the supported public packages that depend on it. Oracle may change its internal logic between releases without notice, so any custom code bound to these two routines should be treated as unsupported and revalidated during upgrades from 12.1.1 to 12.2.2.