Results for “pa_cost_dist_lines_v”

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

Overview

The PA_COST_DIST_LINES_V view is an Oracle E-Business Suite (EBS) database object owned by the APPS schema and registered as a VALID view under the PA – Projects product. It exposes the distribution lines generated by the Oracle Projects Cost Distribution process, which is the mechanism by which eligible project expenditures are selected, grouped into distribution lines, costed, and ultimately transferred to Oracle General Ledger. In EBS 12.1.1 and 12.2.2, this view serves as the principal reporting and integration surface for examining the details of cost distribution activity without querying the underlying transaction table directly.

Because the view is a read-only projection of the base distribution lines, it is widely used in custom reports, Oracle Business Intelligence Publisher (BI Publisher) data models, Project Accounting diagnostics, and interfaces that must validate or reconcile distribution data prior to GL transfer, burdening, or cross-charge processing.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, PA_COST_DIST_LINES_V is defined over the base object PA_COST_DISTRIBUTION_LINES_ALL, accessed through a synonym. In Oracle EBS 12.1.1 and 12.2.2 this table is the multi-organization (ORG_ID-enabled) source of cost distribution line records. The view text confirms a straightforward projection: each column of the view, prefixed CDL., maps one-to-one to a corresponding column such as EXPENDITURE_ITEM_ID, LINE_NUM, AMOUNT, and PROJECT_ID in PA_COST_DISTRIBUTION_LINES_ALL. No aggregation, join, or filtering is applied in the view definition itself; filtering by organization, project, or transfer status must therefore be performed by the calling query.

Key Columns

• EXPENDITURE_ITEM_ID – Links each distribution line back to the originating expenditure item; the primary join key to PA_EXPENDITURE_ITEMS_ALL.
• LINE_NUM, LINE_TYPE, AMOUNT, QUANTITY – Identify and quantify each distribution line, including RAW, BURDENED, and change line types.
• DR_CODE_COMBINATION_ID / CR_CODE_COMBINATION_ID / CODE_COMBINATION_ID – General Ledger chart-of-accounts combinations for the debit, credit, and net accounting entries.
• TRANSFER_STATUS_CODE, TRANSFERRED_DATE, TRANSFER_REJECTION_REASON, GL_DATE, GL_PERIOD_NAME – Govern and record the transfer of the line to General Ledger, including any rejection diagnostics.
• PROJECT_ID, TASK_ID, PA_DATE, PA_PERIOD_NAME – Project and task context together with the Project Accounting date and period.
• Denominated, Project, and Accounting Currency Columns – DENOM_RAW_COST, PROJECT_RAW_COST, ACCT_RAW_COST and their burdened counterparts, with associated rate types, rate dates, and exchange rates, support multi-currency analysis.
• BURDENED_COST, BURDEN_SUM_SOURCE_RUN_ID – Burden amounts and the burden summarization run that produced them.
• ENCUMBRANCE_AMOUNT, ENCUMBRANCE_TYPE_ID, LIQUIDATE_ENCUM_FLAG, BUDGET_CCID – Encumbrance accounting attributes associated with the distribution line.
• ACCUMULATED_FLAG, RESOURCE_ACCUMULATED_FLAG, UTIL_SUMMARIZED_FLAG, PJI_SUMMARIZED_FLAG – Flags indicating whether the line has been accumulated into summary balances.
• ACCT_EVENT_ID – Exposes the subledger accounting event identifier associated with the accounting generated for the line, supporting linkage to Subledger Accounting (SLA) data.

Common Use Cases and Queries

Typical scenarios include validating distributions prior to GL transfer, reconciling rejected lines, tracing expenditures into GL, and driving custom subledger reports. The following examples assume execution in the APPS schema.

• List un-transferred lines for a project – SELECT line_num, amount, dr_code_combination_id, transfer_status_code FROM pa_cost_dist_lines_v WHERE project_id = :project_id AND transfer_status_code <> 'Y';
• Trace transfers to GL by period – SELECT expenditure_item_id, gl_period_name, acct_raw_cost, acct_burdened_cost FROM pa_cost_dist_lines_v WHERE pa_period_name = :period AND transferred_date IS NOT NULL;
• Analyze rejections – SELECT line_num, expenditure_item_id, transfer_rejection_reason FROM pa_cost_dist_lines_v WHERE transfer_rejection_reason IS NOT NULL;
• Locate SLA events – SELECT acct_event_id, project_id, gl_date FROM pa_cost_dist_lines_v WHERE acct_event_id = :event_id;

Because the view is unfiltered, always constrain queries by ORG_ID, project, period, or transfer status to avoid full-table scans across all organizations.