Results for “journal_batch1”

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

Overview

APPS.GLFV_JOURNAL_BATCHES is a security-enabled (read-only) view in the Oracle E-Business Suite General Ledger schema. It presents journal batch header information from GL_JE_BATCHES together with translated lookup meanings and denormalized employee and user names. The view is defined with the WITH READ ONLY clause, so it is intended strictly for reporting and integration consumption rather than for transactional updates. Its principal role is to expose journal batch data to Oracle EBS reporting tools, Oracle Discoverer workbooks, BI Publisher reports, and outward-facing integrations while preserving the data-access-set security model that governs General Ledger.

Row-level filtering is enforced inside the view through a correlated EXISTS clause that joins GL_JE_HEADERS, GL_ACCESS_SETS, and GL_ACCESS_SET_LEDGERS, resolving the caller's security context through GL_SECURITY_PKG.login_access_id. Access is granted either when the access set's security segment code is 'F' (full ledger access), when the ledger access privilege is 'F', or when a matching balancing/management segment value exists in GL_JE_SEGMENT_VALUES for an assigned segment in GL_ACCESS_SET_ASSIGNMENTS. Consequently, two users running the same query may see different result sets depending on their assigned access sets.

Underlying Base Objects

The ETRM metadata documents no referenced base objects, but the view text itself makes the dependency explicit. The primary source is GL_JE_BATCHES, aliased JOURNAL_BATCH1, which supplies the batch identifier, name, status, control totals, posting information, and approval columns. The security predicate introduces additional dependencies: GL_JE_HEADERS (linking batches to ledgers), GL_ACCESS_SETS and GL_ACCESS_SET_LEDGERS (security context), and, for segment-level restriction, GL_JE_SEGMENT_VALUES and GL_ACCESS_SET_ASSIGNMENTS.

Two scalar subqueries enrich the projection: GL_HR_EMPLOYEES_CURRENT_V supplies the approver's employee name, and FND_USER supplies the user name of the posting user. Lookup descriptions and meanings are not stored in the base tables; they are resolved dynamically through the Flexfield/Lookup API reference notation '_LA:' encoded in the SELECT list, which directs the EBS framework to translate codes such as BATCH_STATUS, BATCH_TYPE, AB_JOURNAL_TYPE, JE_BATCH_BC_STATUS, and JE_BATCH_APPROVAL_STATUS against GL_LOOKUPS. The notation '_DF:SQLGL:GL_JE_BATCHES:JOURNAL_BATCH1' similarly tags the view as a SQLGL-registered data source for the underlying batch entity.

Key Columns

• JE_BATCH_ID — Primary key of the journal batch; joins to GL_JE_HEADERS and GL_JE_LINES.
• NAME — User-entered batch name as recorded on GL_JE_BATCHES.
• Status-derived column — Translated from JOURNAL_BATCH1.STATUS via GL_LOOKUPS (BATCH_STATUS:DESCRIPTION).
• Actual flag-derived column — Derived from ACTUAL_FLAG via BATCH_TYPE:DESCRIPTION, distinguishing actual, budget, and encumbrance batches.
• DEFAULT_PERIOD_NAME — Default accounting period for the batch.
• POSTED_DATE, DATE_CREATED, DESCRIPTION — Posting timestamp, creation timestamp, and free-text batch description.
• AVERAGE_JOURNAL_FLAG-derived column — Translated mean value for the AB_JOURNAL_TYPE lookup.
• BUDGETARY_CONTROL_STATUS and APPROVAL_STATUS_CODE-derived columns — Translated meanings for budgetary control and journal approval state.
• CONTROL_TOTAL and RUNNING_TOTAL_DR / CR / ACCOUNTED_DR / ACCOUNTED_CR — Batch control amount and running debit/credit totals in entered and accounted currency.
• APPROVER_EMPLOYEE_ID and approver name — Approver identifier and resolved employee name from GL_HR_EMPLOYEES_CURRENT_V.
• POSTED_BY and poster user name — Posting user identifier and FND_USER user name.
• Two placeholder columns — TO_NUMBER(NULL) paired with the literal 'Obsolete', retained for backward compatibility.

Common Use Cases and Queries

Typical uses include journal batch status reporting, approval and posting audits, control-total reconciliation, and feeds into external financial systems. The following query lists unposted or pending batches visible to the current user:

SELECT je_batch_id, name, default_period_name, control_total, running_total_dr, running_total_cr FROM apps.glfv_journal_batches WHERE default_period_name = :period ORDER BY date_created DESC;

For approval aging, filter on the translated approval status column and the approver name. Because the view is read-only and secured, it is safe to expose to downstream reports; nevertheless, joins back to GL_JE_BATCHES on JE_BATCH_ID are common when additional non-exposed attributes are required.