Search Results mje_batch_status




Overview
Explore in AI Chat

Overview

APPS.GL_LOOKUPS_MJE_BATCH_STATUS_V is a lightweight reporting view in the Oracle E-Business Suite General Ledger module. It exposes the set of valid lookup values defined for the lookup type MJE_BATCH_STATUS, which governs the status codes assignable to a Multi-Journal Entry (MJE) batch. Rather than querying the underlying GL_LOOKUPS table directly, consumers can select from this view to obtain a clean, purpose-built list of batch status codes and their user-facing descriptions.

The view is owned by the APPS schema and is available across Oracle EBS 12.1.1 and 12.2.2. It plays a supporting role in reporting, integration, and validation logic where the status of an MJE batch must be interpreted or restricted. Because it presents lookup metadata rather than transactional data, it is typically joined to detail tables that store an MJE batch status code, allowing reports to render the human-readable description in place of the internal code.

Underlying Base Objects

The view is defined over a single referenced base object: GL_LOOKUPS, itself exposed as a view in the APPS schema. The definition filters GL_LOOKUPS on lookup_type = 'MJE_BATCH_STATUS', so only the rows belonging to the MJE batch status lookup type are returned. This filtering isolates the relevant lookup set and shields callers from having to know or hard-code the lookup type in every query.

Because the view reads from GL_LOOKUPS, it inherits the standard Oracle lookups model. Lookup types are maintained through the application's lookup maintenance functions, and each lookup code carries a description and related attributes such as enabled flag, start and end dates, and tag fields. The view abstracts this structure into two derived columns, as documented in the ETRM metadata.

Key Columns

The documented view definition exposes exactly two columns, both derived by aliasing columns from GL_LOOKUPS:

  • BATCH_STATUS — aliased from l.lookup_code. This is the internal lookup code representing an MJE batch status value. It is the value stored on MJE batch records and compared in application and integration logic.
  • SHOW_BATCH_STATUS — aliased from l.description. This is the display-friendly description associated with the lookup code, suitable for presentation in reports, concurrent program output, and user interfaces.

No additional columns are projected by the documented view text, so attributes such as enabled flag or date ranges are not exposed here and must be obtained from GL_LOOKUPS if required.

Common Use Cases and Queries

The most frequent use is providing a lookup list for batch status selection or validation, and joining to MJE batch data to translate a stored status code into its description. A typical query retrieves all defined statuses:

  • SELECT batch_status, show_batch_status FROM apps.gl_lookups_mje_batch_status_v ORDER BY batch_status; — returns every defined MJE batch status code and its description.
  • SELECT v.batch_status, v.show_batch_status FROM apps.gl_lookups_mje_batch_status_v v WHERE v.batch_status = :p_status; — validates or describes a single status value.
  • Joining to an MJE batch detail source on the status code allows reports to display descriptions alongside transaction-level detail.

Because the view is read-only and references only lookup metadata, it is safe for reporting, parameter list-of-values definitions, and integration lookups. Where the complete set of lookup attributes is needed, query GL_LOOKUPS directly with the MJE_BATCH_STATUS lookup type.