Search Results gl_lookups_batch_type_v




Overview
Explore in AI Chat

Overview

The GL_LOOKUPS_BATCH_TYPE_V view is a lightweight lookup projection owned by the APPS schema in Oracle E-Business Suite General Ledger (GL). Per the ETRM documentation, its status is VALID, and its description is recorded as "10SC ONLY," indicating that this object is a specialized, legacy-oriented construct rather than a core, widely referenced General Ledger view. The view presents a filtered, renamed subset of rows from the GL_LOOKUPS lookup repository, specifically those whose LOOKUP_TYPE equals 'BATCH_TYPE'.

The view exposes exactly two columns: ACTUAL_FLAG, which is sourced from LOOKUP_CODE, and SHOW_ACTUAL_FLAG, which is sourced from DESCRIPTION. The inclusion of the user search term "show_actual_flag" aligns directly with the second column, confirming that the view's primary purpose is to surface a display-oriented label (SHOW_ACTUAL_FLAG) keyed against an internal code (ACTUAL_FLAG). In effect, the view behaves as a simple code-to-description translation layer for batch-type values, suitable for reporting and integration consumers that require a human-readable batch type label rather than the raw lookup code.

Underlying Base Objects

The view is defined over a single documented base object: GL_LOOKUPS. Notably, the ETRM metadata classifies GL_LOOKUPS itself as a VIEW rather than a physical base table, which is consistent with Oracle EBS conventions where GL_LOOKUPS is frequently exposed to the APPS layer through synonym or view wrappers over the underlying lookup storage.

The defining view text is straightforward:

  • Source: GL_LOOKUPS L
  • Filter predicate: L.LOOKUP_TYPE = 'BATCH_TYPE'
  • Projected columns: L.LOOKUP_CODE AS ACTUAL_FLAG and L.DESCRIPTION AS SHOW_ACTUAL_FLAG

Because the view performs no joins, it inherits the row-filtering semantics of the BATCH_TYPE lookup set. Any addition, inactivation, or termination of BATCH_TYPE lookup codes in the lookup repository is immediately reflected in this view, making it a real-time, non-materialized projection with no aggregation or transformation logic beyond column aliasing and the type filter.

Key Columns

  • ACTUAL_FLAG — Mapped from GL_LOOKUPS.LOOKUP_CODE. This is the internal, coded identifier associated with a BATCH_TYPE lookup entry. Within the General Ledger context, actual flags conventionally distinguish actual versus budget or encumbrance balances, so this column carries the operative value used for logic and filtering.
  • SHOW_ACTUAL_FLAG — Mapped from GL_LOOKUPS.DESCRIPTION. This is the descriptive, display-ready text corresponding to the code. It is the column most relevant to the user's search term and is intended for presentation in reports, LOVs, and user interfaces.

Because only these two columns are exposed, the view does not carry lookup enablement dates, tag fields, or language attributes. Consumers requiring such attributes must query GL_LOOKUPS directly.

Common Use Cases and Queries

Typical usage centers on resolving BATCH_TYPE codes to descriptive labels. The most direct query retrieves the full mapping:

  • SELECT ACTUAL_FLAG, SHOW_ACTUAL_FLAG FROM APPS.GL_LOOKUPS_BATCH_TYPE_V;
  • SELECT SHOW_ACTUAL_FLAG FROM APPS.GL_LOOKUPS_BATCH_TYPE_V WHERE ACTUAL_FLAG = :p_actual_flag;
  • Joining to batch-bearing tables: SELECT b.batch_name, v.SHOW_ACTUAL_FLAG FROM gl_batches b, APPS.GL_LOOKUPS_BATCH_TYPE_V v WHERE b.actual_flag = v.ACTUAL_FLAG;

These patterns support lookup population in concurrent programs, value-set validation, and report rendering. Given the "10SC ONLY" designation, deployments should confirm availability on the target instance before embedding the view in custom code, and should prefer standard GL lookup APIs where portability across releases (12.1.1 and 12.2.2) is required.