Results for “gl_je_headers_lov_v”

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

Overview

GL_JE_HEADERS_LOV_V is a General Ledger view shipped within the Oracle E-Business Suite that presents journal entry header information formatted for use by a List of Values (LOV). The view joins the GL_JE_HEADERS table to the GL_JE_BATCHES table so that consumers can retrieve journal header attributes alongside the name of the batch to which each header belongs. Because an LOV typically requires a compact set of descriptive columns suitable for user selection, this view restricts its projection to the header identifier, its parent batch identifier, the set of books, the header name and description, the batch name, the actual flag, and the period name.

The ETRM metadata for this object carries the description "10SC ONLY," indicating that the view is documented as relevant only to a specific localization or country-specific configuration rather than as a generic global component. The metadata further states "Not implemented in this database," meaning that in the reference environment from which the documentation was harvested, the view does not physically exist. This is an important distinction: the view text is documented, but the object itself may not be present in a given instance. The column list confirms the intended shape of the data returned by the SELECT statement catalogued in the documentation.

Underlying Base Objects

Although the documented metadata lists no referenced base objects explicitly, the view text unambiguously defines the view over two foundation tables in Oracle General Ledger: GL_JE_HEADERS, aliased as H, and GL_JE_BATCHES, aliased as B. The join condition, B.JE_BATCH_ID = H.JE_BATCH_ID + 0, links each journal header to its owning batch. The addition of zero to H.JE_BATCH_ID is a common Oracle EBS construct that forces numeric comparison semantics and can prevent index-driven plan behaviour that would otherwise be undesirable in an LOV context.

GL_JE_HEADERS stores the individual journal entry headers, including the header identifier, batch identifier, set of books, name, description, posting status, period, and the actual flag that distinguishes actual from budget journals. GL_JE_BATCHES stores the batch-level grouping of journal entries, including the batch identifier and the batch name surfaced by this view as BATCH_NAME. The view therefore represents a denormalised, read-only projection across the header-to-batch relationship.

Key Columns

• JE_HEADER_ID — The unique identifier of the journal entry header; the primary key value from GL_JE_HEADERS.
• JE_BATCH_ID — The identifier of the batch to which the header belongs, exposed from the header record; this is the column most directly relevant to the search term "je_batch_id."
• SET_OF_BOOKS_ID — The ledger or set of books context for the journal entry.
• NAME — The journal entry header name, used as the primary descriptive element in the LOV.
• DESCRIPTION — The free-text description attached to the journal header.
• BATCH_NAME — The name of the parent batch, sourced from GL_JE_BATCHES.
• ACTUAL_FLAG — Indicates whether the journal is an actual, budget, or encumbrance entry.
• PERIOD_NAME — The accounting period in which the journal falls.

Common Use Cases and Queries

The principal use case is populating a journal entry header list of values, particularly where the calling context already knows the batch. A typical query filters by batch identifier:

• SELECT je_header_id, je_batch_id, name, batch_name, period_name FROM gl_je_headers_lov_v WHERE je_batch_id = :batch_id;

Additional scenarios include retrieving all headers within a set of books for a given period, or joining the view back to GL_JE_LINES for drill-down reporting. Because the documented metadata states the view is not implemented in the reference database and is scoped as "10SC ONLY," implementers should verify its existence in the target instance before relying on it, and should treat the two base tables named in the view text as the authoritative source for the join logic.