Results for “inquiry_type”

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

Overview

GL_LOOKUPS_BUDGET_INQ3_V is a read-only database view owned by the APPS schema within the Oracle E-Business Suite General Ledger (GL) product family. Its documented description in the ETRM metadata is simply "10SC ONLY," indicating that the object is scoped to a specific localization or single-country deployment rather than being part of the standard global feature set. The view serves as a filtered projection of the GL_LOOKUPS lookup repository, restricted to a single lookup type: BUDGET_INQUIRY_TYPE.

The view presents the set of valid budget inquiry types available to the application, exposing each lookup code under the alias INQUIRY_TYPE along with its user-facing meaning and description. In reporting and integration contexts, such a view acts as a controlled enumeration source: rather than querying GL_LOOKUPS directly and re-filtering on the lookup type, downstream reports, concurrent programs, or interfaces can consume the view to obtain a clean, pre-filtered list of inquiry type values. This pattern is common in EBS where lookup-driven LOVs and validation lists are surfaced through dedicated views to simplify developer access and reduce duplication of filter logic.

Underlying Base Objects

The view is defined over a single referenced base object, GL_LOOKUPS, which is itself implemented as a view in the APPS schema. GL_LOOKUPS is the core lookup repository for the General Ledger module, holding code/meaning pairs organized by LOOKUP_TYPE, and is itself typically layered over the underlying FND_LOOKUPS (or FND_LOOKUP_VALUES) dictionary tables.

The defining query selects from GL_LOOKUPS with a hard-coded predicate that restricts rows to the BUDGET_INQUIRY_TYPE lookup type. No joins, unions, or additional filters are present. The relationship between the view and its base object is therefore one-to-many in the sense that a single GL_LOOKUPS row qualifies for inclusion only when its LOOKUP_TYPE equals the budget inquiry type; all other lookup types in GL_LOOKUPS are excluded from the result set. Because GL_LOOKUPS is a view rather than a base table, values exposed here ultimately derive from the seeded lookup dictionary and are maintained through the standard lookup maintenance forms rather than by direct DML.

Key Columns

• INQUIRY_TYPE — Aliased from GL_LOOKUPS.LOOKUP_CODE. This is the stored code value representing a budget inquiry type. It is the column most often referenced in WHERE clauses and joins, and it corresponds to the value persisted against budget inquiry data.
• SHOW_INQUIRY_TYPE — Aliased from GL_LOOKUPS.MEANING. This is the display-friendly label presented to users, typically shown in list of values windows, report prompts, and inquiry screens.
• DESCRIPTION — Aliased from GL_LOOKUPS.DESCRIPTION. Provides supplementary explanatory text for the lookup value, useful for help text, documentation extracts, and detailed reporting where the meaning alone is insufficient.

The three columns mirror the conventional code/meaning/description triplet used throughout EBS lookup views, allowing the view to be treated as a standard lookup source by generic lookup-handling code and by ad hoc SQL.

Common Use Cases and Queries

Typical uses include populating report parameters, validating user-entered inquiry types, and joining inquiry type codes to their meanings in budget inquiry extracts.

The simplest form of access retrieves the complete enumeration:

SELECT inquiry_type, show_inquiry_type, description
FROM   apps.gl_lookups_budget_inq3_v
ORDER BY show_inquiry_type;

Where a report stores the code and must display the meaning, the view is joined on the code value:

SELECT b.inquiry_type, l.show_inquiry_type
FROM   budget_inquiry_data b,
       apps.gl_lookups_budget_inq3_v l
WHERE  b.inquiry_type = l.inquiry_type;

A validation query confirms that a supplied value is a defined inquiry type before submission to a concurrent program or interface:

SELECT 'Y'
FROM   apps.gl_lookups_budget_inq3_v
WHERE  inquiry_type = :p_inquiry_type;

Because the view is pre-filtered to BUDGET_INQUIRY_TYPE, these statements require no additional lookup type predicate, and remaining consistent with the "10SC ONLY" designation, its use should be confined to the deployments for which it was provided.