Search Results get_vst_set

Overview

FND_FLEX_LOADER_APIS is the core PL/SQL package body that powers the Oracle E-Business Suite Flexfield Loader. Its business function is to load and maintain Flexfield definitions — Value Sets, Descriptive Flexfields (DFF), and Key Flexfields (KFF) — into an EBS instance from structured external source files and loader interfaces. In practice, the package is the engine behind the Flexfield Loader, which is used largely for migrating flexfield metadata and value sets between environments (for example, development to test to production) or for bulk-loading flexfield configuration rather than defining each component manually through the Flexfields windows.

The package exposes a family of "UP_" (upload) APIs that parse and apply loader input, together with supporting utilities for debugging, context management, and change tracking. It is registered in ETRM with the API classification OTHER and is referenced by fourteen other packages, confirming its role as a shared foundational component rather than an application-facing user API. The user search term "get_vst_set" relates to value set handling, which is the central subject matter of this package.

Key Procedures and Functions

The body contains 41 documented procedures and functions. The "UP_" procedures constitute the loader entry points. UP_VALUE_SET loads value set definitions and their associated attributes. UP_VSET_DEPENDS_ON, UP_VSET_TABLE, UP_VSET_EVENT, UP_VSET_ROLLUP_GROUP, UP_VSET_QUALIFIER, UP_VSET_VALUE, UP_VSET_VALUE_HIERARCHY, and UP_VSET_VALUE_QUAL_VALUE load the dependent structures that fully describe a value set: its table and value-column bindings, event subscriptions, rollup groups, qualifiers, individual values, hierarchies, and the pairings of values to qualifiers. The UP_VSET_SECURITY_RULE, UP_VSET_SECURITY_LINE, and UP_VSET_SECURITY_USAGE procedures load value set security configuration.

For descriptive flexfields, UP_DESC_FLEX, UP_DFF_COLUMN, UP_DFF_CONTEXT, and UP_DFF_SEGMENT load the flexfield definition, its columns, contexts, and segments. Their key flexfield counterparts are UP_KEY_FLEX and UP_KFF_COLUMN. Two control routines, SET_CONTEXT and SET_DEBUGGING, initialize the session context and the package's internal debug flag, which governs the diagnostic output generated during a load run.

Tables Accessed

The package reads and writes the base Flexfield and concurrent manager tables through APPS synonyms. FND_APPLICATION and FND_COLUMNS identify the owning application and the database columns available for value set and segment binding. FND_DESCRIPTIVE_FLEXS and FND_DESCRIPTIVE_FLEXS_TL hold DFF headers and their translated names; FND_DESCR_FLEX_CONTEXTS and FND_DESCR_FLEX_CONTEXTS_TL hold context definitions; FND_DESCR_FLEX_COLUMN_USAGES and FND_DESCR_FLEX_COL_USAGE_TL hold column usages; and FND_DEFAULT_CONTEXT_FIELDS holds context field defaults. Key flexfield structures are represented by FND_COMPILED_ID_FLEXS, FND_COMPILED_ID_FLEX_STRUCTS, and FND_COMPILED_DESCRIPTIVE_FLEXS, which store the compiled (runtime-optimized) flexfield definitions. FND_FLEX_EXCLUDE_RULE_LINES supports security exclusion rules. The package also references the concurrent manager tables FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS, reflecting its use within concurrent program processing and request tracking.

Usage Notes

FND_FLEX_LOADER_APIS is normally invoked indirectly. It is called by the Flexfield Loader forms and concurrent programs and by the fourteen dependent packages that build on its upload routines. The public loader APIs are organized around module entity constants — ENTITY_VALUE_SET, ENTITY_DESC_FLEX, and ENTITY_KEY_FLEX — and an extensive error constant set (for example ERROR_VST_GENERIC, ERROR_VST_TYPE_MISMATCH, and ERROR_VST_INVALID_PARENT) that callers inspect to diagnose load failures. Custom code should not call the internal routines directly. The package is release-specific; the $Header revision (120.25, dated 2012/03/27) indicates a build shipped for the EBS 12.1.1 and 12.2.2 code lines, and the compiled flexfield tables it populates are regenerated whenever flexfield definitions change, so the package must be used in conjunction with the standard flexfield compilation process.