Results for “fnd_flex_server2”

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

Overview

APPS.FND_FLEX_SERVER2 is a server-side PL/SQL package within the Oracle E-Business Suite Flexfields architecture. It operates in conjunction with FND_FLEX_SERVER1, which supplies the shared PL/SQL record types (ValueArray, SegFormats, FlexStructId, FlexStructInfo, CombTblInfo, DescFlexInfo, TabColArray, CharArray, Qualifiers) referenced throughout the package specification. Together these packages implement the low-level validation, structure resolution, and metadata retrieval services that underpin both Key Flexfields and Descriptive Flexfields across all EBS applications.

The package is not an end-user or form-facing API. It is an internal engine used by the flexfield validation layer to perform cross-validation of segment combinations, resolve flexfield structures from application and flexfield identifiers, and expose column and qualifier metadata used to build dynamic SQL. The header comment (AFFFSV2S.pls, 120.1.12010000.1, 2008/07/25) confirms its long-standing role as a core flexfield infrastructure component. It is referenced by four other packages, indicating that it functions as a dependency for higher-level flexfield processing routines rather than as a top-level entry point.

Key Procedures and Functions

• CROSS_VALIDATE — Validates a combination of segment values against the rules defined for a flexfield structure, returning a status code and an error column indicator when validation fails.
• X_DROP_CACHED_CV_RESULT — Removes a previously cached cross-validation result for a given structure and segment set, returning a Boolean status.
• X_CLEAR_CV_CACHE — Flushes the entire cross-validation result cache maintained by the package.
• SUBMIT_RXR_REPORT — Submits an Oracle Reports (RXR) concurrent request for flexfield-related reporting, accepting parameters such as application, flexfield code, flexfield number, update flag, worker count, and debug flag, with standard errbuf/retcode outputs.
• GET_KEYSTRUCT — Resolves a key flexfield structure from the application short name, flexfield code, view selection, and flexfield number, returning structure, table, and combination-table metadata.
• GET_DESCSTRUCT — Resolves a descriptive flexfield structure and returns its descriptor information.
• GET_STRUCT_COLS — Returns the columns, column types, and segment formats associated with a flexfield structure for a given table.
• GET_ALL_SEGQUALS — Returns all segment qualifiers defined for a flexfield structure.
• GET_QUALSEGS — Returns the segments associated with a particular qualifier.
• BREAKUP_CATSEGS — Decomposes concatenated segment strings, supporting the parsing of category or concatenated segment values.

Tables Accessed

The package reads flexfield definition and metadata tables through APPS synonyms. FND_ID_FLEXS, FND_ID_FLEX_STRUCTURES, and FND_ID_FLEX_SEGMENTS supply flexfield and structure definitions and segment attributes. FND_FLEX_VALUE_SETS and FND_SEGMENT_ATTRIBUTE_VALUES provide value set and attribute configuration used during validation. FND_DESCR_FLEX_COLUMN_USAGES supports descriptive flexfield column resolution, while FND_COLUMNS, FND_TABLES, and FND_VALUE_ATTRIBUTE_TYPES supply table, column, and attribute type metadata. FND_APPLICATION resolves application identifiers. DBMS_SQL and PLITBLM are used for dynamic SQL and PL/SQL table handling, consistent with the package's dynamic SQL generation role.

Usage Notes

FND_FLEX_SERVER2 is typically invoked indirectly through the flexfield validation and structure-resolution stack rather than directly by forms or concurrent programs. It is called by four other packages, which in turn serve form-level validation, concurrent program processing, and custom extensions requiring programmatic combination validation. Custom code should generally use the public flexfield APIs (such as FND_FLEX_KEYVAL or FND_FLEX_EXT) instead of calling this package directly, since its interface is internal, subject to change between releases, and dependent on the shared types defined in FND_FLEX_SERVER1. The SUBMIT_RXR_REPORT procedure is the one documented entry point tied to concurrent processing, reflecting the package's secondary role in flexfield reporting.