Results for “status_flag”

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

Overview

The GL_LOOKUPS_BUDGET_STATUSES_V view is a seeded database object owned by the APPS schema within the Oracle E-Business Suite General Ledger (GL) module. It exists to expose a filtered, human-readable list of budget or plan/version status codes drawn from the GL lookups repository. According to the ETRM metadata, this object is documented with the description "10SC ONLY," indicating that its use is scoped to a specific configuration or localization rather than being a general-purpose global view in all implementations. The view is registered as VALID in the ETRM repository for both the 12.1.1 and 12.2.2 releases.

The view serves a reporting and integration role. Rather than requiring report authors or integration developers to hard-code a lookup type filter against the base GL_LOOKUPS view, it delivers a pre-filtered, renamed result set. The two exposed columns map the stored lookup code to a user-facing meaning, which streamlines the presentation of budget status information in custom reports, concurrent programs, and interface tables.

Underlying Base Objects

The view is defined over a single documented base object, GL_LOOKUPS, which is itself a view in the APPS schema. The defining query is:

SELECT L.LOOKUP_CODE STATUS_FLAG,
       L.MEANING    SHOW_STATUS
  FROM GL_LOOKUPS L
 WHERE L.LOOKUP_TYPE = 'PLAN/VERSION STATUS'

This statement restricts the rows of GL_LOOKUPS to those whose LOOKUP_TYPE equals 'PLAN/VERSION STATUS'. Only the LOOKUP_CODE and MEANING columns are carried forward into the view. Because the source object is a view, no direct DML is intended against GL_LOOKUPS_BUDGET_STATUSES_V; it is a read-only projection suitable for query and reference purposes only.

Key Columns

• STATUS_FLAG — Derived from GL_LOOKUPS.LOOKUP_CODE. This is the internal, stored code that identifies a specific plan or version budget status. It is the value typically held in transactional or configuration columns elsewhere in the application and is the correct column to use in joins and WHERE predicates.
• SHOW_STATUS — Derived from GL_LOOKUPS.MEANING. This is the descriptive, user-facing text associated with the status code. The column name itself reflects the "show_status" search term, making it the natural choice for display purposes in reports, forms, and interfaces.

Both columns are character data, consistent with the Oracle Applications lookup framework, where lookup codes and their meanings are stored as alphanumeric strings.

Common Use Cases and Queries

The primary use case is resolving status codes to descriptive labels in General Ledger budget and plan version reporting. Typical scenarios include budget version status lists in concurrent reports, LOV-style queries in custom forms, and interface or conversion programs that must map a stored status flag to its descriptive meaning. A straightforward query returning all available statuses is:

SELECT STATUS_FLAG, SHOW_STATUS
  FROM APPS.GL_LOOKUPS_BUDGET_STATUSES_V
 ORDER BY SHOW_STATUS;

To resolve a specific code encountered in transactional data, a join or filter is used:

SELECT STATUS_FLAG, SHOW_STATUS
  FROM APPS.GL_LOOKUPS_BUDGET_STATUSES_V
 WHERE STATUS_FLAG = :p_status_flag;

Because the view is described as "10SC ONLY," implementers should confirm applicability within their specific configuration before relying on it, and should verify row counts against the underlying GL_LOOKUPS entries of type PLAN/VERSION STATUS. Where the view is not appropriate, the equivalent query can be issued directly against GL_LOOKUPS with the same lookup type filter.