Search Results p_funds_control_level_code

Overview

PA_BC_PACKETS is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores transactions copied from the General Ledger Budgetary Control staging table GL_BC_PACKETS. Functionally, it operates as a temporary or staging table used during budgetary control and funds checking: it captures the relevant attributes of each transaction along with derived attribute values computed before funds checking is performed against project budgets, encumbrances, and actuals. The table is owned by the PA schema and is documented as a valid object in ETRM with 121 columns.

From a Data Vault modeling perspective, the metadata's heuristic classification of this table is link, reflecting the fact that it records associations between projects, tasks, resources, commitments, documents, and expenditure types rather than serving as a stable master or descriptive satellite. This classification should be treated as a modeling suggestion; in practice the table's transient nature makes it closer to a transient transaction staging structure than a durable enterprise link.

Key Information Stored

The table's primary key is PACKET_ID combined with BC_PACKET_ID, enforced by the unique index PA_BC_PACKETS_PK; the same column pair also appears in PA_BC_PACKETS_U1, making it the documented business-key candidate. Important columns include:

PACKET_ID / BC_PACKET_ID — surrogate and cross-reference identifiers linking the row to its GL budgetary control packet.
PROJECT_ID, TASK_ID, TOP_TASK_ID — project and task context for funds checking.
EXPENDITURE_TYPE, EXPENDITURE_ITEM_DATE — classification and transaction date of the expenditure.
SET_OF_BOOKS_ID, GL_DATE, PA_DATE, PERIOD_NAME — ledger and accounting period context.
ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR — entered and accounted debit/credit amounts.
ENCUMBRANCE_AMOUNT, ENCUMBRANCE_TYPE_ID, BC_COMMITMENT_ID — encumbrance and commitment linkage.
BUDGET_VERSION_ID, BUDGET_LINE_ID, BUDGET_CCID, OLD_BUDGET_CCID — budget version and account references.
RESOURCE_LIST_MEMBER_ID, PARENT_RESOURCE_ID — resource grouping used in funds control.
DOCUMENT_HEADER_ID, DOCUMENT_DISTRIBUTION_ID, DOCUMENT_TYPE — source document context (PO, AP invoice, etc.).
FUNDS_PROCESS_MODE, EFFECT_ON_FUNDS_CODE, RESULT_CODE — outcome of funds processing.
STATUS_CODE, ACTUAL_FLAG, BALANCE_POSTED_FLAG — processing state indicators.

Common Use Cases and Queries

Typical usage centers on diagnosing funds-check failures, tracing encumbrance and budget balances, and reconciling PA transactions against GL budgetary control output.

SELECT p.packet_id, p.project_id, p.task_id,
       p.expenditure_type, p.encumbrance_amount,
       p.result_code, p.status_code
FROM   pa.pa_bc_packets p
WHERE  p.set_of_books_id = :sob_id
AND    p.period_name    = :period;

A second common pattern joins to project and task for reporting on funds-control results:

SELECT p.project_id, t.task_number,
       p.expenditure_type, p.entered_dr, p.accounted_dr,
       p.effect_on_funds_code
FROM   pa.pa_bc_packets p, pa.pa_tasks t
WHERE  p.task_id = t.task_id
AND    p.result_code IS NOT NULL;

Because the table holds transient data derived from GL_BC_PACKETS, queries are usually scoped by REQUEST_ID, SESSION_ID, or FUNDS_PROCESSING_SEQ to isolate a specific funds-check run.

Related Objects

GL_BC_PACKETS — source table from which rows are copied.
PA_PROJECTS_ALL via PROJECT_ID.
PA_TASKS via TASK_ID; PA_TOP_TASKS_IT via TOP_TASK_ID.
PA_BUDGET_VERSIONS via BUDGET_VERSION_ID; PA_BUDGET_LINES via BUDGET_LINE_ID.
PO_HEADERS_ALL and PO_DISTRIBUTIONS_ALL via DOCUMENT_HEADER_ID and DOCUMENT_DISTRIBUTION_ID.
AP_INVOICES_ALL via DOCUMENT_HEADER_ID.
PA_BC_COMMITMENTS_ALL via BC_COMMITMENT_ID.
GL_SETS_OF_BOOKS_11I via SET_OF_BOOKS_ID; GL_ENCUMBRANCE_TYPES via ENCUMBRANCE_TYPE_ID.
PA_EXPENDITURE_TYPES via EXPENDITURE_TYPE.
PA_RESOURCE_LIST_MEMBERS via RESOURCE_LIST_MEMBER_ID.

Table: PA_BC_PACKETS 12.2.2
owner:PA, object_type:TABLE, fnd_design_data:PA.PA_BC_PACKETS, object_name:PA_BC_PACKETS, status:VALID, product: PA - Projects , description: PA_BC_PACKETS holds all the transactions that copied from GL_BC_PACKETS. This a type of temporary table which holds all the relevant attributes of a transaction in addition to some other attribute values which are derived before they are p , implementation_dba_data: PA.PA_BC_PACKETS ,
Table: PA_BC_PACKETS 12.1.1
owner:PA, object_type:TABLE, fnd_design_data:PA.PA_BC_PACKETS, object_name:PA_BC_PACKETS, status:VALID, product: PA - Projects , description: PA_BC_PACKETS holds all the transactions that copied from GL_BC_PACKETS. This a type of temporary table which holds all the relevant attributes of a transaction in addition to some other attribute values which are derived before they are p , implementation_dba_data: PA.PA_BC_PACKETS ,
View: PA_TRX_FUNDS_CHK_DET_V 12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PA.PA_TRX_FUNDS_CHK_DET_V, object_name:PA_TRX_FUNDS_CHK_DET_V, status:VALID, product: PA - Projects , implementation_dba_data: APPS.PA_TRX_FUNDS_CHK_DET_V ,
View: PA_TRX_FUNDS_CHK_DET_V 12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PA.PA_TRX_FUNDS_CHK_DET_V, object_name:PA_TRX_FUNDS_CHK_DET_V, status:VALID, product: PA - Projects , implementation_dba_data: APPS.PA_TRX_FUNDS_CHK_DET_V ,