Search Results flex_valueset_longlist_flag

Overview

APPS.EGO_VS_DISPLAY_CODES_V is a reporting view in Oracle E-Business Suite that exposes the seeded lookup values governing the display behavior of extensible flexfield value sets. The view is defined over FND_LOOKUP_VALUES and filters that table to a single lookup type, FLEX_VALUESET_LONGLIST_FLAG, returning only the codes N and X. Its purpose is to supply the set of permissible "long list" display flags that the value set definition UI and related validation logic use when determining how a value set presents its list of values to the end user.

In EBS 12.1.1 and 12.2.2, the view is owned by APPS and is exposed as a read-only reporting and integration surface. Rather than letting consumers query FND_LOOKUP_VALUES directly — where the same lookup type may be filtered by application, language, or other context — EGO_VS_DISPLAY_CODES_V encapsulates the correct predicates, including VIEW_APPLICATION_ID = 0 and LANGUAGE = USERENV('LANG'), so that each user session sees the values in the appropriate language.

Underlying Base Objects

The view is defined over a single referenced base object: FND_LOOKUP_VALUES, accessed through a synonym. The view text is essentially a filtered projection of that table:

• LOOKUP_TYPE predicate restricts rows to FLEX_VALUESET_LONGLIST_FLAG.
• LOOKUP_CODE predicate restricts rows to N and X.
• VIEW_APPLICATION_ID = 0 selects the shared, non-application-specific lookup rows.
• LANGUAGE = USERENV('LANG') returns the translated meaning for the session language.

Because no join, union, or aggregation is present, the view is a lightweight, low-cost access path. It inherits the security and enablement characteristics of FND_LOOKUP_VALUES, so disabled or date-inactive lookup rows remain visible in the projection (the ENABLED_FLAG and active date columns are carried through rather than filtered).

Key Columns

• LOOKUP_CODE — the flag value itself, either N or X. This is the value stored against the flexfield value set definition.
• MEANING — the translated, user-facing description of the flag, resolved for the session language via USERENV('LANG').
• ENABLED_FLAG — indicates whether the lookup row is currently enabled; consumers may use this to hide retired options.
• START_DATE (START_DATE_ACTIVE) — the date from which the lookup value becomes effective.
• END_DATE (END_DATE_ACTIVE) — the date after which the lookup value is no longer effective.

Common Use Cases and Queries

Typical scenarios include populating a list of values on a custom concurrent program parameter or an OAF page that lets a user set the long list flag on a value set, and producing validation reports confirming which flags are available. A standard query is:

• SELECT LOOKUP_CODE, MEANING, ENABLED_FLAG, START_DATE, END_DATE FROM APPS.EGO_VS_DISPLAY_CODES_V;
• To restrict to currently enabled options: ... WHERE ENABLED_FLAG = 'Y' AND SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE + 1);
• To build a lookup join: SELECT v.SEGMENT1, d.MEANING FROM FND_FLEX_VALUES_VL v, APPS.EGO_VS_DISPLAY_CODES_V d WHERE v.LONGLIST_FLAG = d.LOOKUP_CODE;

Because the view already constrains LOOKUP_TYPE, LOOKUP_CODE, application, and language, callers avoid duplicating those predicates and remain insulated from changes to the underlying lookup configuration.