Results for “show_inquiry_type”

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

Overview

GL_LOOKUPS_BUDGET_INQ1_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the General Ledger (GL) product family and is registered in the E-Business Suite Technical Reference Manual (ETRM) with a status of VALID. The documented description of the object is limited to the notation "10SC ONLY," indicating that the view is a single-purpose, narrowly scoped artifact rather than a general-purpose reporting interface. Its function is to expose a single filtered lookup row from the General Ledger lookup repository, specifically the budget inquiry type value used by inquiry screens and related setup logic.

Rather than returning a result set of many lookups, the view hard-codes its filter predicates so that the caller always receives one row describing the "D" lookup code under the BUDGET_INQUIRY_TYPE lookup type. This makes it a convenience view: consumers do not need to know the underlying lookup type or code values to retrieve the meaning and description of that entry. In EBS reporting and integration terms, the view behaves as a static configuration lookup source that can be joined or referenced by concurrent programs, forms-based inquiry blocks, and custom SQL used for validation and display.

Underlying Base Objects

The view is defined over a single documented base object: GL_LOOKUPS, itself a view within the APPS schema. GL_LOOKUPS is the General Ledger lookup repository that stores lookup types, lookup codes, meanings, descriptions, and related attributes such as enabled flags, display order, and date ranges.

The defining query of GL_LOOKUPS_BUDGET_INQ1_V is:

SELECT LK.LOOKUP_CODE INQUIRY_TYPE, LK.MEANING SHOW_INQUIRY_TYPE, LK.DESCRIPTION DESCRIPTION FROM GL_LOOKUPS LK WHERE LK.LOOKUP_TYPE = 'BUDGET_INQUIRY_TYPE' AND LK.LOOKUP_CODE = 'D'

The relationship is therefore a straightforward projection and restriction: all three output columns are drawn directly from GL_LOOKUPS, with column aliases applied, and the predicate set is fixed to the BUDGET_INQUIRY_TYPE lookup type and the specific lookup code "D". Because GL_LOOKUPS is itself a view, the view inherits any base-table dependencies of that object, but the ETRM documents only GL_LOOKUPS as the referenced base object. No joins, aggregates, or subqueries are present, and no base tables are modified, so the view is purely read-only and incurs no maintenance overhead beyond the cost of resolving the lookup query.

Key Columns

• INQUIRY_TYPE — Alias for LK.LOOKUP_CODE. For this view it always resolves to the literal value 'D', representing the budget inquiry type code as stored in GL_LOOKUPS.
• SHOW_INQUIRY_TYPE — Alias for LK.MEANING. Provides the user-facing, translated meaning associated with the "D" lookup code, which is suitable for direct display in inquiry screens and report output.
• DESCRIPTION — Alias for LK.DESCRIPTION. Supplies the extended descriptive text maintained against the lookup entry in the lookup repository.

Because the filter is fixed, every column value is effectively a constant row from the perspective of the caller. Any variability in the returned data comes from the underlying lookup maintenance performed in the GL lookup tables, such as changes to the meaning or description of the "D" code under BUDGET_INQUIRY_TYPE.

Common Use Cases and Queries

The view is most commonly used where a caller needs the display text for the budget inquiry type without embedding lookup type and code literals in application SQL. Typical scenarios include inquiry form logic that labels budget inquiry results, custom concurrent programs that print budget inquiry reports, and integration extracts that require the descriptive meaning rather than the raw code.

A basic retrieval of the single row is straightforward:

SELECT INQUIRY_TYPE, SHOW_INQUIRY_TYPE, DESCRIPTION FROM APPS.GL_LOOKUPS_BUDGET_INQ1_V;

The view can also be joined to transactional or inquiry data on the inquiry type code, for example:

SELECT b.inquiry_type, v.show_inquiry_type, v.description FROM ap_budget_inquiry b, apps.gl_lookups_budget_inq1_v v WHERE b.inquiry_type = v.inquiry_type;

Because the view returns exactly one row, such joins do not multiply result sets. Consumers should be aware that the view is documented as "10SC ONLY," so its intended scope is limited and it should not be treated as a general lookup access layer. Where broader lookup coverage is required, querying GL_LOOKUPS directly with the appropriate BUDGET_INQUIRY_TYPE filter is preferable.