Search Results pa_bc_commitments_n1

Overview

PA.PA_BC_COMMITMENTS_ALL is a transactional table within the Oracle E-Business Suite Projects (PA) schema that stores commitment, encumbrance, and budgetary control records associated with project expenditures. It is the primary staging and accumulation table for budgetary control (BC) processing in Oracle Projects, holding rows that represent purchase order commitments, requisition encumbrances, accounts payable invoice commitments, and their relief (liquidation) entries. The table mediates between source purchasing and payables transactions and the project budget engine, enabling funds checking and budgetary control against project budget versions.

The object is registered as a multi-org view within the Applications schema layer (FND Design Data: PA.PA_BC_COMMITMENTS_ALL), which causes queries to be filtered automatically by the current operating unit. Rows are physically stored in the APPS_TS_TX_DATA tablespace, and all associated indexes reside in APPS_TS_TX_IDX. The table status is documented as VALID under ETRM for both 12.1.1 and 12.2.2.

From a dimensional modeling perspective, the Data Vault classification heuristic applied to this object is link. This reflects its role as an associative table connecting project, task, budget version, purchasing document, and accounting entities through a dense network of foreign keys rather than acting as a standalone hub or a descriptive satellite.

Key Information Stored

The table contains 75 documented columns. The most significant are summarized below.

• BC_COMMITMENT_ID — the numeric surrogate primary key defined by constraint PA_BC_COMMITMENTS_PK. A unique index, PA_BC_COMMITMENTS_U1, is also defined on this column, making it the single documented business-key candidate.
• PROJECT_ID, TASK_ID, TOP_TASK_ID — identify the project and task hierarchy against which the commitment applies.
• BUDGET_VERSION_ID, BUDGET_LINE_ID — link the commitment to the project budget version and budget line under funds control.
• EXPENDITURE_TYPE, EXPENDITURE_ITEM_DATE, EXP_ITEM_ID — describe the expenditure classification and the related expenditure item date for the commitment.
• DOCUMENT_TYPE, DOCUMENT_HEADER_ID, DOCUMENT_DISTRIBUTION_ID, DOCUMENT_LINE_ID — identify the originating purchasing or payables document and its distribution line.
• ENCUMBRANCE_TYPE_ID, JE_CATEGORY_NAME, JE_SOURCE_NAME, SET_OF_BOOKS_ID — carry the accounting context for the encumbrance journal entry.
• ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR — hold the monetary amounts in entered and accounted currencies.
• GL_DATE, PA_DATE, LIQUIDATE_GL_DATE, TRANSFERRED_DATE — date stamps governing the accounting period, project date, liquidation, and transfer status.
• TRANSFER_STATUS_CODE — indicates whether the row has been transferred to the general ledger.
• ORG_ID — the operating unit discriminator enforced by the multi-org view.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — standard concurrent program audit columns maintained when a batch process populates the row.

Common Use Cases and Queries

Consultants and developers query this table to reconcile project commitments, trace funds checking outcomes, and audit the transfer of encumbrances to GL. Typical joining patterns exploit the indexed columns: PROJECT_ID combined with EXPENDITURE_ITEM_DATE (index PA_BC_COMMITMENTS_N1), DOCUMENT_TYPE (N2), GL_DATE (N3), BUDGET_VERSION_ID (N4), DOCUMENT_HEADER_ID with DOCUMENT_DISTRIBUTION_ID (N5), TRANSFER_STATUS_CODE and REQUEST_ID (N6), EXP_ITEM_ID (N7), and BC_EVENT_ID (N8).

A representative query retrieves un-transferred commitments for a project:

• SELECT bc_commitment_id, project_id, task_id, entered_dr, entered_cr, gl_date FROM pa.pa_bc_commitments_all WHERE project_id = :p_project_id AND transfer_status_code IS NULL ORDER BY gl_date;

Another common pattern joins the table to budget versions to review funds consumption:

• SELECT c.project_id, c.budget_version_id, SUM(c.entered_dr) FROM pa.pa_bc_commitments_all c WHERE c.set_of_books_id = :p_sob GROUP BY c.project_id, c.budget_version_id;

Because the object is exposed as a multi-org view, queries executed under an operating unit context automatically restrict rows to that unit's ORG_ID.

Related Objects

The table participates in an extensive foreign-key network with master and transactional data across Projects, Purchasing, Payables, and General Ledger.

• PA.PA_PROJECTS_ALL — joined on PROJECT_ID; the project definition.
• PA.PA_TASKS — joined on TASK_ID and TOP_TASK_ID; the task hierarchy.
• PA.PA_BUDGET_VERSIONS and PA.PA_BUDGET_LINES — joined on BUDGET_VERSION_ID and BUDGET_LINE_ID; the budget context.
• PO.PO_HEADERS_ALL and PO.PO_DISTRIBUTIONS_ALL — joined on DOCUMENT_HEADER_ID and DOCUMENT_DISTRIBUTION_ID; the purchasing source for commitments.
• AP.AP_INVOICES_ALL and AP.AP_INVOICE_DISTRIBUTIONS_ALL — joined on DOCUMENT_HEADER_ID and AIL_INVOICE_ID; the payables source.
• GL.GL_SETS_OF_BOOKS_11I and GL.GL_ENCUMBRANCE_TYPES — joined on SET_OF_BOOKS_ID and ENCUMBRANCE_TYPE_ID; the accounting context.
• PA.PA_BC_PACKETS — references this table on BC_COMMITMENT_ID, grouping commitments into packets for processing.
• PA.PA_EXPENDITURE_TYPES — joined on EXPENDITURE_TYPE; classifies the commitment expenditure.