Search Results from_code_combination_id

Overview

The GL_BUDGET_TRANSFER_V view is an Oracle E-Business Suite General Ledger database object owned by the APPS schema and classified with a status of VALID. Per the ETRM documentation, its description is marked as "10SC ONLY," indicating that the object is restricted to a specific localization or deployment context (commonly associated with the 10SC configuration) rather than a general-purpose GL deliverable. The view consolidates budget transfer activity originating from journal interface rows and budget control packets, presenting a unified projection of transfers across ledgers and periods.

Its principal role is to expose budgetary transfer records for reporting, validation, and downstream integration. The view combines journal source, journal category, and period status information with the interface and packet data, enabling consumers to reconcile transfer amounts, accounted dates, and ledger context without directly joining several GL tables.

Underlying Base Objects

The documented referenced base objects for this view are GL_BC_PACKETS, GL_INTERFACE, GL_JE_CATEGORIES, and GL_JE_SOURCES, all accessed via synonyms, together with GL_PERIOD_STATUSES. The view text demonstrates that it is built as a UNION of two queries: the first selects from GL_INTERFACE filtered on the 'TRANSFER' journal source and 'BUDGET' category, and the second selects from GL_BC_PACKETS (referenced as PKT). In both branches, GL_JE_SOURCES supplies the user and internal source names, GL_JE_CATEGORIES supplies the category names, and GL_PERIOD_STATUSES supplies period year, period number, and quarter number for the ledger.

Key Columns

• ENABLE_BUDGETARY_CONTROL_FLAG — 'N' for interface-derived rows and 'Y' for budget control packet rows.
• ACCOUNTED_DATE — mapped from INT.ACCOUNTING_DATE, representing the accounting date of the transfer, and the column most commonly searched by users.
• LEDGER_ID, PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM, QUARTER_NUM — ledger and period context.
• TRANSFER_AMOUNT — the absolute net of entered debit and credit amounts.
• FROM_ENTERED_DR, FROM_ENTERED_CR, TO_ENTERED_DR, TO_ENTERED_CR — source and destination entered amounts.
• USER_JE_SOURCE_NAME, JE_SOURCE_NAME, USER_JE_CATEGORY_NAME, JE_CATEGORY_NAME — source and category identification.
• STATUS, STATUS_DESCRIPTION, BUDGET_VERSION_ID, CURRENCY_CODE, GROUP_ID, JE_BATCH_NAME, CREATION_DATE — transfer status and metadata.

Common Use Cases and Queries

Typical uses include auditing budget transfers by ledger and period, tracing transfers to their source interface rows, and reconciling packet-based transfers. Because the view exposes an ACCOUNTED_DATE column, users frequently filter on it.

• List transfers for a ledger within a period:
  SELECT LEDGER_ID, PERIOD_NAME, TRANSFER_AMOUNT, ACCOUNTED_DATE FROM APPS.GL_BUDGET_TRANSFER_V WHERE PERIOD_NAME = :p_period;
• Retrieve transfers by accounted date range:
  SELECT * FROM APPS.GL_BUDGET_TRANSFER_V WHERE ACCOUNTED_DATE BETWEEN :p_from AND :p_to;
• Separate interface versus budgetary-control transfers using the ENABLE_BUDGETARY_CONTROL_FLAG.