Search Results cc_cross_charge_code




Overview
Explore in AI Chat

Overview

PA_XLA_CROSSCHARGE_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Projects (PA) module. Its status is VALID in ETRM 12.2.2, and it is deployed in both the 12.1.1 and 12.2.2 release streams. The view presents cross-charge expenditure data in a denormalized, human-readable form, joining low-level expenditure item records to their project, task, organization, expenditure type, and lookup descriptions. The name prefix "XLA" reflects the fact that this view is intended to support the Oracle Subledger Accounting (XLA) and Projects accounting workflows, where cross-charged expenditures between provider and receiver organizations must be resolved, reviewed, or reconciled. Rather than requiring callers to reconstruct descriptive information from multiple satellite tables, PA_XLA_CROSSCHARGE_V exposes a flattened projection that is convenient for reporting, integration extracts, and diagnostic SQL. It is a read-only view; no DML is performed against it.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms except PA_LOOKUPS, which is itself a view:

The view joins PA_EXPENDITURE_ITEMS_ALL to PA_PROJECTS_ALL and PA_TASKS on project_id (and task_id for tasks), to PA_EXPENDITURES_ALL on expenditure_id, to the expending organization via NVL(OVERRIDE_TO_ORGANIZATION_ID, INCURRED_BY_ORGANIZATION_ID), to provider and receiver organizations via CC_PRVDR_ORGANIZATION_ID and CC_RECVR_ORGANIZATION_ID, to PA_EXPENDITURE_TYPES on expenditure_type, to PA_SYSTEM_LINKAGES on system_linkage_function, and to PA_LOOKUPS on CC_CROSS_CHARGE_CODE with lookup_type = 'CC_CROSS_CHARGE_CODE'. All joins are equality (or NVL) predicates with no outer joins, so an expenditure item is returned only when every participant row is present.

Key Columns

The view exposes the following documented columns:

Common Use Cases and Queries

Typical scenarios include reviewing cross-charge transactions between internal organizations, validating cost transfers prior to period close, feeding downstream XLA accounting extracts, and diagnosing missing or misclassified cross-charge items. A straightforward query to retrieve all cross-charged expenditure for a given project number follows:

SELECT expenditure_item_id, project_name_num_concat, task_name_num_concat, expenditure_type, expenditure_category, expenditure_item_date, provider_organization, receiver_organization, cross_charge_code FROM apps.pa_xla_crosscharge_v WHERE project_name_num_concat LIKE '%:project%';

Filtering by date range and cross-charge code supports period-end reconciliation:

SELECT expenditure_item_id, project_name_num_concat, cross_charge_code, expenditure_item_date FROM apps.pa_xla_crosscharge_v WHERE expenditure_item_date BETWEEN :start_date AND :end_date AND cross_charge_code = :cc_code;

Because the view is read-only and joins several large tables, best practice is to restrict queries with PROJECT_ID- or date-derived predicates where possible, and to avoid selecting all rows without filters on production data volumes.