Results for “be_line_num”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IGI.IGI_BUD_JOURNAL_LINES table is a core transactional data object within the IGI - Public Sector Financials International module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the individual line-level detail for budget journals entered or interfaced through the IGI budgetary control and budget execution functionality. Each row represents a single distribution line belonging to a budget journal header, capturing the accounting flexfield, monetary amounts, and control attributes that drive budget checking, funds reservation, and budget-to-actual reporting for public sector organizations.

From a dimensional modeling perspective, the provided metadata classifies this object heuristically as standalone based on its foreign key structure. In Data Vault terms this suggests the table may be modeled as a link object, since it associates a budget journal header, a batch, and a code combination, holding measures (debit and credit amounts) on the relationship. The classification is a modeling suggestion only; the authoritative schema remains the documented physical structure.

Key Information Stored

The table contains 20 documented columns. The most significant are:

The documented unique index IGI_BUD_JOURNAL_LINES_PK (BE_HEADER_ID, BE_LINE_NUM) confirms the composite business key that uniquely identifies each line relative to its header.

Common Use Cases and Queries

Typical scenarios include extracting budget journal lines for a given header, reconciling batch activity, and reporting budget movement by accounting flexfield. A representative query joining line detail to the parent batch is:

SELECT l.be_header_id, l.be_line_num, l.code_combination_id,
       l.entered_dr, l.entered_crendentered_cr
FROM   igi.igi_bud_journal_lines l, igi.igi_bud_journal_batches b
WHERE  l.be_batch_id = b.be_batch_id
AND    l.be_header_id = :p_header_id;

Reporting use cases include aging of budget journals by START_PERIOD, analysis of recurring versus non-recurring entries, and summarization of debits and credits by CODE_COMBINATION_ID and SET_OF_BOOKS_ID. Because the primary key is composite, any extract should include both BE_HEADER_ID and BE_LINE_NUM to ensure uniqueness.

Related Objects

  • IGI_BUD_JOURNAL_BATCHES — Primary parent object; joined via BE_BATCH_ID.
  • IGI_BUD_JOURNAL_HEADERS — Parent header implied by BE_HEADER_ID and the primary key structure.
  • GL_CODE_COMBINATIONS — Resolves CODE_COMBINATION_ID to the accounting flexfield.
  • GL_SETS_OF_BOOKS / GL_LEDGERS — Resolves SET_OF_BOOKS_ID to the ledger name.
  • IGI_BUD_JOURNAL_BATCHES (FWK) — Additional IGI budgetary control tables that consume these lines for funds checking.

These relationships support joins from low-level budget line detail up through headers, batches, and the general ledger chart of accounts for complete budgetary reporting.