Results for “ego_vs_format_codes_v”

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

Overview

EGO_VS_FORMAT_CODES_V is a read-only database view owned by the APPS schema within the EGO - Advanced Product Catalog product module of Oracle E-Business Suite. Its purpose is to expose the set of format codes that are applicable to Value Sets supported by the EGO application. In the EBS architecture, value sets define the permissible values and validation behavior used by flexfields, descriptive flexfields, and other key and descriptive segments. The format code associated with a value set determines the data type and validation characteristics of the values it may contain. This view presents the subset of those format codes that EGO recognizes and supports, thereby serving as a controlled reference list for the product catalog and related configuration functions.

From a reporting and integration standpoint, the view acts as a lightweight lookup surface. It allows forms, concurrent programs, OAF pages, and external integrations to retrieve the valid format codes without querying the underlying flexfield lookup infrastructure directly. Because it filters the underlying data to only the four supported codes, consumers of the view are insulated from unrelated lookup values that exist in the base table.

Underlying Base Objects

The view is defined over a single documented base object: FND_LOOKUP_VALUES, which is referenced through a synonym. FND_LOOKUP_VALUES is the standard EBS lookup values table maintained by the Application Object Library. It stores the code, meaning, enabled flag, and active date ranges for every lookup type defined in the system.

EGO_VS_FORMAT_CODES_V applies a fixed set of predicates against this table. It restricts the lookup type to 'FIELD_TYPE', constrains the lookup code to the values 'C', 'N', 'X', and 'Y', requires VIEW_APPLICATION_ID to equal 0, and limits the result to the language of the current user session via USERENV('LANG'). The view therefore does not maintain any data of its own; it is a filtered projection of the lookup values table.

Key Columns

• LOOKUP_CODE — The format code itself. The supported values are C, N, X, and Y, representing the format categories recognized for EGO value sets.
• MEANING — The displayable description of the format code, suitable for use in list of values and user-facing prompts.
• ENABLED_FLAG — Indicates whether the format code is currently enabled. A value of 'Y' indicates active availability.
• START_DATE — The date from which the format code becomes active. This is an alias for START_DATE_ACTIVE in the base table.
• END_DATE — The date on which the format code ceases to be active. This is an alias for END_DATE_ACTIVE in the base table.

Common Use Cases and Queries

A typical use case is populating a list of values for a value set format field in a catalog administration form. Another is validating that a format code configured by a user falls within the EGO-supported set. Reporting on currently active format codes is also common.

The following query returns all enabled format codes that are currently in effect:

SELECT lookup_code, meaning
FROM   apps.ego_vs_format_codes_v
WHERE  enabled_flag = 'Y'
AND    SYSDATE BETWEEN NVL(start_date, SYSDATE)
                   AND NVL(end_date, SYSDATE);

To list all codes with their validity windows for auditing purposes:

SELECT lookup_code, meaning, enabled_flag, start_date, end_date
FROM   apps.ego_vs_format_codes_v
ORDER  BY lookup_code;

Because the view already filters by the user's session language, no additional language predicate is required in these queries. The view is safe for read-only integration use and reflects the underlying lookup configuration at query time.