Search Results x_dsql_select_one

Overview

FND_FLEX_SERVER1 is a private, low-level PL/SQL package in the Oracle E-Business Suite Application Object Library (FND) schema that provides the server-side engine for Oracle Flexfields. It underpins both Key Flexfields (KFF) and Descriptive Flexfields (DFF) by resolving flexfield structure metadata, parsing and validating concatenated segment values, building dynamic SQL, and enforcing cross-validation and security rules against the FND flexfield definition tables. The package is declared as a specification-only shell (PACKAGE fnd_flex_server1 AS) whose header dates to Release 12.0 (120.1.12010000.1), meaning the same source is deployed and shared across 12.1.1 and 12.2.2.

A defining characteristic of the package is its set of private inter-package PL/SQL types, which are the plumbing that lets other FND server packages pass flexfield data efficiently. These include ValueArray, ValueIdArray, ValueDescArray, StringArray, CharArray, NumberArray, BooleanArray, ValAttribArray, QualNameArray, TabColArray, ErrMsgArray, and AppNameArray, together with the composite records FlexStructId and DescFlexInfo. The FlexStructId record carries the key flexfield identity (application, ID flex code, ID flex number) or the descriptive flexfield identity (name and context), while DescFlexInfo carries descriptive flexfield structure attributes such as the context column and context-required flag.

Key Procedures and Functions

The 27 documented entry points group into distinct functional areas:

• Token / clause construction: PARSE_WHERE_TOKEN, X_INRANGE_CLAUSE, X_COMPARE_CLAUSE, SELECT_CLAUSE. These assemble WHERE and SELECT fragments from flexfield segment metadata.
• Validation and security: CHECK_COMB_VRULES enforces cross-validation rules; VALS_SECURED enforces value-set security; VALIDATE_STRUCT confirms a flexfield structure is valid and enabled.
• Dynamic SQL execution: X_DSQL_EXECUTE, X_DSQL_SELECT_ONE, and X_DSQL_SELECT run the generated statements (typically through DBMS_SQL).
• Array conversion utilities: TO_STRINGARRAY/FROM_STRINGARRAY and TO_STRINGARRAY2/FROM_STRINGARRAY2 marshal segment arrays between representations.
• SQL / NSQL generation: ADD_SQL_STRING, GET_SQL_INTERNAL, and GET_NSQL_INTERNAL build the underlying query text used to fetch valid values.
• Global / session state: INIT_GLOBALS primes package state; STORED_DATE_FORMAT resolves date formatting; ISA_NUMBER tests numeric attributes.

Tables Accessed

All access is through APPS synonyms. The package reads flexfield structure and segment definitions from FND_ID_FLEX_SEGMENTS and the descriptive flexfield tables FND_DESCRIPTIVE_FLEXS, FND_DESCRIPTIVE_FLEXS_TL, and FND_DESCR_FLEX_CONTEXTS. Column metadata for DFF segments comes from FND_DESCR_FLEX_COLUMN_USAGES, FND_TABLES, and FND_COLUMNS. Validation metadata is drawn from FND_FLEX_VALIDATION_QUALIFIERS, FND_FLEX_VALIDATION_TABLES, FND_FLEX_VALUE_SETS, FND_VALUE_ATTRIBUTE_TYPES, and FND_SEGMENT_ATTRIBUTE_VALUES. DBMS_SQL and PLITBLM are used for dynamic execution and array manipulation respectively.

Usage Notes

FND_FLEX_SERVER1 is not intended for direct application calls. It is referenced by 11 other FND packages and is invoked indirectly when flexfields are validated through the standard Flexfield Open Interfaces or the AOL forms, and whenever concurrent programs or custom code that manipulate key or descriptive flexfield combinations execute. Because the documented procedures are the internal engine, the term the user searched (“1per connect server 2replug 3”) does not correspond to any documented procedure in this package; the nearest matches are the SQL-assembly routines such as ADD_SQL_STRING and the dynamic-select routines. Integrators and developers should treat FND_FLEX_SERVER1 strictly as a support object and consume flexfields through the supported FND Flexfield API rather than calling these procedures directly.