Search Results converted_batch_total_dr




Overview
Explore in AI Chat

Overview

The view GLBV_ACTUAL_JOURNAL_BATCHES is a General Ledger (GL) reporting object that exposes actual (non-budget) journal batches to which the current EBS user has security access. The "GLBV" prefix identifies it as a General Ledger Business View, a family of read-only views built for Oracle Business Intelligence Applications (OBIA) and other downstream reporting layers. It presents batch-level header information — status, periods, posting dates, control totals, and running debit/credit totals — for journals flagged as actual (ACTUAL_FLAG = 'A').

The view enforces Oracle EBS data security directly in its WHERE clause. Access to each batch is granted only when the user's active access set (resolved through GL_SECURITY_PKG.LOGIN_ACCESS_ID) covers the ledger of a journal header in that batch, or when full ledger-level ("F") privilege is held. Segment-level access is validated through GL_JE_SEGMENT_VALUES and GL_ACCESS_SET_ASSIGNMENTS. The view is declared WITH READ ONLY, so it is strictly a query object and cannot be used for DML.

The search term converted_batch_total_dr does not correspond to a column in this view. The documented columns carry the naming convention RUNNING_TOTAL_DR / RUNNING_TOTAL_CR and their accounted equivalents. A "converted" or entered-versus-accounted distinction in GL is typically handled at the journal line level rather than at this batch-level view, so users seeking a converted debit total should translate that requirement against RUNNING_TOTAL_ACCOUNTED_DR or query the underlying journal line tables directly.

Underlying Base Objects

Despite the metadata recording no separate base object list, the view text reveals its primary base object: GL_JE_BATCHES, aliased as ACTUAL_JOURNAL_BATCH. The security filter references several additional data objects:

  • GL_JE_HEADERS — provides the ledger context and the batch-to-header join.
  • GL_ACCESS_SETS and GL_ACCESS_SET_LEDGERS — define the ledgers and privilege level available to the logged-in user.
  • GL_JE_SEGMENT_VALUES and GL_ACCESS_SET_ASSIGNMENTS — drive fine-grained segment-value access checks.
  • GL_HR_EMPLOYEES_CURRENT_V — supplies the approver employee name.
  • FND_USER — supplies the posted-by user name.

Several columns are expressed as lookup-based value sets via the _LA: convention, meaning descriptive meanings (status, average journal flag, budgetary control status, approval status) are derived from GL lookup codes rather than stored literally on the batch record.

Key Columns

  • JE_BATCH_ID — Primary key of the journal batch; joins to GL_JE_BATCHES and GL_JE_HEADERS.
  • NAME — User-visible batch name.
  • STATUS — Lookup-translated batch status (e.g., Unposted, Posted).
  • DEFAULT_PERIOD_NAME — Accounting period default for the batch.
  • POSTED_DATE — Date the batch was posted.
  • CONTROL_TOTAL — Control (expected) total for the batch.
  • RUNNING_TOTAL_DR / RUNNING_TOTAL_CR — Entered debit and credit totals.
  • RUNNING_TOTAL_ACCOUNTED_DR / RUNNING_TOTAL_ACCOUNTED_CR — Accounted debit and credit totals, the closest analogue to a "converted" total.
  • APPROVER_EMPLOYEE_ID and the derived approver name — batch approval identity.
  • POSTED_BY and the derived FND_USER.USER_NAME — posting identity.

Common Use Cases and Queries

Typical use is batch-level reconciliation, posting audits, and feeds into OBIA extracts. Because row visibility is security-filtered, queries return only batches the session user may see.

  • List accessible actual batches with their totals:

SELECT JE_BATCH_ID, NAME, STATUS, DEFAULT_PERIOD_NAME, POSTED_DATE, RUNNING_TOTAL_DR, RUNNING_TOTAL_CR FROM GLBV_ACTUAL_JOURNAL_BATCHES;

  • Find posted batches for a period:

SELECT NAME, POSTED_DATE, RUNNING_TOTAL_ACCOUNTED_DR FROM GLBV_ACTUAL_JOURNAL_BATCHES WHERE POSTED_DATE IS NOT NULL AND DEFAULT_PERIOD_NAME = 'JAN-22';

  • Verify debit/credit balance on a batch:

SELECT JE_BATCH_ID, RUNNING_TOTAL_DR, RUNNING_TOTAL_CR, RUNNING_TOTAL_DR - RUNNING_TOTAL_CR DIFFERENCE FROM GLBV_ACTUAL_JOURNAL_BATCHES WHERE JE_BATCH_ID = :batch_id;

Analysts looking for a distinct "converted batch total debit" figure should confirm whether the requirement maps to RUNNING_TOTAL_ACCOUNTED_DR or to line-level converted amounts, since the view exposes no column with that exact name.