Results for “xla_psa_bc_lines_v”

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

Overview

XLA_PSA_BC_LINES_V is a Subledger Accounting (XLA) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the line-level detail of the Prepayment Application and Budgetary Control processing model, correlating validation lines against accounting entry lines for a given subledger transaction. The view is a core component of the XLA Prepayment Application (PSA) architecture, which governs how prepayments, awards, and budgetary control distributions are matched and accounted. Its name reflects its purpose: PSA (Prepayment Application), BC (Budgetary Control), and LINES (line-level detail).

Functionally, the view presents the joined result of two global temporary tables holding validation lines and accounting entry lines. It is primarily used by the XLA engine and by diagnostic or reconciliation reports that must trace how a source distribution was consumed against an applied-to distribution. The presence of numerous APPLY_TO_* columns indicates the view is designed to support bilateral matching, where a source document line is associated with a target (apply-to) document line.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two referenced base objects, both exposed as synonyms in the APPS schema:

• XLA_VALIDATION_LINES_GT — a global temporary table holding the validation lines produced during subledger accounting validation of a transaction. It supplies the left-hand side of the join, aliased as L.
• XLA_AE_LINES_GT — a global temporary table holding the accounting entry lines generated by the application accounting definition. It supplies the right-hand side, aliased as D.

The join is performed on AE_HEADER_ID and AE_LINE_NUM, meaning that each row of the view represents a validation line paired with its corresponding accounting entry line for the same transaction header and line number. Because both objects are global temporary tables, the view is session-scoped and returns data only for the transaction currently being processed within the calling session.

Key Columns

The view exposes a wide set of columns organized into three logical groups:

• Accounting line attributes (from L): LEDGER_ID, EVENT_ID, ENTITY_ID, AE_HEADER_ID, AE_LINE_NUM, BALANCE_TYPE_CODE, ACCOUNTING_DATE, PERIOD_NAME, JE_CATEGORY_NAME, BUDGET_VERSION_ID, ENCUMBRANCE_TYPE_ID, CODE_COMBINATION_ID, ENTERED_CURRENCY_CODE, ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, and ACCOUNTED_CR. These identify the ledger, transaction event, journal category, accounting period, and monetary amounts in both entered and accounted currencies.
• Apply-to (target) identifiers (from D, aliased APPLY_TO_*): BFLOW_APPLICATION_ID, BFLOW_ENTITY_CODE, BFLOW_SOURCE_ID_NUM_1 through _4, BFLOW_SOURCE_ID_CHAR_1 through _4, BFLOW_DISTRIBUTION_TYPE, BFLOW_DIST_ID_NUM_1 through _5, and BFLOW_DIST_ID_CHAR_1 through _5. These columns describe the target distribution or document against which the source is being applied.
• Source distribution identifiers (from D): SOURCE_DISTRIBUTION_TYPE, SOURCE_DISTRIBUTION_ID_CHAR_1 through _5, and SOURCE_DISTRIBUTION_ID_NUM_1 through _4. These describe the originating distribution.

The user search term "source_distribution_type" maps directly to the SOURCE_DISTRIBUTION_TYPE column, which is sourced from XLA_AE_LINES_GT and identifies the classification of the originating distribution (for example, a prepayment, award, or budgetary control distribution).

Common Use Cases and Queries

Typical uses include reconciling prepayment applications, diagnosing budget check failures, and tracing how source distributions map to apply-to distributions during subledger accounting. A representative query filtering on the searched column is:

• SELECT ae_header_id, ae_line_num, source_distribution_type, apply_to_dist_type, entered_dr, entered_cr FROM xla_psa_bc_lines_v WHERE source_distribution_type = 'PREPAY';
• SELECT event_id, period_name, source_distribution_id_num_1, apply_to_source_id_int_1 FROM xla_psa_bc_lines_v WHERE balance_type_code = 'A';
• SELECT code_combination_id, SUM(accounted_dr), SUM(accounted_cr) FROM xla_psa_bc_lines_v GROUP BY code_combination_id;

Because the view relies on session-scoped global temporary tables, queries executed outside an active subledger accounting session will return no rows. It is therefore most appropriately used within XLA diagnostic scripts, custom accounting programs, or during troubleshooting sessions while the transaction is being processed.