Results for “glfv_journal_batches”

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

Overview

GLFV_JOURNAL_BATCHES is a General Ledger (GL) view owned by the APPS schema in Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. It presents General Ledger journal batches, which are groups of related journal entries sharing the same GL period. The view is a translated ("_LA" and "_DF") reporting view generated by the Oracle Application Object Library (AOL) standards, exposing denormalized lookup descriptions and descriptive flexfield references alongside the core batch attributes. Because journal batches act as the container for journal headers and lines, this view is fundamental to subledger-to-GL reconciliation, period-close monitoring, and audit reporting. A distinguishing feature is its integration with the GL Access Set security model: the view embeds the login user's access privileges directly in its WHERE clause via GL_SECURITY_PKG.LOGIN_ACCESS_ID, so a query executed by an unauthorized user returns only batches for ledgers to which that user has access. This makes the view suitable for responsibility-based reporting without additional row-level security logic in the report itself.

Underlying Base Objects

The view text is defined primarily over GL_JE_BATCHES, aliased as JOURNAL_BATCH1. The WHERE clause joins to GL_JE_HEADERS, GL_ACCESS_SETS, GL_ACCESS_SET_LEDGERS, and, for finer security, GL_JE_SEGMENT_VALUES and GL_ACCESS_SET_ASSIGNMENTS. Two scalar subqueries reference GL_HR_EMPLOYEES_CURRENT_V (for the approver name) and FND_USER (for the posted-by user name). The ETRM metadata documents no referenced base objects explicitly, but the embedded view definition confirms GL_JE_BATCHES as the driving table. All access paths are filtered by the security EXISTS clause, and the view is defined with a "DF:SQLGL:GL_JE_BATCHES" descriptive flexfield marker, meaning it participates in GL batch DFF reporting.

Key Columns

The view selects JE_BATCH_ID and NAME for batch identification, DEFAULT_PERIOD_NAME, POSTED_DATE, DATE_CREATED, and DESCRIPTION. Status columns are translated through GL_LOOKUPS: STATUS (BATCH_STATUS), ACTUAL_FLAG (BATCH_TYPE), AVERAGE_JOURNAL_FLAG (AB_JOURNAL_TYPE MEANING), BUDGETARY_CONTROL_STATUS (JE_BATCH_BC_STATUS), and APPROVAL_STATUS_CODE (JE_BATCH_APPROVAL_STATUS). Two positions are returned as TO_NUMBER(NULL) with literal 'OBSOLETE', reflecting deprecated columns retained for column-position stability. Control and running balances are exposed as CONTROL_TOTAL, RUNNING_TOTAL_DR, RUNNING_TOTAL_CR, RUNNING_TOTAL_ACCOUNTED_DR, and RUNNING_TOTAL_ACCOUNTED_CR. Of particular relevance to the search term "approver_employee_id", the view exposes APPROVER_EMPLOYEE_ID together with a correlated subquery that resolves the employee name from GL_HR_EMPLOYEES_CURRENT_V. POSTED_BY and a corresponding FND_USER user-name subquery are also exposed.

Common Use Cases and Queries

Typical uses include identifying batches awaiting approval, reconciling control totals, and reporting who approved or posted a batch. Because APPROVER_EMPLOYEE_ID is a foreign key to the HR employee, reporting tools can display the resolved approver name without a separate join. Example:

• SELECT je_batch_id, name, default_period_name, approval_status_code, approver_employee_id FROM glfv_journal_batches WHERE approved_flag = 'Y'; — lists approved batches and their approver employees.

• SELECT name, control_total, running_total_accounted_dr, running_total_accounted_cred FROM glfv_journal_batches WHERE default_period_name = :period_name; — reviews batch control versus accounted totals during period close.

• SELECT b.name, b.posted_by, u.user_name FROM glfv_journal_batches b WHERE b.approval_status_code = 'PENDING'; — monitors pending approvals with the posting user.

Queries must respect the embedded access-set security; a user with restricted ledger access will not see batches outside assigned access sets. For best performance, filter on JE_BATCH_ID, NAME, or DEFAULT_PERIOD_NAME, and be mindful that the correlated subqueries to GL_HR_EMPLOYEES_CURRENT_V execute per returned row.