Search Results insert_edge

Overview

APPS.CN_DIHY_TWO_API_PKG is a public PL/SQL package in the Oracle E-Business Suite Channel Intelligence / Dimension Hierarchy (CN) module, shipped under the APPS schema. It exposes the lower-level application programming interface used to build and maintain dimension hierarchies — the ordered parent/child structures through which transactional and master data are rolled up, sliced, and reported. Its header, dated 2005 with Release 12 (R12) Multi-Org Access Control (MOAC) changes applied, indicates that the package predates the 12.1.1 and 12.2.2 releases and remains a supporting API in both.

The user search term "insert_dimension" corresponds directly to the Insert_Dimension procedure declared in this package. That procedure, together with Insert_Edge and Cascade_Delete, forms a compact maintenance interface: dimensions are defined, hierarchy edges (parent-child links) are created, and hierarchy nodes are removed along with their descendants. In the ETRM classification this object is typed as OTHER rather than a fully public documented API, so it is generally treated as an internal or semi-private package invoked by other CN components rather than by end users directly.

Key Procedures and Functions

• Insert_Dimension — Registers a new dimension definition. Its parameters carry the dimension identifier, display name, the base table from which dimension members are drawn, the primary key of that table, a user-defined column name reference, and the MOAC X_org_id so the dimension is scoped to the correct operating unit.
• Insert_Edge — Creates a hierarchy edge, i.e., a parent-child relationship between two hierarchy nodes. It accepts the edge name, the dimension hierarchy identifier, the node value identifier (IN OUT, so the caller receives the generated or resolved value), the parent value identifier, an external identifier, the hierarchy API identifier, and the MOAC X_org_id.
• Cascade_Delete — Removes a hierarchy node and recursively cascades the deletion to its dependent edges/descendants, using the value identifier, parent value identifier, hierarchy identifier, and the MOAC X_org_id.

Tables Accessed

The package reads and writes the CN dimension hierarchy base tables through APPS synonyms:

• CN_HIERARCHY_EDGES — stores the parent-child edge rows created by Insert_Edge and removed by Cascade_Delete.
• CN_HIERARCHY_NODES and CN_HIERARCHY_NODES_S — hold hierarchy node/definition data and its translated or secondary (sibling) representation.
• CN_OBJECTS — the object registry supplying metadata for the dimensions and associated underlying entities.
• DUAL — used for single-row lookups and sequence/next-value style queries.

Usage Notes

CN_DIHY_TWO_API_PKG is referenced by two other packages, so it is primarily invoked programmatically rather than from a standard EBS form. Typical callers include higher-level CN hierarchy APIs, concurrent programs that load or rebuild dimension hierarchies, and custom extensions that need to insert dimensions or edges in bulk. Because the MOAC X_org_id parameter is present on all three procedures, callers in a multi-org environment must initialize the session's org context correctly before invoking the API. As an OTHER-classified internal package, its signatures are not guaranteed as a stable public contract; upgrades between 12.1.1 and 12.2.2 should be validated when custom code depends on it.