Search Results up_vset_security_rule

Overview

APPS.FND_FLEX_LOADER_APIS is a public PL/SQL package in Oracle E-Business Suite that serves as the programmatic loader interface for the Oracle Flexfields repository. Its principal business function is to create, update, and maintain flexfield metadata definitions — value sets, descriptive flexfields, and key flexfields — without requiring the administrator to navigate the Flexfields form-based user interface. The package encapsulates the full upload lifecycle for flexfield components across all supported EBS releases, including 12.1.1 and 12.2.2.

The package is designed around a phased upload model. Each upload procedure accepts an upload phase and upload mode, and an optional custom mode that lets the loader honor site-specific customizations. Inputs are passed as VARCHAR2 strings rather than native typed parameters, which allows the loader to accept values from external sources, including flat files, staging tables, and concurrent program parameters. A WHO record type (who_type) carries the standard audited columns — created_by, creation_date, last_updated_by, last_update_date, and last_update_login — so that loader-driven changes retain proper audit attribution.

Key Procedures and Functions

The package exposes two session-control utilities. SET_CONTEXT establishes the runtime context for the loader session, and SET_DEBUGGING enables or disables diagnostic output for troubleshooting upload operations.

The bulk of the API surface consists of upload procedures organized by flexfield object family. For value sets, UP_VALUE_SET handles the value set definition itself; UP_VSET_DEPENDS_ON and UP_VSET_TABLE manage dependent and table-validated value sets; UP_VSET_EVENT manages event-based validation; UP_VSET_SECURITY_RULE, UP_VSET_SECURITY_LINE, and UP_VSET_SECURITY_USAGE maintain hierarchical security rules, their constituent lines, and assignment of security to value sets. UP_VSET_ROLLUP_GROUP and UP_VSET_QUALIFIER support rollup groupings and value qualifiers, while UP_VSET_VALUE, UP_VSET_VALUE_HIERARCHY, and UP_VSET_VALUE_QUAL_VALUE load individual values, their hierarchies, and qualified value assignments.

For descriptive flexfields, the package provides UP_DESC_FLEX, UP_DFF_COLUMN, UP_DFF_CONTEXT, and UP_DFF_SEGMENT to load the DFF structure, its columns, context definitions, and context-sensitive segments. For key flexfields, UP_KEY_FLEX and UP_KFF_COLUMN load structure definitions and key segment columns. Notably, the documented API list includes UP_DFF_CONTEXT, which is the procedure relevant to the user search term "up_dff_context" — it manages descriptive flexfield context records.

Tables Accessed

The loader writes to and reads from the core flexfield repository tables. Value set definitions and their relationships are maintained through FND_DESCRIPTIVE_FLEXS and its translation table FND_DESCRIPTIVE_FLEXS_TL. Context and column usage data are held in FND_DESCR_FLEX_CONTEXTS, FND_DESCR_FLEX_CONTEXTS_TL, FND_DESCR_FLEX_COLUMN_USAGES, FND_DESCR_FLEX_COL_USAGE_TL, and FND_DEFAULT_CONTEXT_FIELDS. Compiled runtime representations are refreshed or referenced through FND_COMPILED_DESCRIPTIVE_FLEXS, FND_COMPILED_ID_FLEXS, and FND_COMPILED_ID_FLEX_STRUCTS.

Supporting tables include FND_COLUMNS for segment-to-column mapping, FND_APPLICATION for application ownership, and FND_FLEX_EXCLUDE_RULE_LINES for exclusion rules. Concurrency and scheduling information is read from FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS, consistent with the package's typical execution under a concurrent program.

Usage Notes

FND_FLEX_LOADER_APIS is normally invoked from concurrent programs — often wrapped in a custom loader program that reads a staging table or interface file and calls the appropriate UP_* procedure for each record. It may also be called directly from custom PL/SQL scripts during data migration, environment cloning, or multi-org setup, and it is referenced by fourteen other packages, which indicates it acts as a dependency for higher-level flexfield utilities rather than an end-user entry point. Because the procedures accept string parameters, callers must ensure values are correctly formatted and that prerequisites (such as the parent value set name before a dependent value set) are loaded in the correct order. Direct table manipulation should be avoided in favor of these APIs so that validation, audit stamping, and compiled flexfield synchronization remain intact.