Results for “cn_dim_hierarchies”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CN_DIM_HIERARCHIES_PKG is a PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema associated with the Oracle Price Protection / Channel Revenue Management (CN) product family. Its purpose is to manage the persistence and lifecycle of dimension hierarchies stored in the CN_DIM_HIERARCHIES table. A dimension hierarchy represents a structured tree of related values — for example, customer, product, or channel dimension groupings — used by pricing, accrual, and channel analytics processes throughout the CN modules. The package is classified as OTHER under the ETRM taxonomy, indicating it is an internal supporting API rather than a formally published integration interface.

The package body maintains the header record for each hierarchy (dates, root node pointer, header link, and MOAC-enabled ORG_ID) while coordinating the creation of the root node and base node entries in the hierarchy node and edge tables. This ensures that every hierarchy created through the package is internally consistent from the moment of insertion.

Key Procedures and Functions

The package body exposes three documented procedures:

• INSERT_ROW — Creates a new dimension hierarchy record. It obtains surrogate keys from the CN_DIM_HIERARCHIES_S and CN_HIERARCHY_NODES_S sequences, inserts the header row into CN_DIM_HIERARCHIES (including ORG_ID for multi-org access control, start and end dates, the header dimension hierarchy reference, and standard WHO audit columns), inserts a root node into CN_HIERARCHY_NODES, and delegates base node creation to CN_DIHY_TWO_API_PKG.Insert_Edge. The new DIM_HIERARCHY_ID and ROOT_NODE values are returned to the caller as OUT parameters.
• UPDATE_ROW — Modifies an existing dimension hierarchy header record, supporting adjustments to the hierarchy attributes and audit tracking.
• DELETE_ROW — Removes a dimension hierarchy record and its dependent structures, applying the appropriate cleanup across the header, node, and edge tables.

All three procedures operate on the hierarchy as an atomic unit, upholding referential integrity between the header, nodes, and edges.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• CN_DIM_HIERARCHIES — the primary header table holding each dimension hierarchy definition, dates, root node, header link, and org context; inserted, updated, and deleted by the package.
• CN_HIERARCHY_NODES — stores the individual nodes of each hierarchy; the package inserts the root and base nodes on creation.
• CN_HIERARCHY_EDGES — stores the parent-child relationships between nodes, populated when the base node is linked to the root node through the edge API.
• CN_DIM_HIERARCHIES_S and CN_HIERARCHY_NODES_S — sequences used to generate the unique DIM_HIERARCHY_ID and ROOT_NODE identifiers.
• DUAL — used solely for sequence selection.

Usage Notes

CN_DIM_HIERARCHIES_PKG is invoked programmatically rather than directly by end users. It is typically called from CN module forms, concurrent programs, and other PL/SQL packages that need to create, maintain, or remove dimension hierarchies. As the package is referenced by one other package in the ETRM metadata, it functions as a lower-level building block within the CN pricing and channel hierarchy stack. Because it is classified as OTHER and not as a public API, customizations should prefer any of the parent packages that wrap it, and direct calls should be restricted to controlled extensions that preserve the node and edge integrity established by INSERT_ROW. Callers must supply a valid ORG_ID to satisfy multi-org access control requirements.