Search Results gl_batch_name

Overview

GL_JE_BATCHES_AP_V is a Payables-module database view that exposes journal entry batch information relevant to the subledger accounting relationship between Oracle Payables (AP) and Oracle General Ledger (GL). Its documented purpose is limited to Release 10SC of the E-Business Suite; the ETRM metadata explicitly notes that the view is "Not implemented in this database," meaning that in Oracle EBS 12.1.1 and 12.2.2 environments it may not exist as a deployed database object. It is nonetheless a frequently referenced object in legacy SQL scripts, custom reports, and migration utilities that were authored against the earlier 10SC schema.

The view's role is to associate each GL journal batch with the accounting method that governs it, based on the relationship between the batch's set of books and the Payables system parameters. This enables reporting on which accounting convention—cash or accrual—a batch reflects, without requiring the caller to re-derive that logic. The user search term "gl_batch_name" maps directly to the GL_BATCH_NAME column, which is the batch's user-facing name and the most common filter or display value requested by end users.

Underlying Base Objects

The view text is defined over three base tables:

• GL_JE_BATCHES (GLB) — the GL journal batch header table, providing JE_BATCH_ID, NAME, SET_OF_BOOKS_ID, and ACTUAL_FLAG.
• GL_JE_HEADERS (GLH) — the journal entry header table, joined on JE_BATCH_ID and used to obtain JE_CATEGORY.
• AP_SYSTEM_PARAMETERS (SP) — the Payables system parameters, supplying SET_OF_BOOKS_ID, SECONDARY_SET_OF_BOOKS_ID, ACCOUNTING_METHOD_OPTION, and SECONDARY_ACCOUNTING_METHOD.

Although the ETRM metadata for 12.2.2 records no documented referenced base objects, the embedded view text unambiguously identifies these three tables. The join is driven by a DECODE expression that resolves the correct set of books for the batch, first testing the secondary accounting method against the JE_CATEGORY-mapped value (PAYMENTS maps to CASH, PURCHASE INVOICES maps to ACCRUAL, and DUMMY is treated as a special case), then testing the primary accounting method option. The ACTUAL_FLAG = 'A' predicate restricts the result set to actual (posted or unposted) journal batches, excluding budgets and encumbrances.

Key Columns

• JE_BATCH_ID — the unique identifier of the GL journal batch; serves as the join key to GL_JE_BATCHES and GL_JE_HEADERS.
• GL_BATCH_NAME — the batch name (GLB.NAME), the primary descriptive attribute and the column most often referenced in ad hoc queries and listings.
• ACCOUNTING_METHOD — a derived value returning either the Payables accounting method option or the secondary accounting method, depending on whether the batch's set of books matches the primary SET_OF_BOOKS_ID. This indicates whether the batch is associated with the primary or secondary accounting method configuration.

Common Use Cases and Queries

The principal use case is resolving a batch name or batch ID to its associated accounting method and set of books context, typically during reconciliation between Payables and GL, or when auditing which batches were created under cash versus accrual accounting.

A representative query listing batches by name and accounting method:

• SELECT JE_BATCH_ID, GL_BATCH_NAME, ACCOUNTING_METHOD FROM GL_JE_BATCHES_AP_V WHERE GL_BATCH_NAME LIKE 'PAY%';
• SELECT GL_BATCH_NAME FROM GL_JE_BATCHES_AP_V ORDER BY GL_BATCH_NAME;
• SELECT ACCOUNTING_METHOD, COUNT(*) FROM GL_JE_BATCHES_AP_V GROUP BY ACCOUNTING_METHOD;

Because the object is documented as unimplemented in current releases, developers targeting 12.1.1 or 12.2.2 should verify its existence in the data dictionary and, where absent, reconstruct equivalent logic directly against GL_JE_BATCHES, GL_JE_HEADERS, and AP_SYSTEM_PARAMETERS, or use the corresponding modern subledger accounting views.