Results for “gl_lookups_yes_no_v”

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

Overview

GL_LOOKUPS_YES_NO_V is a simple database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It resides in the General Ledger (GL) product family and is catalogued in the E-Business Suite Technical Reference Manual (ETRM) as a View object with a status of VALID. The documented description is terse—"10SC ONLY"—indicating that the object was originally introduced to satisfy a narrow requirement, historically associated with a specific localization or historical code line rather than a broadly reused seeded component.

Functionally, the view presents a filtered, two-column projection of the YES/NO lookup values maintained in the GL_LOOKUPS repository. Rather than exposing the full lookup record, it restricts output to rows whose LOOKUP_TYPE equals 'YES/NO' and renames the two returned columns to application-friendly aliases. Its role in EBS reporting and integration is therefore one of convenience: it provides a ready-made, pre-filtered list of Yes/No code-and-meaning pairs that forms, report, or interface logic can consume without embedding the lookup-type predicate directly in each query. Because it is a view and not a table, it carries no independent storage and always reflects the current state of the underlying lookup data.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: GL_LOOKUPS, itself identified as a VIEW in the metadata. This is consistent with the standard EBS design in which GL_LOOKUPS is a synonym or view layered over the FND_LOOKUPS / FND_LOOKUP_VALUES infrastructure that stores all Oracle Application Object Library lookup types and their translated meanings.

The relationship between the two objects is direct and one-to-one at the row level. GL_LOOKUPS_YES_NO_V applies a WHERE clause predicate on the LOOKUP_TYPE column of GL_LOOKUPS, retaining only the rows belonging to the 'YES/NO' lookup type, and projects two of the available columns forward under new aliases. No joins, aggregations, or outer queries are involved. Because the base object is itself a view, GL_LOOKUPS_YES_NO_V is effectively a view over a view, which means any change to lookup values—insertions of new enabled codes, updates to meanings, or end-dating of obsolete values—is immediately visible through this object without recompilation.

Key Columns

The view exposes exactly two columns, both derived from the base lookup record:

• YES_NO — Maps to GL_LOOKUPS.LOOKUP_CODE. This is the stored code value for a Yes/No entry (conventionally 'Y' and 'N' in the seeded data). It is the value that would ordinarily be stored in, or compared against, application columns that reference the YES/NO lookup type.
• SHOW_YES_NO — Maps to GL_LOOKUPS.MEANING. This is the translated, user-facing description of the code, such as "Yes" or "No." Its naming suggests its intended purpose: supplying a display-ready label alongside the stored code for use in reports, list-of-values definitions, or user-facing output.

Notably, the view does not expose attributes such as ENABLED_FLAG, START_DATE_ACTIVE, or END_DATE_ACTIVE. Consumers requiring only currently enabled values must therefore apply their own filtering or rely on the semantics of the underlying GL_LOOKUPS view, which may already restrict output to active rows. This is an important consideration when the view is used to drive validation logic.

Common Use Cases and Queries

The principal use cases for GL_LOOKUPS_YES_NO_V are report parameter lists, concurrent program value sets, and interface or conversion logic that must present or resolve Yes/No indicators. A typical reporting query joins the view to a transactional table to render a readable flag:

• Decoding a stored flag: SELECT t.transaction_id, v.SHOW_YES_NO FROM ap_invoices_all t, gl_lookups_yes_no_v v WHERE t.pay_group_lookup_code = v.yes_no;
• Populating a list of values: SELECT SHOW_YES_NO, YES_NO FROM apps.gl_lookups_yes_no_v ORDER BY YES_NO DESC;
• Resolving a code to its meaning: SELECT SHOW_YES_NO FROM apps.gl_lookups_yes_no_v WHERE YES_NO = 'Y';

Because the object is small, static in structure, and fully dependent on seeded lookup data, it is inexpensive to query and safe for repeated use in loops. It should not be treated as an extension point: new Yes/No values are added through the Application Developer responsibility against the YES/NO lookup type, not by modifying this view. Given the "10SC ONLY" designation in the ETRM, implementations should verify availability in their specific environment before adopting it as a hard dependency, and consider querying GL_LOOKUPS or FND_LOOKUPS directly where portability across releases is required.