Search Results pa_cc_dist_lines_ar

Overview

PA_CC_DIST_LINES_AR is a Projects (PA) module table that stores cross-charge distribution lines in Oracle EBS 12.1.1 and 12.2.2. Cross-charging allows costs incurred in one organization, project, or task to be transferred and shared with another, and each such transfer is represented by a distribution line. The "_AR" suffix indicates that this is an archive or purge-related copy of the corresponding live distribution data held in PA_CC_DIST_LINES_ALL. Rows in this table are typically moved here during a purge or archival process, preserving historical cross-charge distribution detail after the active records have been removed from the operational table.

Mined from its foreign key structure, the table is classified heuristically as a standalone object within the Data Vault modeling convention. Because it functions as an archival counterpart to PA_CC_DIST_LINES_ALL and its relationships are predominantly key lookups to parent entities (expenditure items, distribution lines, and purge batches) rather than defining hubs or links in its own right, treating it as a standalone archival satellite is a reasonable modeling suggestion for reporting or migration purposes. The physical schema is documented for 12.2.2 with the owner PA and 64 columns.

Key Information Stored

The most significant columns fall into identification, accounting, transfer-pricing, and audit categories.

• CC_DIST_LINE_ID — the identifier linking each archived record back to its live cross-charge distribution line in PA_CC_DIST_LINES_ALL. This is the principal surrogate-style key relationship.
• EXPENDITURE_ITEM_ID — identifies the expenditure item that gave rise to the cross-charge distribution.
• PURGE_BATCH_ID — identifies the purge batch under which the row was archived, tying records to PA_PURGE_BATCHES_ALL; PURGE_RELEASE and PURGE_PROJECT_ID provide further purge context.
• PROJECT_ID and TASK_ID — the project and task receiving or providing the cross-charge.
• LINE_NUM, LINE_TYPE, CROSS_CHARGE_CODE, REVERSED_FLAG, LINE_NUM_REVERSED, DIST_LINE_ID_REVERSED — describe the line and any reversal relationship.
• DR_CODE_COMBINATION_ID and CR_CODE_COMBINATION_ID — the debit and credit accounting flexfield combinations.
• AMOUNT, ACCT_CURRENCY_CODE, PA_DATE, GL_DATE, GL_PERIOD_NAME, PA_PERIOD_NAME — accounting amount, currency, and date/period context.
• TRANSFER_STATUS_CODE, TRANSFERRED_DATE, TRANSFER_REJECTION_CODE, GL_BATCH_NAME — track the status of the transfer to General Ledger.
• Transfer-price fields such as BILL_RATE, TP_BASE_AMOUNT, TP_AMT_TYPE_CODE, and the ACCT_/PROJFUNC_/PROJECT_ rate, price, and currency columns support cross-charge pricing.
• ORG_ID and the standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — provide operating unit and audit context.
• ACCT_EVENT_ID and ACCT_SOURCE_CODE — link the row to its Subledger Accounting event.

Common Use Cases and Queries

The table is principally queried for audit, reconciliation, and investigative reporting where live cross-charge records no longer exist. A common pattern is to join archived lines to their original distributions using CC_DIST_LINE_ID, or to gather all lines archived under a given purge event.

• Reporting all archived cross-charge lines for a purge batch: SELECT * FROM pa.pa_cc_dist_lines_ar WHERE purge_batch_id = :batch_id;
• Reconciling archived lines to live distributions: SELECT ar.* FROM pa.pa_cc_dist_lines_ar ar JOIN pa.pa_cc_dist_lines_all d ON ar.cc_dist_line_id = d.cc_dist_line_id;
• Auditing transfer pricing and rejection activity: filter on TRANSFER_STATUS_CODE, TRANSFER_REJECTION_CODE, TRANSFERED_DATE, and TP_AMT_TYPE_CODE.
• Accounting analysis by project, task, or GL period for purged projects, using PROJECT_ID, TASK_ID, GL_PERIOD_NAME, and DR_CODE_COMBINATION_ID / CR_CODE_COMBINATION_ID.

Related Objects

The documented foreign keys establish the primary relationships to parent and reference entities.

• PA_CC_DIST_LINES_ALL — joined via CC_DIST_LINE_ID; the live counterpart of the archived records.
• PA_EXPENDITURE_ITEMS_ALL — joined via EXPENDITURE_ITEM_ID; the source expenditure item.
• PA_PURGE_BATCHES_ALL — joined via PURGE_BATCH_ID; defines the archive/purge run.
• PA_PROJECTS_ALL and PA_TASKS — referenced through PROJECT_ID and TASK_ID for project and task detail.
• GL_CODE_COMBINATIONS — referenced through DR_CODE_COMBINATION_ID and CR_CODE_COMBINATION_ID for accounting flexfield descriptions.
• XLA events and accounting tables — associated through ACCT_EVENT_ID for subledger accounting reporting.