Search Results budget_inquiry_type

Overview

APPS.GL_LOOKUPS_BUDGET_INQ1_V is a lightweight inquiry view in the Oracle E-Business Suite General Ledger schema. It exposes a single, pre-filtered lookup row from the GL_LOOKUPS foundation table, returning the inquiry type designation used by the Budget Inquiry functionality. Rather than presenting the entire BUDGET_INQUIRY_TYPE lookup set, the view deliberately narrows its result set to the lookup code 'D', delivering one deterministic row that downstream forms, reports, and integrations can consume without embedding the filtering logic themselves.

The view is most relevant to developers and functional analysts searching on the column alias inquiry_type. Because the view assigns the alias INQUIRY_TYPE to the underlying LOOKUP_CODE column, any query, concurrent program, or external interface that references INQUIRY_TYPE against this view will resolve cleanly. The view therefore acts as a stable, semantically named contract over a generic lookup table, insulating callers from the physical structure of GL_LOOKUPS and from knowledge of which lookup_type and lookup_code values are required.

Underlying Base Objects

The view is defined over a single documented base object: GL_LOOKUPS, itself a view in the APPS schema. GL_LOOKUPS is the General Ledger repository of lookup codes keyed by LOOKUP_TYPE, storing the short code, the user-facing meaning, a free-form description, and related attributes such as enabled flag, display sequence, and date ranges.

GL_LOOKUPS_BUDGET_INQ1_V constrains that repository with two predicates. The first restricts rows to LOOKUP_TYPE = 'BUDGET_INQUIRY_TYPE', isolating the lookup set that governs budget inquiry behavior. The second restricts rows to LOOKUP_CODE = 'D'. The combination yields exactly one row under normal data conditions. No joins, aggregations, or subqueries are present, so the view imposes negligible overhead and inherits whatever security and synonyms apply to GL_LOOKUPS. There is no dependency on transactional GL tables, budget balances, or period data.

Key Columns

• INQUIRY_TYPE — Alias for GL_LOOKUPS.LOOKUP_CODE. Returns the literal value 'D', identifying the specific budget inquiry type. This is the column most commonly referenced in search and integration contexts.
• SHOW_INQUIRY_TYPE — Alias for GL_LOOKUPS.MEANING. Returns the translatable, user-facing label associated with lookup code 'D' as maintained by the system administrator. Suitable for display in reports and LOVs.
• DESCRIPTION — Alias for GL_LOOKUPS.DESCRIPTION. Provides the longer explanatory text stored against the lookup code, useful for help text, audit output, or diagnostic reporting.

All three columns are derived from GL_LOOKUPS with no transformation beyond aliasing and filtering. Values reflect the current state of the lookup definition, so administrators can adjust the meaning or description without requiring any change to dependent code.

Common Use Cases and Queries

Typical uses include validating that the budget inquiry lookup is configured, populating a report parameter or LOV with a human-readable inquiry type label, and providing a stable source for integrations that must reference the inquiry type by name rather than by literal.

• Confirming configuration: SELECT inquiry_type, show_inquiry_type FROM apps.gl_lookups_budget_inq1_v;
• Retrieving the display label for reports: SELECT show_inquiry_type FROM apps.gl_lookups_budget_inq1_v;
• Joining to denormalize a stored code: SELECT t.*, v.show_inquiry_type FROM my_budget_tab t, apps.gl_lookups_budget_inq1_v v WHERE t.inquiry_type = v.inquiry_type;

Because the view returns a single row, joins against it are safe from row multiplication. Note that the view exposes only lookup code 'D'; any requirement to enumerate all BUDGET_INQUIRY_TYPE values should query GL_LOOKUPS directly with the appropriate lookup_type predicate.