Search Results get_vst_scu

Overview

FND_FLEX_DIAGNOSE is a diagnostic utility package in the Oracle E-Business Suite Applications (APPS) schema. Its business purpose is to centralize a set of helper functions that return formatted diagnostic strings describing the state of key EBS metadata: the database, the application release, row-level "WHO" audit information, application registration, tables, columns, languages, responsibilities, and Flexfield-related configuration objects. The package name and its header comments ("Common get_something() RETURN VARCHAR2; functions") indicate that its principal role is to produce human-readable, consistently formatted values that are consumed by other diagnostics, Flexfield validation utilities, or troubleshooting routines rather than by transactional business logic.

The package is classified as OTHER in the documented metadata, meaning it is a supporting/utility API rather than a public business API. It is owned by APPS and, per the source header ($Header: AFFFDGNS.pls 120.4.12010000.1), is a long-standing FND component. In the context of Oracle EBS 12.1.1 and 12.2.2, it is most commonly encountered when diagnosing Flexfield definition problems, responsibility/security issues, or when generating standard diagnostic output strings for support and debugging.

Key Procedures and Functions

The package exposes 72 documented procedures and functions, the majority of which are getter-style functions returning VARCHAR2 diagnostic strings. The documented functions include:

• GET_DB — returns database information.
• GET_REL — returns the release (version) information.
• GET_WHO — returns WHO audit information. Two overloads are shown: one that accepts the individual WHO columns (creation date, created by, last update date, last updated by, last update login) and concatenates them into a formatted string, and one that accepts a table name and ROWID and reads the WHO columns from that row. The documented format is 'CD:<creation_date> CB:<created_by> LUD:<last_update_date> LUB:<last_updated_by> LUL:<last_update_login>'.
• GET_APP — returns application information in the documented syntax '<application_id>/<application_short_name>/<application_name>', for example '0/FND/Application Object Library'. This is the function most directly associated with the user's search term "get_app".
• GET_TBL — returns table information formatted as '<table_owner>/<table_name>/<table_id>', for example 'GL/GL_CODE_COMBINATIONS/584'.
• GET_COL, GET_LNG, GET_RSP — return column, language, and responsibility information respectively.
• GET_FB_FUNC, GET_FB_KAPP, GET_FB_KFLX, GET_FB_KSTR — return FlexBuilder function and key (application, flexfield, structure) information.
• GET_VST_SET, GET_VST_TBL, GET_VST_EVT, GET_VST_SCR, GET_VST_SCL, GET_VST_SCU, GET_VST_VAL, GET_VST_RLG — return the various elements of Flexfield validation (VST) configuration: value sets, tables, events, screens, columns, values, and related rules.

Tables Accessed

The package reads from a set of FND dictionary and Flexfield metadata tables through APPS synonyms, including FND_APPLICATION, FND_COLUMNS, FND_COMPILED_DESCRIPTIVE_FLEXS, FND_COMPILED_ID_FLEXS, FND_COMPILED_ID_FLEX_STRUCTS, FND_DEFAULT_CONTEXT_FIELDS, FND_DESCRIPTIVE_FLEXS, FND_DESCR_FLEX_COLUMN_USAGES, FND_DESCR_FLEX_CONTEXTS, FND_FLEXBUILDER_FUNCTIONS, FND_FLEX_EXCLUDE_RULE_LINES, FND_FLEX_HIERARCHIES, FND_FLEX_INCLUDE_RULE_LINES, FND_FLEX_VALIDATION_EVENTS, and FND_FLEX_VALIDATION_QUALIFIERS. These are consulted so that the getter functions can resolve IDs, names, and compiled structures into the formatted diagnostic strings they return (for example, resolving an application_id into its short name and name via FND_APPLICATION).

Usage Notes

FND_FLEX_DIAGNOSE is not referenced by any other documented package (referenced by 0 other packages), so it is typically invoked directly from Flexfield diagnostic forms, concurrent diagnostic programs, or custom troubleshooting code rather than composed into larger PL/SQL APIs. Its functions are best treated as read-only diagnostic helpers: they query metadata and return formatted strings, and they should not be relied upon for transactional behavior. In 12.1.1 and 12.2.2 environments, calling functions such as GET_APP or GET_WHO during Flexfield issue investigation provides a quick, standardized textual representation of the object under examination.