Results for “igi_bud_journal_lines_v”

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

Overview

IGI_BUD_JOURNAL_LINES_V is an APPS-owned database view within the Oracle E-Business Suite product IGI — Public Sector Financials International. In EBS 12.1.1 and 12.2.2, the object carries a VALID status in the ETRM repository and is documented as "Based on IGI_BUD_JOURNAL_LINES." The view does not persist data of its own; it provides a read-only presentation layer over the budget journal line records maintained by the IGI budgeting engine, exposing journal line attributes together with the standard Oracle who-columns and a ROWID-derived identifier.

The view is significant for reporting and integration because budget journal lines in the public sector budgeting model are frequently queried directly by external tools, custom concurrent programs, and interfaces rather than through the base table. It presents a stable, flattened projection of the journal line entity, and it is the object of interest when users search on attributes such as fye_pye_entry, a budget-specific indicator that signals whether a line represents a fiscal-year-end or prior-year-end entry.

Underlying Base Objects

The documented definition is a straightforward projection over a single base object:

• IGI_BUD_JOURNAL_LINES — the base table (referenced in the ETRM metadata as a synonym) that stores budget journal line records for IGI budgeting.

The view text selects every column from the base table using the alias JL, with no joins, filters, or aggregations. The only transformation is the exposure of JL.ROWID as ROW_ID. Consequently, the view is one-to-one with IGI_BUD_JOURNAL_LINES: every row in the table appears exactly once, and no columns are dropped or renamed other than the ROWID alias. Because there are no joins, query performance against the view is effectively the same as querying the base table, and no duplicate-row risk exists.

Key Columns

• ROW_ID — the ROWID of the base table row, exposed for tools that require a unique row identifier.
• BE_BATCH_ID, BE_HEADER_ID, BE_LINE_NUM — budget entry batch, header, and line identifiers establishing the journal line's position in the budgeting hierarchy.
• SET_OF_BOOKS_ID — the ledger (set of books) to which the budget journal belongs.
• CODE_COMBINATION_ID — the accounting flexfield combination charged or credited by the line.
• RECORD_TYPE — classifies the line within the budget entry process.
• ENTERED_DR, ENTERED_CR — the entered debit and credit amounts for the line.
• NEXT_YEAR_BUDGET — flag indicating the line affects next-year budget balances.
• FYE_PYE_ENTRY — the fiscal-year-end / prior-year-end entry indicator. This is the column associated with the user search term "fye_pye_entry" and distinguishes closing and prior-period budget entries from ordinary budget journal activity.
• DESCRIPTION — free-form line description.
• PROFILE_CODE — identifies the budget profile governing the line.
• START_PERIOD — the period in which the budget line takes effect.
• REASON_CODE — reason or justification code attached to the entry.
• RECURRING_ENTRY — flag indicating whether the line forms part of a recurring budget entry.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle audit columns recording insert and update history.

Common Use Cases and Queries

Typical scenarios include reconciling budget journal lines to the budget entry batch, reporting fiscal-year-end and prior-year-end budget adjustments, and extracting budget data for integration with feeder systems or data warehouses. Because the view is a thin projection, it is often used in place of the base table to insulate custom code from direct table references.

Retrieving all lines for a batch:

SELECT ROW_ID, BE_BATCH_ID, BE_HEADER_ID, BE_LINE_NUM,
       CODE_COMBINATION_ID, ENTERED_DR, ENTERED_CR
FROM   APPS.IGI_BUD_JOURNAL_LINES_V
WHERE  BE_BATCH_ID = :p_batch_id
ORDER  BY BE_LINE_NUM;

Isolating fiscal-year-end and prior-year-end entries, tying directly to the search term:

SELECT BE_BATCH_ID, BE_HEADER_ID, BE_LINE_NUM,
       CODE_COMBINATION_ID, ENTERED_DR, ENTERED_CR, FYE_PYE_ENTRY
FROM   APPS.IGI_BUD_JOURNAL_LINES_V
WHERE  FYE_PYE_ENTRY IS NOT NULL
AND    SET_OF_BOOKS_ID = :p_set_of_books_id;

Filtering by budget profile, start period, or recurring status supports period-close reporting and recertification of recurring budget entries. All queries should be executed against the APPS schema or a synonym with appropriate grants, since the view inherits the security and privileges of IGI_BUD_JOURNAL_LINES.