Search Results running_total_accounted_dr




Overview
Explore in AI Chat

Overview

GL_JE_BATCHES_V is a General Ledger view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a user-friendly, denormalized projection of journal entry batches held in the GL_JE_BATCHES base table. Rather than returning raw foreign keys alone, the view joins to GL_PERIODS, GL_LOOKUPS, and FND_USER to resolve period dates, lookup descriptions, and the posted-by user name. This makes it a convenient source for reporting, concurrent program logic, and integration extracts that need batch-level detail without writing the lookup and period joins manually.

The view carries a significant portion of the batch record, including control totals, running totals, status, approval state, and descriptive flexfield columns (ATTRIBUTE1 through ATTRIBUTE10, CONTEXT, CONTEXT2). Its lifecycle fields — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — are also exposed. The user search term "running_total_accounted_dr" maps directly to the RUNNING_TOTAL_ACCOUNTED_DR column, which is one of the running-total columns surfaced by this view and which is typically populated during journal import and posting activity.

Underlying Base Objects

Per documented metadata, the view is defined over four referenced objects: GL_JE_BATCHES (synonym to the base table), GL_PERIODS (synonym), GL_LOOKUPS (view), and FND_USER (synonym). The primary driving table is GL_JE_BATCHES, aliased as B in the view text. GL_PERIODS supplies START_DATE, END_DATE, PERIOD_YEAR, and PERIOD_NUM for the batch's default period name and period set. GL_LOOKUPS is referenced twice — resolved as L for the batch STATUS display description (SHOW_STATUS) and as L2 for the budgetary control status display meaning (SHOW_BC_STATUS) — with L3 supplying SHOW_ACTUAL_FLAG. FND_USER is used in a scalar subquery to translate POSTED_BY into POSTED_BY_NAME. Because the view is a read-only projection, it inherits the security and concurrency behavior of its underlying objects.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciliation of entered versus accounted totals, monitoring batches for a given period, and auditing posting activity. A representative query for the searched column follows:

  • SELECT je_batch_id, name, default_period_name, running_total_dr, running_total_cr, running_total_accounted_dr, running_total_accounted_cr FROM gl_je_batches_v WHERE default_period_name = :period AND status = 'U';
  • SELECT je_batch_id, name, show_status, posted_date, posted_by_name FROM gl_je_batches_v WHERE posted_date IS NOT NULL;
  • SELECT default_period_name, SUM(running_total_accounted_dr) accounted_dr, SUM(running_total_accounted_cr) accounted_cr FROM gl_je_batches_v GROUP BY default_period_name;

Because the view does not restrict by ledger or organization beyond the ORG_ID column it exposes, callers should apply appropriate ORG_ID and period predicates to bound results.