Search Results from_entered_dr

Overview

The APPS.GL_BUDGET_TRANSFER_V view is a General Ledger reporting object that consolidates budget transfer activity within Oracle EBS 12.1.1 and 12.2.2. It unifies two distinct budget transfer mechanisms: legacy transfers that flow through the GL_INTERFACE staging table, and budgetary control transfers that are staged as packets in GL_BC_PACKETS. A discriminating column, ENABLE_BUDGETARY_CONTROL_FLAG, indicates which mechanism produced each row—'N' for interface-based transfers and 'Y' for budgetary control packets. This view is primarily referenced by budget transfer inquiry and reconciliation logic, allowing users and concurrent programs to review transfer amounts, source and category classifications, period context, and the correspondence between "from" and "to" accounting entries from a single query surface.

Underlying Base Objects

The view is defined over five documented base objects, all exposed through APPS synonyms: GL_INTERFACE, GL_BC_PACKETS, GL_JE_SOURCES, GL_JE_CATEGORIES, and GL_PERIOD_STATUSES. The first UNION branch joins GL_INTERFACE (aliased int) to GL_INTERFACE again (aliased to_int), linking the two rows through to_int.rowid = int.status_description. This branch is filtered to the 'Transfer' journal source and the 'Budget' journal category. The second UNION branch draws from GL_BC_PACKETS (aliased pkt), where pkt.reference2 supplies the corresponding "to" row identifier. Both branches join GL_JE_SOURCES and GL_JE_CATEGORIES to resolve user-facing source and category names, and GL_PERIOD_STATUSES to derive period year, period number, and quarter number (restricted to application_id = 101, the General Ledger application). The "to_int" reference in the user's search relates to the self-join alias in the first branch.

Key Columns

• ENABLE_BUDGETARY_CONTROL_FLAG — Literal 'N' for interface-sourced transfers, 'Y' for budgetary control packets.
• FROM_ROW_ID / TO_ROW_ID — Row identifiers linking the source and destination transfer records; TO_ROW_ID resolves to the status description or reference2 depending on the branch.
• LEDGER_ID, GROUP_ID — Ledger context and the grouping identifier (packet_id for budgetary control rows).
• USER_JE_SOURCE_NAME / JE_SOURCE_NAME and USER_JE_CATEGORY_NAME / JE_CATEGORY_NAME — User-entered and internal source and category values.
• PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM, QUARTER_NUM — Accounting period and calendar attributes.
• ACTUAL_FLAG, BUDGET_VERSION_ID, CURRENCY_CODE — Balance type, budget version, and currency.
• TRANSFER_AMOUNT — Computed as abs(nvl(int.entered_dr,0) - nvl(int.entered_cr,0)).
• FROM_ENTERED_DR / FROM_ENTERED_CR / TO_ENTERED_DR / TO_ENTERED_CR — Debit and credit amounts on the source and destination sides.
• ACCOUNTED_DATE, JE_BATCH_NAME, CREATION_DATE, CREATED_BY, STATUS — Accounting date, batch reference, audit stamps, and processing status.

Common Use Cases and Queries

Typical scenarios include auditing budget transfers for a ledger and period, reconciling interface-staged transfers against their posted counterparts, and distinguishing manual from budgetary-control transfers. A representative query lists transfer amounts by period:

• SELECT period_name, ledger_id, transfer_amount, status FROM apps.gl_budget_transfer_v WHERE enable_budgetary_control_flag = 'Y' ORDER BY period_name;
• SELECT group_id, from_code_combination_id, transfer_amount FROM apps.gl_budget_transfer_v WHERE ledger_id = :ledger AND period_name = :period;

Filtering on ENABLE_BUDGETARY_CONTROL_FLAG isolates the desired transfer mechanism, while FROM_CODE_COMBINATION_ID and CURRENCY_CODE narrow results to specific accounts and currencies.