Search Results actual_journal_batch1

Overview

GLFV_ACTUAL_JOURNAL_BATCHES is an Oracle E-Business Suite General Ledger view owned by the APPS schema. In the ETRM metadata it is listed with a status of VALID and is associated with the GL – General Ledger product. The view presents actual journal batches, which are defined in the metadata as groups of journal entries that represent the results of financial operations. Functionally, the view exposes batch-level attributes of journal batches — such as batch name, period, control totals, approval and budgetary control status, and posting information — together with derived, display-oriented columns that resolve lookup codes into descriptive text.

The view is built on a security-filtered query, meaning it does not simply surface all rows of the underlying batch table. Its definition embeds an EXISTS subquery that restricts access according to the logged-in user's GL access set and access privileges (GL_SECURITY_PKG.LOGIN_ACCESS_ID). This makes the view suitable for reporting where data security must be enforced consistently with the application's own access rules.

Underlying Base Objects

The metadata states that no base objects are documented for this view, but the view text clearly identifies GL_JE_BATCHES as its primary source, aliased as ACTUAL_JOURNAL_BATCH1. The view also references several supporting objects used for access control and value resolution, including GL_JE_HEADERS, GL_ACCESS_SETS, GL_ACCESS_SET_LEDGERS, GL_JE_SEGMENT_VALUES, and GL_ACCESS_SET_ASSIGNMENTS within the security predicate. Additional scalar subqueries reference GL_HR_EMPLOYEES_CURRENT_V and FND_USER to translate approver and poster identifiers into names. Lookup-based columns are resolved through GL_LOOKUPS, and the view is flagged in its definition with the descriptor _DF:SQLGL:GL_JE_BATCHES.

Key Columns

Because the user search included "posted_by", the most relevant columns are POSTED_BY and POSTED_DATE. POSTED_BY holds the USER_ID of the individual who posted the batch, and the view supplies a companion column resolved from FND_USER.USER_NAME for a readable user name. POSTED_DATE records when posting occurred. Other prominent columns include JE_BATCH_ID, NAME, DEFAULT_PERIOD_NAME, DATE_CREATED, and DESCRIPTION. Financial aggregates are exposed through CONTROL_TOTAL, RUNNING_TOTAL_DR, RUNNING_TOTAL_CR, RUNNING_TOTAL_ACCOUNTED_DR, and RUNNING_TOTAL_ACCOUNTED_CR. Status-related attributes include batch status, AVERAGE_JOURNAL_FLAG, BUDGETARY_CONTROL_STATUS, and APPROVAL_STATUS_CODE, the last three being rendered as lookup descriptions. Approver identity is exposed via APPROVER_EMPLOYEE_ID and a derived employee name.

Common Use Cases and Queries

Typical scenarios include locating all batches posted by a specific user, auditing posting activity, or reviewing batch control totals against running debit and credit totals. The following query filters by poster:

• SELECT je_batch_id, name, default_period_name, posted_date, posted_by FROM apps.glfv_actual_journal_batches WHERE posted_by = :user_id;
• SELECT name, posted_date, control_total, running_total_dr, running_total_cr FROM apps.glfv_actual_journal_batches WHERE default_period_name = :period;
• SELECT name, budgetary_control_status, approval_status_code FROM apps.glfv_actual_journal_batches WHERE name LIKE :pattern;

Because the view already enforces access-set security, queries against it automatically return only batches the current user is authorized to see.