Results for “enabled_flag”

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

Overview

FND_FLEX_KEYVAL is one of the foundational PL/SQL packages in the Oracle E-Business Suite Flexfields architecture. It resides in the APPS schema and, in the 12.1.1 and 12.2.2 releases, holds a VALID status as a package body with API classification OTHER. The package encapsulates the core validation and resolution logic for key flexfields, most notably the Accounting Flexfield, whose concatenated segment combinations are stored as code combinations. Its central responsibility is to determine whether a combination of segment values constitutes a valid, enabled, and secure key flexfield combination, and to return identifying and descriptive information about that combination.

Because key flexfield validation underpins virtually every module that references accounting distributions — General Ledger, Payables, Receivables, Assets, Purchasing, and others — FND_FLEX_KEYVAL is invoked at extremely high volume across the application. The ETRM metadata records that the package is referenced by 106 other packages, confirming its role as a shared service in the Flexfields Foundation layer.

Key Procedures and Functions

The documented API exposes 32 procedures and functions. The validation family forms the core: VALIDATE_SEGS validates a set of segment values as supplied; VALIDATE_CCID validates a fully constructed code combination identifier; and IS_VALID returns whether a combination is valid. IS_SECURED determines whether the current user is permitted to use a given combination, enforcing security rules defined for the key flexfield structure.

Error handling is served by a set of dedicated routines. VALUE_ERROR, UNSUPPORTED_ERROR, and SERIOUS_ERROR raise categorized failures during processing. ERROR_SEGMENT identifies the specific segment implicated in a validation failure, while ERROR_MESSAGE and ENCODED_ERROR_MESSAGE supply the human-readable and encoded diagnostic text associated with the error.

Combination resolution and attribute retrieval are handled by NEW_COMBINATION, which creates or registers a new code combination, and COMBINATION_ID, which returns the internal identifier for a validated combination. A group of accessors expose combination attributes: SEGMENT_DELIMITER returns the delimiter used to join segment values; CONCATENATED_VALUES returns the joined segment values; CONCATENATED_IDS returns the joined segment value identifiers; and CONCATENATED_DESCRIPTIONS returns the joined segment descriptions. ENABLED_FLAG, SUMMARY_FLAG, START_DATE, and END_DATE return the corresponding control attributes governing the combination's availability and date range.

Tables Accessed

The ETRM excerpt documents dependencies on FND_FLEX_KEYVAL itself along with FND_FLEX_SERVER, FND_FLEX_SERVER1, FND_GLOBAL, and FND_MESSAGE, plus SYS standards such as DBMS_STANDARD and STANDARD. No explicit table list is enumerated in the supplied metadata; the package operates against the Flexfields Foundation schema objects, principally FND_ID_FLEX_STRUCTURES, FND_ID_FLEX_SEGMENTS, FND_FLEX_VALUES, and FND_FLEX_VALUE_SETS, accessed through APPS synonyms. These tables provide the structure definition, segment definitions, valid value definitions, and value set hierarchy data required to validate combinations and enforce security. FND_GLOBAL supplies session context such as the current application and user, and FND_MESSAGE provides translation of error codes into messages.

Usage Notes

Custom code should not call FND_FLEX_KEYVAL directly in preference to the higher-level, supported FND_FLEX_APIS interface, which wraps these routines. Where direct use is required, the package is typically invoked from Forms-based flexfield validation triggers, from concurrent programs that build or validate accounting combinations, and from PL/SQL APIs and interfaces that must confirm a code combination before posting journal or distribution data. Because the package is depended upon by 106 other packages, changes to its behavior propagate widely across the application, and any extension or override should be carefully assessed against standard validation and security semantics.