Search Results show_actual_flag




Overview

APPS.GL_LOOKUPS_BATCH_TYPE_V is a lightweight reporting view in the Oracle E-Business Suite General Ledger (GL) module. It exposes a specialized subset of the GL_LOOKUPS lookup repository, filtered exclusively to the lookup type BATCH_TYPE. The view is documented in ETRM for release 12.2.2 and is present in 12.1.1 as well, and is owned by the APPS schema.

The view serves a narrow but important role: it presents the set of valid batch type codes — most commonly A for actuals and B for budgets — alongside their translated, user-facing descriptions. Its principal purpose is to support reporting and integration logic that must resolve a stored batch type code into a descriptive label, or that must enumerate the available batch types when presenting selection lists or validation sets.

The user search term "show_actual_flag" maps directly to the column alias SHOW_ACTUAL_FLAG in this view. This alias reflects the view's semantics in the GL journal and batch entry flow, where the ACTUAL_FLAG determines whether a journal or batch is an actual (A) or a budget (B) entry. The view provides the descriptive counterpart to that flag.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over a single base object: GL_LOOKUPS, which is itself documented as a VIEW in the referenced object list. The view definition is:

SELECT l.lookup_code ACTUAL_FLAG,
       l.description SHOW_ACTUAL_FLAG
FROM gl_lookups l
WHERE l.lookup_type = 'BATCH_TYPE'

Because GL_LOOKUPS is the Oracle Applications synonym/view that resolves to the FND_LOOKUPS lookup table (filtered by application), the view is effectively a two-column projection of the GL batch type lookup values with no joins, aggregation, or outer query logic. This makes it inexpensive to query and safe for repeated reference in reports.

Key Columns

  • ACTUAL_FLAG — Sourced from GL_LOOKUPS.LOOKUP_CODE. Contains the stored batch type code. The documented batch type codes are typically A (Actual) and B (Budget). This value is what appears in journal and batch control columns such as ACTUAL_FLAG in GL_JE_BATCHES and GL_JE_HEADERS.
  • SHOW_ACTUAL_FLAG — Sourced from GL_LOOKUPS.DESCRIPTION. Provides the user-facing, translatable label corresponding to the code, such as "Actual" or "Budget". The name underscores its intended use: as the value to show when displaying an actual flag to a user.

Both columns derive directly from GL_LOOKUPS with no transformation, so referential integrity and multilingual behavior follow the standard Oracle Applications lookup framework.

Common Use Cases and Queries

Typical uses include resolving batch type codes into descriptions in custom reports, populating concurrent program parameters and value sets, and validating batch type codes in inbound interfaces.

-- List all available batch types
SELECT actual_flag, show_actual_flag
FROM   apps.gl_lookups_batch_type_v
ORDER BY actual_flag;
-- Resolve the description for a stored batch code
SELECT show_actual_flag
FROM   apps.gl_lookups_batch_type_v
WHERE  actual_flag = :p_actual_flag;
-- Join batch type descriptions to GL journal batches
SELECT b.name, b.actual_flag, v.show_actual_flag
FROM   gl_je_batches b,
       apps.gl_lookups_batch_type_v v
WHERE  v.actual_flag = b.actual_flag;

Because the view contains no date-effective or enabled-flag filtering of its own, consumers requiring only currently enabled lookup values should join to the underlying lookup table or apply the relevant enabled criteria. For most display and decoding purposes, however, the view as documented provides a complete and reliable mapping of GL batch type codes to their descriptions.