Search Results transfer_rejection_code




Overview
Explore in AI Chat

Overview

PA_CC_DIST_LINES is a Projects (PA) module view that presents cross-charge distribution lines in Oracle EBS 12.1.1 and 12.2.2. It is a Single-Org view, meaning it filters rows from the underlying multi-org table to the operating unit currently set in the session. The view is not implemented as a standalone database object in every environment; the ETRM metadata indicates "Not implemented in this database," which means it is typically created only where the Projects cross-charge distribution functionality is deployed. In practice, the view is used for reporting, reconciliation, and integration of cross-charge accounting entries generated by the Projects costing engine.

The view is defined over PA_CC_DIST_LINES_ALL, the base table that stores cross-charge distribution lines. It exposes both the accounting code combination identifiers — DR_CODE_COMBINATION_ID (debit) and CR_CODE_COMBINATION_ID (credit) — which are the source of the "cr_code_combination_id" column commonly referenced in queries and reports.

Underlying Base Objects

The ETRM documentation does not enumerate referenced base objects, but the view text shows it selects directly from PA_CC_DIST_LINES_ALL. The WHERE clause applies the operating-unit (ORG_ID) security predicate using USERENV('CLIENT_INFO'), so rows are restricted to the current organization context. Because it selects from the _ALL table rather than a _TL table, no additional language or translation tables are involved. No joins to other tables are present in the documented view text; all columns originate from PA_CC_DIST_LINES_ALL.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling cross-charge accounting entries, verifying debit/credit account combinations for transferred distributions, and checking transfer or rejection status before GL posting. A common pattern joins EXPENDITURE_ITEM_ID back to expenditure items and looks up the credit account.

Sample query:

  • SELECT cc.CC_DIST_LINE_ID, cc.EXPENDITURE_ITEM_ID, cc.AMOUNT, cc.DR_CODE_COMBINATION_ID, cc.CR_CODE_COMBINATION_ID, cc.PA_DATE, cc.GL_DATE, cc.TRANSFER_STATUS_CODE FROM PA_CC_DIST_LINES cc WHERE cc.EXPENDITURE_ITEM_ID = :expenditure_item_id;
  • SELECT cc.CR_CODE_COMBINATION_ID, gcc.concatenated_segments, SUM(cc.AMOUNT) FROM PA_CC_DIST_LINES cc, GL_CODE_COMBINATIONS_KFV gcc WHERE cc.TRANSFER_STATUS_CODE = 'T' AND cc.CR_CODE_COMBINATION_ID = gcc.code_combination_id GROUP BY cc.CR_CODE_COMBINATION_ID, gcc.concatenated_segments;
  • SELECT cc.* FROM PA_CC_DIST_LINES cc WHERE cc.PA_PERIOD_NAME = :period AND cc.REVERSED_FLAG = 'N';

Because ORG_ID filtering is applied through the view, queries automatically respect the session's operating unit; explicit ORG_ID predicates are therefore optional but can improve clarity in multi-org reporting.