Search Results purchase_order
Overview
PA_XLA_BC_PKT_PO_DETAIL_V is a Subledger Accounting (SLA/XLA) supporting view owned by the APPS schema within the Oracle E-Business Suite Projects (PA) module. Its name reflects its function: it exposes the purchase order and requisition distribution detail associated with Burden Cost (BC) packets that are processed by the Projects SLA/XLA accounting engine. It is designated a "detail" view because it flattens the encumbrance and accounting distribution lines that feed the creation of XLA events and their corresponding journal entries for procurement-related project expenditures.
The view is primarily consumed by the Subledger Accounting programs that derive and populate the XLA_AE_HEADERS and XLA_AE_LINES tables for project burden cost transactions. Because it joins procurement documents (purchase orders and requisitions) to Projects burden packet structures, it is relevant to funds control, encumbrance accounting, and budgetary reconciliation reporting. The view is delivered VALID in both 12.1.1 and 12.2.2 releases.
Underlying Base Objects
The view is defined over the following documented base objects, joined through synonyms and utility packages:
- PA_BC_PACKETS (SYNONYM) — the central burden cost packet table providing BC_EVENT_ID, BC_PACKET_ID, DOCUMENT_DISTRIBUTION_ID, DOCUMENT_TYPE, BUDGET_VERSION_ID, and MAIN_OR_BACKING_CODE.
- GL_LEDGERS (SYNONYM) — supplies CURRENCY_CODE for the ledger associated with the transaction.
- PA_RESOURCE_LIST_MEMBERS (SYNONYM) — provides event type, expenditure and revenue categories, person and job identifiers for the resource definitions behind the packet.
- XLA_EVENTS_GT (SYNONYM) — the XLA events global temporary table used to resolve the EVENT_TYPE_CODE referenced by the accounting derivation logic.
- PA_FUNDS_CONTROL_UTILS (PACKAGE) — a PL/SQL package invoked within the view text to derive the PO/REQ amount side, burden cost types, and legacy upgrade attributes.
- PO_DOCUMENT_FUNDS_PVT (PACKAGE) — referenced for procurement document funds logic.
The view is therefore a composite layer that joins procurement distributions to Projects packet data and uses package functions to compute the appropriate debit or credit side for each distribution line.
Key Columns
- BC_EVENT_ID / BC_PACKET_ID / PACKET_ID — identifiers linking the row to the originating burden cost packet and event.
- DOCUMENT_DISTRIBUTION_ID / DOCUMENT_LINE_ID / DOCUMENT_HEADER_ID — keys to the source PO or requisition distribution, line, and header.
- DOCUMENT_TYPE — distinguishes 'PO' (purchase order) from 'REQ' (requisition) and drives burden name mapping ('PA_PO_BURDEN' vs 'PA_REQ_BURDEN').
- ACCOUNTED_DR / ACCOUNTED_CR / ENTERED_DR / ENTERED_CR — the accounted and entered amounts, selected on the appropriate side by PA_FUNDS_CONTROL_UTILS.DERIVE_PO_REQ_AMT_SIDE.
- PROJECT_ID / TASK_ID / EXPENDITURE_ORGANIZATION_ID / EXPENDITURE_ITEM_DATE — Projects expenditure attributes for the distribution.
- ENCUMBRANCE_TYPE_ID / PROJ_ENCUMBRANCE_TYPE_ID — encumbrance classification for funds control.
- CURRENCY_CODE, SET_OF_BOOKS_ID, BUDGET_CCID, BUDGET_VERSION_ID, BUDGET_LINE_ID — ledger, budget, and currency context.
- USE_ENC_UPG_ATTRIB_FLAG — derived flag indicating whether the encumbrance upgrade attribute path applies.
- MAIN_OR_BACKING_CODE / BURDEN_COST_FLAG — classification of the distribution as main or backing and whether it represents burden.
Common Use Cases and Queries
Typical scenarios include auditing the amount side selected for a PO/REQ distribution, verifying encumbrance upgrade flags, and reconciling burden packet events to their procurement source.
Example: list distributions for a given packet.
SELECT bc_event_id, document_distribution_id, document_type, project_id, task_id, currency_code, budget_version_id FROM pa_xla_bc_pkt_po_detail_v WHERE bc_packet_id = :p_packet_id;
Example: identify rows requiring the encumbrance upgrade attribute.
SELECT bc_event_id, document_header_id, document_distribution_id, use_enc_upg_attrib_flag FROM pa_xla_bc_pkt_po_detail_v WHERE use_enc_upg_attrib_flag IS NOT NULL;
Because the view embeds package function calls, queries should be constrained by packet or event identifiers to avoid full-table evaluation of the underlying derivation logic. Outputs feed the Projects SLA accounting programs, so results should generally be correlated to XLA_EVENTS_GT and the resulting journal entries.
-
View: PA_XLA_BC_PKT_PO_DETAIL_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PA.PA_XLA_BC_PKT_PO_DETAIL_V, object_name:PA_XLA_BC_PKT_PO_DETAIL_V, status:VALID, product: PA - Projects , implementation_dba_data: APPS.PA_XLA_BC_PKT_PO_DETAIL_V ,
-
View: PA_XLA_BC_PKT_PO_DETAIL_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PA.PA_XLA_BC_PKT_PO_DETAIL_V, object_name:PA_XLA_BC_PKT_PO_DETAIL_V, status:VALID, product: PA - Projects , implementation_dba_data: APPS.PA_XLA_BC_PKT_PO_DETAIL_V ,
-
View: PA_XLA_BC_PKT_AP_DETAIL_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PA.PA_XLA_BC_PKT_AP_DETAIL_V, object_name:PA_XLA_BC_PKT_AP_DETAIL_V, status:VALID, product: PA - Projects , implementation_dba_data: APPS.PA_XLA_BC_PKT_AP_DETAIL_V ,
-
View: PA_XLA_BC_PKT_AP_DETAIL_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PA.PA_XLA_BC_PKT_AP_DETAIL_V, object_name:PA_XLA_BC_PKT_AP_DETAIL_V, status:VALID, product: PA - Projects , implementation_dba_data: APPS.PA_XLA_BC_PKT_AP_DETAIL_V ,
-
View: PA_XLA_CDL_LINES_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PA.PA_XLA_CDL_LINES_V, object_name:PA_XLA_CDL_LINES_V, status:VALID, product: PA - Projects , implementation_dba_data: APPS.PA_XLA_CDL_LINES_V ,
-
View: PA_XLA_CDL_LINES_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PA.PA_XLA_CDL_LINES_V, object_name:PA_XLA_CDL_LINES_V, status:VALID, product: PA - Projects , implementation_dba_data: APPS.PA_XLA_CDL_LINES_V ,