Results for “gl_flex_values_nh_obj_tbl”
8 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
GL_COA_SEG_VAL_IMP_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as a PUB (public) API within the ETRM metadata for releases 12.1.1 and 12.2.2. Its business function is to support the import and validation of Chart of Accounts (COA) segment values and their associated hierarchy definitions. In EBS, the structure of a Chart of Accounts is defined by key flexfield segments, and each segment draws its valid values from one or more registered value sets. The GL_COA_SEG_VAL_IMP_PUB package provides the public entry point through which segment value data — including hierarchical relationships maintained in the flexfield hierarchy tables — is loaded, validated, and reconciled against the underlying value set definitions.
The package is closely aligned with the Key Flexfield architecture, acting as the interface layer between external or staged segment value data and the FND_FLEX value tables. Because it is designated as a public API, it is the supported programmatic entry point that other Oracle modules and customizations are expected to call, rather than reaching into the underlying private packages directly.
Key Procedures and Functions
The documented interface exposes a single program unit:
- COA_SEGMENT_VAL_IMP — the primary import procedure. It drives the loading of COA segment values, performing validation against the target value set and applying hierarchy information. This procedure is the reason the package is referenced by the private counterpart GL_COA_SEGMENT_VAL_PVT, as well as by GL_COA_SEG_VAL_IMP_PKG and GL_COA_SVIM_CONC_PKG, indicating that the public routine serves as a wrapper over private implementation logic.
Parameter lists are not defined in the available metadata and are therefore not reproduced here. Consumers should obtain the exact signature from the package specification in the target instance before invoking it.
Tables Accessed
The package references the following tables through APPS synonyms, all of which are core Key Flexfield and value set infrastructure objects:
- FND_FLEX_VALUES and FND_FLEX_VALUES_TL — store the individual valid values for a value set and their translated descriptions; these are the primary targets for imported segment values.
- FND_FLEX_VALUE_SETS — defines the value set to which each imported value belongs, establishing the validation context.
- FND_FLEX_HIERARCHIES — holds hierarchy definitions used to organize values into parent-child rollup structures.
- FND_FLEX_VALUE_NORM_HIERARCHY — supports normalized (denormalized range) hierarchy storage, enabling efficient range-based hierarchy queries.
- FND_NEW_MESSAGES and PLITBLM — used for message resolution and PL/SQL table handling of message text during error reporting.
The package additionally works with the PL/SQL object types GL_FLEX_VALUES_OBJ_TBL and GL_FLEX_VALUES_NH_OBJ_TBL, which carry value and normalized-hierarchy records as bulk collections. It depends on FND_API for standard API error and message handling conventions.
Usage Notes
GL_COA_SEG_VAL_IMP_PUB is typically invoked through the Chart of Accounts segment value import flow rather than directly by end users. Its documented dependents — GL_COA_SEGMENT_VAL_PVT, GL_COA_SEG_VAL_IMP_PKG, GL_COA_SVIM_CONC_PKG, and GL_DRM_INTEGRATION_PKG — show that it is called by the segment value import concurrent program and by Data Relationship Management (DRM) integration processes that push externally maintained hierarchies into EBS. In practice, this means the import may be triggered from an Oracle-supplied concurrent program or integration package rather than from an online form.
Custom code should treat GL_COA_SEGENT_VAL_IMP as a supported public API and route all segment value imports through it, relying on its FND_API-based error handling for validation feedback. Because the package manipulates core flexfield value and hierarchy tables, callers should run it within a controlled transaction and follow Oracle's standard commit strategy. Always verify the exact procedure signature against the package specification in the specific EBS release (12.1.1 or 12.2.2) before use, since parameter lists are not documented in the available metadata.
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2