Search Results req_pa_burden

Overview

APPS.PA_XLA_BC_PKT_REQ_DETAIL_V is a Project Accounting (PA) subledger accounting view that exposes requisition and purchase order burden data destined for the Subledger Accounting (SLA / XLA) engine. It provides the detail rows required to create accounting for expenditure items and encumbrances related to requisitions, in particular burden cost lines derived through the Project Burdening process. The view consolidates data from budget and burden packets, resource list members, ledger currency information, and XLA event context to produce a single row per accounting distribution with the source amounts, accounting class assignments, and account identifiers needed for entry creation.

The view is referenced in reporting and diagnostic contexts to trace requisition burdened amounts, verify encumbrance accounting class derivation, and inspect the accounting created for PA requisition distributions when a user searches on "pa_req_burden". Its literal output column returns the value 'PA_REQ_BURDEN', identifying the accounting event class for burdened requisition lines.

Underlying Base Objects

The documented base objects underlying this view are:

• PA_BC_PACKETS (SYNONYM) — the principal driver, aliased as Pbc, supplying budget/burden packet identifiers, distribution identifiers, expenditure types, project and task identifiers, encumbrance type, budget CCID, and burden cost flag.
• PA_RESOURCE_LIST_MEMBERS (SYNONYM) — alias Prlm, providing resource-level attributes such as expenditure category, revenue category, person, and job.
• GL_LEDGERS (SYNONYM) — alias gll, supplying the ledger currency code.
• XLA_EVENTS_GT (SYNONYM) — alias xev_source, providing the XLA event type code used to derive the accounting amount side (debit or credit).
• PA_FUNDS_CONTROL_UTILS (PACKAGE) — a PL/SQL package invoked within the view to derive the PO/requisition amount side, determine the not-upgraded flag for SLA, and compute accounting class values.

Because the view is defined over these synonyms rather than base segment tables, it inherits the standard EBS synonym-to-table indirection and must be queried through the APPS schema with appropriate grants.

Key Columns

Prominent columns include:

• bc_event_id, bc_packet_id, packet_id, parent_bc_packet_id — packet and event identifiers linking rows to burden and budget packet structures.
• document_distribution_id, document_line_id, document_header_id, document_type — document identity columns that tie the row to the underlying requisition or PO distribution.
• expenditure_type, project_id, task_id, expenditure_organization_id, expenditure_item_date — project expenditure attributes.
• accounted_dr / accounted_cr and entered_dr / entered_cr — paired with a DECODE on the derived amount side to yield the correct signed amount column.
• currency_code — sourced twice from GL_LEDGERS, supplying entered and accounted currency codes.
• Enc_Upg_Dr_Acct_Class / Enc_Upg_Cr_Acct_Class — derived accounting class strings such as 'REQ_PA_BURDENED', 'REQ_PA_BURDEN', or 'PA_BUDGET_ENC', selected according to burden method code and amount side.
• budget_ccid — reused to populate Enc_Upg_Dr_Account and Enc_Upg_Cr_Account.
• Use_Enc_Upg_Attrib_Flag — returned by PA_FUNDS_CONTROL_UTILS.get_sla_notupgraded_flag for requisition documents.

Common Use Cases and Queries

Typical uses include verifying that requisition burden amounts are populated correctly, auditing the derived accounting class for encumbrance accounting, and reconciling SLA entries against PA burden packets.

• List all burdened requisition distributions for a given project: SELECT project_id, task_id, expenditure_type, currency_code FROM ap_pa_xla_bc_pkt_req_detail_v WHERE project_id = :project_id AND enc_upg_dr_acct_class = 'REQ_PA_BURDENED';
• Trace a packet's contributing rows: SELECT bc_packet_id, bc_event_id, document_header_id FROM apps.pa_xla_bc_pkt_req_detail_v WHERE bc_packet_id = :packet_id;
• Inspect SLA upgrade flags for requisitions: SELECT document_header_id, document_distribution_id, use_enc_upg_attrib_flag FROM apps.pa_xla_bc_pkt_req_detail_v WHERE use_enc_upg_attrib_flag = 'Y';