Results for “entered_amount”

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

Overview

PA_XLA_BC_BUDGET_LINES_V is an Oracle E-Business Suite view owned by the APPS schema in the Projects (PA) product family. It exposes budgetary control event data sourced from project budget lines and joins them to the Subledger Accounting (XLA) event model. The view is one of the internal integration points between Oracle Projects budgeting functionality and the XLA accounting engine, and it is registered for use in ETRM (Enterprise Tax and Reporting Model) contexts in both EBS 12.1.1 and 12.2.2.

The name reflects its purpose: "BC" denotes budgetary control, "BUDGET_LINES" identifies the source of the underlying amounts, and the "_V" suffix confirms it is a view rather than a table. In practice it is used to feed budget-related accounting event data — specifically the balance type (encumbrance or budget) and the corresponding amounts — into downstream XLA processing.

Underlying Base Objects

The view is defined over the following documented base objects:

• PA_BUDGET_LINES (PBL) — the primary factual source, supplying budget amounts, periods, attributes, and the BC_EVENT_ID foreign key.
• PA_RESOURCE_ASSIGNMENTS (PRA) — provides the project, task, and resource assignment context.
• PA_RESOURCE_LIST_MEMBERS (PRLM) — supplies expenditure type, event type, expenditure category, revenue category, person, job, vendor, and organization identifiers.
• XLA_EVENTS_GT (XEV) — the global temporary table holding XLA event information, joined on BC_EVENT_ID = XEV.EVENT_ID.
• GL_LEDGERS (GLL) — supplies the ledger and currency code.
• PA_BUDGETARY_CONTROL_OPTIONS (PBCO) — determines whether the balance is encumbrance (E) or budget (B).
• PA_BUDGET_VERSIONS (PBV) and PA_BUDGET_TYPES (PBT) — provide budget version and budget amount code semantics.
• PA_FUNDS_CONTROL_UTILS — a PL/SQL package referenced indirectly by the definition.

Key Columns

• BC_EVENT_ID — the budgetary control event identifier linking the budget line to the XLA event; the primary join key for accounting integration.
• SOURCE_ID_INT_1 — the XLA event source identifier from XLA_EVENTS_GT.
• BUDGET_LINE_ID, PROJECT_ID, TASK_ID — project and budget line identifiers for reporting and drill-down.
• PERIOD_NAME — the accounting period associated with the budget line.
• ACCT_AMOUNT / ENTERED_AMOUNT — derived amounts computed through DECODE logic based on BALANCE_TYPE and BUDGET_AMOUNT_CODE; encumbrance balances use burdened cost where available, revenue balances use the revenue column.
• LEDGER_ID, CURRENCY_CODE — ledger and currency context inherited from GL_LEDGERS.
• ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield columns carried through from PA_BUDGET_LINES.
• Additional columns expose expenditure category, revenue category, person, job, and vendor for analytical reporting.

Common Use Cases and Queries

Typical uses include reconciling budget and encumbrance balances to XLA events, drilling from accounting entries back to the originating budget line, and building custom budget-versus-actual reports. A representative query:

SELECT BC_EVENT_ID, PROJECT_ID, TASK_ID, PERIOD_NAME,
       ACCT_AMOUNT, ENTERED_AMOUNT, CURRENCY_CODE
FROM   APPS.PA_XLA_BC_BUDGET_LINES_V
WHERE  PROJECT_ID = :project_id
AND    PERIOD_NAME = :period_name;

Because the view accesses a global temporary table (XLA_EVENTS_GT), queries should generally be issued within the same session context that populated those events, typically during subledger accounting transfer or reporting runs. Joining BC_EVENT_ID back to XLA_EVENTS or XLA_AE_HEADERS is the standard technique for tracing a budget line to its generated journal entries.