Search Results batch_context2

Overview

The APPS.IGI_GL_JE_JOURNAL_LINES_V view is a denormalized reporting object delivered with the IGI – Public Sector Financials International product. It presents a consolidated, read-only projection of Oracle General Ledger journal activity, joining batch, header, line, period and reference lookup information into a single queryable structure. The view exists primarily to support federal and public-sector reporting requirements, where journal entries must be presented with descriptive context — such as batch status meaning, budgetary control status, encumbrance type, journal source and category — rather than raw coded identifiers. Because the view is owned by APPS and defined over standard GL tables, it is reachable from any custom concurrent program, BI Publisher data template, OAF page or third-party extract that has been granted SELECT on the APPS schema objects. The view is documented as VALID in ETRM for release 12.2.2 and is equally present in 12.1.1, where its column signature and underlying join logic are unchanged.

Underlying Base Objects

The documented definition draws on eleven base objects: GL_JE_SOURCES_TL, GL_JE_CATEGORIES_TL, GL_ENCUMBRANCE_TYPES, GL_BUDGET_VERSIONS, GL_LOOKUPS, GL_DAILY_CONVERSION_TYPES, GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES and GL_PERIOD_STATUSES. The transactional core is the trio GL_JE_BATCHES (aliased B), GL_JE_HEADERS (H) and GL_JE_LINES (L). The batch-level columns dominate the visible SELECT text, confirming that the view is anchored on GL_JE_BATCHES and left-joined outward to headers and lines. Translation tables GL_JE_SOURCES_TL and GL_JE_CATEGORIES_TL supply user-facing source and category names, while GL_LOOKUPS provides the DECODE-style meaning for batch status (SHOW_BATCH_STATUS) and budgetary control status (SHOW_BC_STATUS). GL_PERIOD_STATUSES contributes PERIOD_YEAR and PERIOD_NUM so that entries can be aligned to fiscal reporting calendars. The ETRM metadata also lists DUAL as a referenced synonym, a common artifact of the Resolve view compilation process rather than a functional dependency.

Key Columns

• BATCH_ROW_ID / JE_BATCH_ID – the batch ROWID and primary key, used to drill back to GL_JE_BATCHES.
• SET_OF_BOOKS_ID – ledger identifier; critical for multi-ledger environments.
• PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM – accounting period and its fiscal position.
• ACTUAL_FLAG – distinguishes actual, budget and encumbrance balances.
• BATCH_STATUS / SHOW_BATCH_STATUS – the coded status and its decoded description.
• BUDGETARY_CONTROL_STATUS / SHOW_BC_STATUS – budgetary control outcome for the batch.
• BATCH_CONTROL_TOTAL, BATCH_RUNNING_TOTAL_DR, BATCH_RUNNING_TOTAL_CR – batch totals used for balance verification; these are the columns most closely associated with the balanced_je_flag concept, since a batch is balanced when debits equal credits and CONTROL_TOTAL equals zero.
• BATCH_STATUS_VERIFIED, BATCH_EFFECTIVE_DATE, BATCH_USSGL_TRANSACTION_CODE – posting and USSGL attributes required for federal reporting.
• ATTRIBUTE1 … ATTRIBUTE10, BATCH_CONTEXT, BATCH_CONTEXT2 – descriptive flexfield segments.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) – standard WHO tracking.

Common Use Cases and Queries

The view is typically queried to reconcile journal batches, identify unbalanced or unposted entries, and feed federal USSGL extracts. A representative query filters on the decoded status and compares running totals to detect imbalance:

SELECT je_batch_id, batch_name, period_name, show_batch_status, batch_control_total, batch_running_total_dr, batch_running_total_cr FROM apps.igi_gl_je_journal_lines_v WHERE set_of_books_id = :p_sob AND period_name = :p_period AND batch_running_total_dr <> batch_running_total_cr;

For budgetary reporting, users constrain ACTUAL_FLAG to 'B' and group by SHOW_BC_STATUS to summarize control outcomes. For USSGL submissions, BATCH_USSGL_TRANSACTION_CODE is selected alongside period and ledger identifiers. Because the view exposes batch, header and line attributes together, it removes the need for callers to re-implement the joins to GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES, GL_JE_SOURCES_TL and GL_LOOKUPS, ensuring consistent interpretation of statuses and periods across all public-sector reporting outputs. The balanced_je_flag search term maps naturally to the CONTROL_TOTAL and RUNNING_TOTAL_DR/CR columns, which are the definitive indicators of batch balance within this view.