Search Results liquidate_gl_date

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_BC_COMMITMENTS_ALL is the Oracle Projects (PA) intersection table that stores funds-checked commitment transactions originating from requisitions, purchase orders, and Payables invoices. It resides in the PA schema and represents the staging and audit layer between the source procurement or payables document and the Project Budgeting and Commitments (BC) engine. When the Maintain Project Balances concurrent programs sweep commitment records into project balances, the qualifying commitment rows are inserted into this table. It therefore acts as the authoritative record of what has been encumbered against a project, task, and budget version before the amounts are rolled into PA project balances and reconciled against GL encumbrances.

Under the heuristic Data Vault classification supplied in the metadata, PA_BC_COMMITMENTS_ALL is best modeled as a link table. Its structure is dominated by foreign-key references to projects, tasks, resources, budgets, distribution lines, and encumbrance types, forming a many-to-many connective hub-and-link lattice rather than a pure descriptive satellite. The single-column primary key PA_BC_COMMITMENTS_PK on BC_COMMITMENT_ID is a surrogate identifier generated from the PA_BC_COMMITMENTS_S sequence; a unique index, PA_BC_COMMITMENTS_U1, guards the same column as the business-key candidate.

Key Information Stored

The 75 documented columns capture commitment identity, document lineage, project attribution, accounting amounts, and processing status. The most important include:

• BC_COMMITMENT_ID — surrogate primary key and unique-index business-key candidate; the row identifier.
• PROJECT_ID, TASK_ID, TOP_TASK_ID — the project and task hierarchy the commitment is charged to, joined to PA_PROJECTS_ALL and PA_TASKS.
• EXPENDITURE_TYPE — the expenditure category controlling cost and burden treatment, joined to PA_EXPENDITURE_TYPES.
• DOCUMENT_TYPE, DOCUMENT_HEADER_ID, DOCUMENT_DISTRIBUTION_ID, DOCUMENT_LINE_ID — the originating document and its distribution; header and distribution IDs resolve to PO_HEADERS_ALL, PO_DISTRIBUTIONS_ALL, AP_INVOICES_ALL, and AP_INVOICE_DISTRIBUTIONS_ALL depending on document type.
• PDL_PO_DISTRIBUTION_ID, PRL_DISTRIBUTION_ID, PCL_LINE_NUM, PCL_EXPENDITURE_ITEM_ID — explicit lineage to PO distributions, requisition distributions, and project cost distribution lines.
• ENCUMBRANCE_TYPE_ID / PROJ_ENCUMBRANCE_TYPE_ID — the GL encumbrance classification, joined to GL_ENCUMBRANCE_TYPES.
• BUDGET_VERSION_ID, BUDGET_LINE_ID — the budget version and line the commitment is checked against.
• ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR — the commitment amounts in entered and accounted currency.
• COMM_TOT_RAW_AMT, COMM_TOT_BD_AMT, COMM_RAW_AMT_RELIEVED, COMM_BD_AMT_RELIEVED — total and relieved commitment amounts in raw and burdened terms.
• TRANSFER_STATUS_CODE, TRANSFERRED_DATE, COMMITMENT_BATCH_NAME, COMM_TRANSFER_REJ_REASON — transfer-to-balances state and rejection detail.
• PERIOD_NAME, PERIOD_NUM, PERIOD_YEAR, GL_DATE, PA_DATE, SET_OF_BOOKS_ID — accounting period and ledger context.
• ORG_ID, FUNDS_PROCESS_MODE, ACTUAL_FLAG, SUMMARY_RECORD_FLAG — operating unit, funds-check behavior, and record aggregation flags.

Common Use Cases and Queries

Because the user searched on po_distributions_all, the most frequent access path is tracing a PO distribution to the commitment and project balance it produced. A representative query joins on DOCUMENT_DISTRIBUTION_ID or PDL_PO_DISTRIBUTION_ID:

SELECT c.project_id, c.task_id, c.expenditure_type, d.po_distribution_id, d.po_header_id, c.comm_tot_raw_amt, c.transfer_status_code FROM pa.pa_bc_commitments_all c, po.po_distributions_all d WHERE c.pdl_po_distribution_id = d.po_distribution_id AND c.set_of_books_id = :sob;

Other common patterns include reconciling commitments to GL encumbrances by ENCUMBRANCE_TYPE_ID and SET_OF_BOOKS_ID; reporting remaining commitment by subtracting COMM_RAW_AMT_RELIEVED from COMM_TOT_RAW_AMT; auditing rows that failed to transfer using TRANSFER_STATUS_CODE and COMM_TRANSFER_REJ_REASON; and drilling to requisition-level commitments through PRL_DISTRIBUTION_ID on PO_REQ_DISTRIBUTIONS_ALL. Commitment and budget-versus-actual reports routinely aggregate on PROJECT_ID, TASK_ID, and BUDGET_VERSION_ID.

Related Objects

• PO_DISTRIBUTIONS_ALL — joined via DOCUMENT_DISTRIBUTION_ID and PDL_PO_DISTRIBUTION_ID; the primary purchase-order commitment source.
• PO_HEADERS_ALL — joined via DOCUMENT_HEADER_ID for PO header context.
• PO_REQ_DISTRIBUTIONS_ALL — joined via PRL_DISTRIBUTION_ID for requisition commitments.
• AP_INVOICES_ALL — joined via DOCUMENT_HEADER_ID for invoice commitments.
• AP_INVOICE_DISTRIBUTIONS_ALL — joined via AIL_INVOICE_ID and AIL_DISTRIBUTION_LINE_NUMBER.
• PA_PROJECTS_ALL and PA_TASKS — joined via PROJECT_ID, TASK_ID, and TOP_TASK_ID.
• PA_BUDGET_VERSIONS and PA_BUDGET_LINES — joined via BUDGET_VERSION_ID and BUDGET_LINE_ID.
• PA_COST_DISTRIBUTION_LINES_ALL — joined via PCL_LINE_NUM and PCL_EXPENDITURE_ITEM_ID.
• GL_ENCUMBRANCE_TYPES and GL_SETS_OF_BOOKS_11I — joined via ENCUMBRANCE_TYPE_ID and SET_OF_BOOKS_ID.
• PA_BC_PACKETS — the child table, referencing this table via BC_COMMITMENT_ID, that groups commitment rows prior to transfer.