Search Results pa_bc_commitments_pk

Overview

The PA_BC_COMMITMENTS_ALL table is a core transactional table within the Oracle E-Business Suite Projects module (PA), specifically for the Project Costing and Project Billing functionalities. Its primary role is to serve as the central repository for all commitment transactions—such as requisitions, purchase orders, and payables invoices—that have undergone funds checking. The table acts as a staging area between the source procurement or payables transactions and the summarized project balances. When the "Maintain Project Balances" concurrent program executes, it processes the records in this table, sweeping the commitment amounts into the project's summarized financial balances, which are used for budgeting, forecasting, and funds control.

Key Information Stored

The table stores detailed attributes that link a financial commitment to a specific project and task, and to its originating source document. Key columns include BC_COMMITMENT_ID (the primary key), PROJECT_ID, TASK_ID, and TOP_TASK_ID for project structure linkage. Critical financial and reference columns are BUDGET_VERSION_ID (linking to the budget against which funds are checked), EXPENDITURE_TYPE, and RESOURCE_LIST_MEMBER_ID. To maintain the connection to the source transaction, the table holds document identifiers such as DOCUMENT_HEADER_ID and DOCUMENT_DISTRIBUTION_ID, which join to tables like PO_HEADERS_ALL, PO_DISTRIBUTIONS_ALL, AP_INVOICES_ALL, and PO_REQ_DISTRIBUTIONS_ALL. The SET_OF_BOOKS_ID links the commitment to the general ledger.

Common Use Cases and Queries

A primary use case is troubleshooting funds checking results or analyzing commitment details that feed project balances. Common queries involve joining to source documents to get a complete view of committed costs. For instance, to analyze purchase order commitments for a specific project, a query might join to PO_HEADERS_ALL and PO_DISTRIBUTIONS_ALL. Another critical scenario is reconciling project commitments before running the "Maintain Project Balances" program. Sample SQL to find all commitments for a project would be:

• SELECT pbc.* FROM pa_bc_commitments_all pbc WHERE pbc.project_id = <project_id>;
• SELECT pbc.bc_commitment_id, pbc.project_id, pt.task_number, poh.segment1 po_number, pod.quantity_ordered FROM pa_bc_commitments_all pbc JOIN pa_tasks pt ON pbc.task_id = pt.task_id JOIN po_headers_all poh ON pbc.document_header_id = poh.po_header_id JOIN po_distributions_all pod ON pbc.document_distribution_id = pod.po_distribution_id WHERE pbc.project_id = <project_id>;

Related Objects

PA_BC_COMMITMENTS_ALL has extensive relationships with other EBS tables, as evidenced by its foreign keys. It is directly linked to core project tables like PA_PROJECTS_ALL, PA_TASKS, PA_BUDGET_VERSIONS, and PA_EXPENDITURE_TYPES. Its primary integration with external modules is through relationships with procurement tables (PO_HEADERS_ALL, PO_DISTRIBUTIONS_ALL, PO_REQ_DISTRIBUTIONS_ALL) and payables tables (AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL). It also links to PA_COST_DISTRIBUTION_LINES_ALL for costed labor and expense items. The table's primary key constraint is PA_BC_COMMITMENTS_PK. The summarized results of its data are reflected in various project balance and funds available views.