Search Results batch_effective_date

Overview

IGC_CBC_JE_LINES_V is an APPS-owned reporting view within the IGC – Contract Commitment module of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. It presents journal entry lines that have been generated by the Contract Commitment (CBC) funds-checking and commitment accounting processes, enriched with batch-level header attributes and decoded lookup values. Its principal purpose is to expose the debit and credit detail of commitment journal entries alongside descriptive context that is not available from the line table alone, such as the batch name, batch description, and the batch effective date.

The view is read-only by design and is intended for inquiry, reporting, and data extraction rather than transactional processing. Because the funds-check and commitment journal records are normally aggregated in the base tables, this view offers a convenient denormalized surface for reconciliation and audit reports, and for feeding external ledgers or data warehouses.

Underlying Base Objects

The view is defined over four documented base objects:

• IGC_CBC_JE_LINES (SYNONYM) — the primary source, providing every journal line and the aliased JEL prefix.
• IGC_CBC_JE_BATCHES (SYNONYM) — the header source, aliased JEB, supplying batch name, effective date, description, and running totals.
• GL_ENCUMBRANCE_TYPES (SYNONYM) — aliased ET, resolving the encumbrance type identifier to its descriptive name.
• GL_LOOKUPS (VIEW) — aliased L, used to translate lookup codes such as ACTUAL_FLAG into readable descriptions (exposed as SHOW_ACTUAL_FLAG).

The lines are joined to their batch header on CBC_JE_BATCH_ID, preserving the line grain while appending header context to each row.

Key Columns

The column list mirrors the base tables. The user search term batch_effective_date maps directly to BATCH_EFFECTIVE_DATE, which is sourced from JEB.EFFECTIVE_DATE and is distinct from the line-level EFFECTIVE_DATE. BATCH_EFFECTIVE_DATE indicates when the commitment journal batch as a whole took effect in General Ledger.

Other significant columns include:

• Identification — CBC_JE_BATCH_ID, CBC_JE_LINE_NUM, and ROW_ID (from JEL.ROWID).
• Batch context — BATCH_NAME, BATCH_DESCRIPTION, RUNNING_TOTAL_DR, RUNNING_TOTAL_CR.
• Accounting attributes — JE_SOURCE, JE_CATEGORY, ACCOUNTING currency_code, ACTUAL_FLAG and SHOW_ACTUAL_FLAG, SET_OF_BOOKS_ID, CODE_COMBINATION_ID, ENCUMBRANCE_TYPE, BUDGET_VERSION_ID, BUDGET_TYPE, FUNDS_CHECK_LEVEL_CODE, AMOUNT_TYPE, DETAIL_SUMMARY_CODE.
• Amounts and period — ENTERED_DR, ENTERED_CR, DR_CR_CODE, PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM, QUARTER_NUM, POSTED_DATE.
• Descriptive and audit — DESCRIPTION, REFERENCE_1 through REFERENCE_10, ATTRIBUTE1 onward, plus the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

The view supports commitment-journal reconciliation, funds-check reporting, batch-level audit of effective dates, and encumbrance analysis. A typical query filtering on the searched attribute is:

• SELECT cbc_je_batch_id, cbc_je_line_num, batch_name, batch_effective_date, entered_dr, entered_credits, period_name
• FROM igc_cbc_je_lines_v
• WHERE batch_effective_date BETWEEN :start_date AND :end_date
• ORDER BY cbc_je_batch_id, cbc_je_line_num;

To reconcile running batch totals to line detail:

• SELECT cbc_je_batch_id, SUM(entered_dr), SUM(entered_cr), MAX(running_total_dr), MAX(running_total_cr)
• FROM igc_cbc_je_lines_v GROUP BY cbc_je_batch_id;

Because the row identifier and all base keys are exposed, the view integrates cleanly into reports requiring drill-down from batch header to individual journal line.