Search Results validate_default_type

Overview

The APPS.FND_FLEX_TYPES package body is a foundational Oracle E-Business Suite utility that centralizes validation of the code values used throughout the Key Flexfield and Descriptive Flexfield infrastructure. Flexfields rely on a large set of controlled lookup categories — default types, range codes, field types, segment value types, validation events, column types, and yes/no flags — each stored as a lookup type in the FND_LOOKUPS repository. Rather than allowing every flexfield maintenance routine to re-implement lookup verification, this package provides a single, reusable validation layer. Its header revision, AFFFTYPB.pls 120.2.12010000.1, identifies it as a long-standing core component shipped with the 11i and R12 application technology stack. In EBS 12.1.1 and 12.2.2, the package serves as the canonical gatekeeper that confirms a supplied code is an enabled, currently effective lookup before the calling program proceeds with configuration or validation logic.

Key Procedures and Functions

The package exposes nine documented entry points. The core routine is VALIDATE_TYPE, which performs a lookup against FND_LOOKUPS matching the supplied lookup type and code while enforcing ENABLED_FLAG = 'Y' and the active date window. When no matching row is found, a NO_DATA_FOUND exception is raised to the caller. Seven thin wrapper procedures delegate to this core routine with a fixed lookup type:

• VALIDATE_DEFAULT_TYPE — validates against the FLEX_DEFAULT_TYPE lookup category.
• VALIDATE_RANGE_CODE — validates against the RANGE_CODES category.
• VALIDATE_FIELD_TYPE — validates against the FIELD_TYPE category.
• VALIDATE_SEGVAL_TYPE — validates against the SEG_VAL_TYPES category.
• VALIDATE_EVENT_TYPE — validates against the FLEX_VALIDATION_EVENTS category.
• VALIDATE_COLUMN_TYPE — validates against the COLUMN_TYPE category.
• VALIDATE_YES_NO_FLAG — validates against the YES_NO category.

The function GET_CODE performs the inverse translation, accepting a lookup type and meaning and returning the corresponding lookup code, preferring the US language row via a decode-based priority ordering. The procedure AD_DD_USED_BY_FLEX is documented as the ninth entry point and supports the Application Object Library dictionary dependency checks that track flexfield usage of database columns.

Tables Accessed

The package reads from FND_LOOKUPS through the FND_LOOKUP_VALUES APPS synonym, which supplies both the validation source and the code resolution used by GET_CODE. The dictionary-related routine AD_DD_USED_BY_FLEX references FND_COLUMNS and FND_TABLES, the AOL data dictionary views that describe registered table and column metadata. No table in the documented set is written; the package is strictly read-oriented validation logic.

Usage Notes

FND_FLEX_TYPES is referenced by at least three other packages and is invoked throughout the flexfield maintenance layer. Typical callers include the flexfield definition forms and their underlying PL/SQL libraries, which validate user-entered default types, range codes, and segment value attributes before committing configuration. Custom concurrent programs and extensions that manipulate flexfield definitions should call these procedures instead of querying FND_LOOKUPS directly, thereby inheriting the enabled-flag and effective-date checks. Because validation failures raise NO_DATA_FOUND, invoking code must supply its own exception handling to present meaningful messages to the user. The package requires no initialization and is safe to call from any APPS session.