Search Results prc_assignment_id




Overview
Explore in AI Chat

Overview

The PA_MC_CC_DIST_LINES_ALL table in the Oracle E-Business Suite Projects (PA) module stores information about cross charge distributions of expenditure items for each reporting set of books. In Oracle EBS 12.1.1 and 12.2.2, this table participates in the multi-organization cross charge accounting flow, where labor and non-labor costs incurred in one organization are redistributed — or "cross charged" — to the organization that ultimately bears the cost. The "_ALL" suffix denotes that the table is partitioned by operating unit via the Multi-Org security model, so queries must respect MOAC (Multi-Org Access Control) policies.

The table carries a heuristic Data Vault classification of link, mined from its foreign key structure. In Data Vault modeling terms, it functions as a transactional link table: it records the association between a cross charge distribution line and the reporting set of books, with descriptive and status attributes layered on top. Rows originate when the Cross Charge Distribution process is run for a reporting set of books, and they drive downstream transfer to General Ledger through Subledger Accounting (XLA).

Key Information Stored

The composite primary key PA_MC_CC_DIST_LINES_PK comprises three columns: SET_OF_BOOKS_ID, PRC_ASSIGNMENT_ID, and CC_DIST_LINE_ID. Note that the user's search term, PRC_ASSIGNMENT_ID, is a component of this surrogate primary key, identifying the specific cost distribution or cross charge assignment that generated the distribution line. SET_OF_BOOKS_ID anchors the row to the reporting ledger via the GL_SETS_OF_BOOKS_11I foreign key. CC_DIST_LINE_ID links to the underlying PA_CC_DIST_LINES_ALL row, and EXPENDITURE_ITEM_ID ties the line back to the source PA_EXPENDITURE_ITEMS_ALL transaction.

The ETRM metadata documents two unique indexes that serve as business-key candidates. PA_MC_CC_DIST_LINES_U1 covers (CC_DIST_LINE_ID, SET_OF_BOOKS_ID), while PA_MC_CC_DIST_LINES_U2 covers (EXPENDITURE_ITEM_ID, LINE_NUM, SET_OF_BOOKS_ID, LINE_TYPE), enforcing uniqueness per expenditure item, line number, ledger, and line type. Additional columns capture accounting detail: ACCT_CURRENCY_CODE and ACCT_TP_RATE_TYPE (linked to FND_CURRENCIES and GL_DAILY_CONVERSION_TYPES respectively), together with ACCT_TP_RATE_DATE and ACCT_TP_EXCHANGE_RATE, hold the currency and conversion information used to value the distribution. AMOUNT carries the distributed value, LINE_NUM and LINE_TYPE classify the line, and TRANSFER_STATUS_CODE, TRANSFERRED_DATE, TRANSFER_REJECTION_CODE, and GL_BATCH_NAME track the posting lifecycle. PROGRAM_ID and REQUEST_ID capture the concurrent program context, and XLA_MIGRATED_FLAG supports subledger accounting migration.

Common Use Cases and Queries

Typical reporting scenarios include reconciling cross charge distributions to General Ledger, auditing lines that failed transfer, and tracing the reporting set of books for a given assignment. Because PRC_ASSIGNMENT_ID participates in the primary key, it is frequently used as a filter to isolate all distributions produced by a specific cross charge assignment.

  • Distributions for an assignment across ledgers: SELECT set_of_books_id, cc_dist_line_id, amount, transfer_status_code FROM pa_mc_cc_dist_lines_all WHERE prc_assignment_id = :prc_assignment_id;
  • Unposted or rejected lines: SELECT * FROM pa_mc_cc_dist_lines_all WHERE transfer_status_code = 'R' OR transfer_rejection_code IS NOT NULL;
  • Reconciliation by expenditure item: join to PA_EXPENDITURE_ITEMS_ALL on expenditure_item_id to compare source and distributed amounts.

Related Objects

The following objects are most significant in relation to this table, based on the documented foreign key and primary key relationships:

  • PA_CC_DIST_LINES_ALL — joined on CC_DIST_LINE_ID; the parent cross charge distribution line.
  • PA_EXPENDITURE_ITEMS_ALL — joined on EXPENDITURE_ITEM_ID; the originating expenditure item.
  • GL_SETS_OF_BOOKS_11I — joined on SET_OF_BOOKS_ID; the reporting set of books.
  • FND_CURRENCIES — joined on ACCT_CURRENCY_CODE for currency validation.
  • GL_DAILY_CONVERSION_TYPES — joined on ACCT_TP_RATE_TYPE for conversion rate definitions.

These relationships confirm the table's role as a distribution-level link between expenditure, cross charge, and ledger entities within the Oracle Projects cost accounting model.