Search Results pa_po_burden




Overview
Explore in AI Chat

Overview

APPS.PA_XLA_BC_PKT_PO_DETAIL_V is a Subledger Accounting (XLA) supporting view belonging to the Projects (PA) application in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes purchase order and requisition distribution details associated with burden cost packets maintained in the Projects budgeting and encumbrance accounting flows, presenting them in a structure consumed by the XLA accounting engine when generating subledger journal entries. Because the view is owned by APPS and referenced by XLA packet-processing logic, it functions as an integration layer between Projects Funds Control, Purchasing distributions, and the SLA accounting model. The user search term "document_type" is central to this view: pbc.document_type is carried through much of the view's logic, driving the decode branches that distinguish purchase order ('PO') from requisition ('REQ') processing.

Underlying Base Objects

The documented base objects underlying this view are:

  • PA_BC_PACKETS (synonym) — the primary burden cost packet table, supplying bc_packet_id, bc_event_id, document_type, main_or_backing_code, and related distribution columns.
  • PA_FUNDS_CONTROL_UTILS (package) — supplies the DERIVE_PO_REQ_AMT_SIDE and GET_SLA_NOTUPGRADED_FLAG functions used to compute debit/credit direction and upgrade flags.
  • PA_RESOURCE_LIST_MEMBERS (synonym) — referenced as Prlm, providing event type, expenditure/revenue category, person, and job attributes.
  • GL_LEDGERS (synonym) — referenced as gll, supplying the currency_code for the ledger.
  • XLA_EVENTS_GT (synonym) — referenced as xev_source, supplying the source event_type_code used in amount-side derivation.
  • PO_DOCUMENT_FUNDS_PVT (package) — referenced in the PO funds control logic underlying the view's distribution sourcing.

Key Columns

Common Use Cases and Queries

The view is principally used to diagnose and report on burden cost packets arising from purchase order and requisition encumbrance flows, and to trace amounts feeding XLA journal entries.

  • Identifying all distribution rows for a given packet.
  • Isolating requisition versus purchase order documents by document_type.
  • Reconciling accounted versus entered amounts by side.

Sample query:

SELECT bc_packet_id, document_type, document_header_id,
DECODE(document_type,'PO','PO_DISTRIBUTIONS_ALL','PO_REQ_DISTRIBUTIONS_ALL') source,
accounted_dr, accounted_cr, entered_dr, entered_cr, currency_code
FROM apps.pa_xla_bc_pkt_po_detail_v
WHERE bc_packet_id = :p_packet_id;

A second common query filters by document_type to audit requisition-sourced burden packets for a project. Because the view embeds function calls, queries should bind on indexed columns such as BC_PACKET_ID or DOCUMENT_HEADER_ID where practical.