Search Results show_batch_status




Overview
Explore in AI Chat

Overview

GL_LOOKUPS_MJE_BATCH_STATUS_V is a database view owned by the APPS schema in Oracle E-Business Suite, defined within the General Ledger (GL) product family. Its documented description is "10SC ONLY," indicating that the object is restricted to a specific localization or statutory configuration rather than being part of the standard, globally deployed GL schema. The view presents a filtered, presentation-oriented projection of the MJE_BATCH_STATUS lookup values, exposing the lookup code and its descriptive text under friendly column aliases. Its functional role is to decouple reporting and integration logic from the underlying generic lookup infrastructure: rather than requiring every consumer to hard-code the LOOKUP_TYPE predicate MJE_BATCH_STATUS, the view encapsulates that filter and exposes a narrow, purpose-built result set.

Because the object is a view rather than a table, it stores no data of its own. It provides a read-only, always-current window onto the GL_LOOKUPS lookup repository, ensuring that any additions or description changes made to the MJE_BATCH_STATUS lookup type are immediately reflected to downstream consumers.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view references a single base object: GL_LOOKUPS (itself a view in the APPS schema). GL_LOOKUPS is the standard General Ledger lookup repository that stores all lookup types and their associated codes, meanings, and descriptions used throughout the GL module. The view text is:

The relationship is therefore a simple one-to-many filter: every row in GL_LOOKUPS whose LOOKUP_TYPE equals MJE_BATCH_STATUS becomes one row in this view. No joins, aggregations, or outer references are present, so the view cannot multiply or lose data relative to its filtered base set. MJE typically denotes Multi-Jurisdiction Entries or Manual Journal Entry processing context; the lookup type governs the permitted status codes for journal batch processing in the affected localization.

Key Columns

  • BATCH_STATUS — Sourced from GL_LOOKUPS.LOOKUP_CODE. This is the stored, internal code value used to identify a batch state. It is the value typically persisted on transactional tables and used in WHERE predicates and programmatic comparisons.
  • SHOW_BATCH_STATUS — Sourced from GL_LOOKUPS.DESCRIPTION. This is the user-facing or display text associated with the status code. The column name directly answers the "show_batch_status" search intent: it is the value intended for presentation in reports, LOVs, and screens.

No other columns are exposed. The view deliberately omits the lookup type, enabled flag, start/end dates, and tag columns that exist on GL_LOOKUPS, presenting only the code and its display description.

Common Use Cases and Queries

The primary use case is populating batch status values in reports, concurrent program outputs, and integration payloads where only the code and its display text are required. It is also suitable for driving value sets or LOV definitions that must show meaningful status descriptions alongside stored codes.

To list all valid batch statuses with their display text:

  • SELECT batch_status, show_batch_status FROM apps.gl_lookups_mje_batch_status_v ORDER BY batch_status;

To resolve a single stored status code to its display value:

  • SELECT show_batch_status FROM apps.gl_lookups_mje_batch_status_v WHERE batch_status = :p_status;

To join batch status descriptions onto journal batch data, the view is typically outer-joined to the batch table on the persisted status code, substituting SHOW_BATCH_STATUS in the SELECT list. Because the view filters only on MJE_BATCH_STATUS, it should not be used as a general-purpose lookup source. Consumers should also confirm whether the "10SC ONLY" restriction applies to their environment, since availability may be limited to specific localizations in 12.1.1 and 12.2.2.