Search Results pa_cc_org_relationships




Overview
Explore in AI Chat

Overview

PA_CC_ORG_RELATIONSHIPS is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the relationship between operating units and the attributes that govern cross charge control and processing. Cross charging in Oracle Projects enables one operating unit (the provider) to charge another operating unit (the receiver) for services or expenditures delivered across organizational boundaries. This table defines the rules, approvals, and invoice generation defaults that apply to each provider-to-receiver organizational pair.

Under the heuristic Data Vault classification derived from its foreign key structure, this object is modeled as a link table. It resolves a many-to-many association between provider and receiver organizations and carries descriptive processing attributes alongside that association, which is the classic signature of a link entity rather than a hub or satellite.

Key Information Stored

The table contains 30 documented columns. The most operationally significant are:

There is no separate surrogate key column; the primary key is the natural composite of the two organization identifiers.

Common Use Cases and Queries

Typical uses include validating that a provider-receiver pair is enabled for cross charging, reconciling cross charge setups during implementations, and reporting on the expenditure types and invoice grouping defaults configured per relationship.

A common query retrieves the cross charge setup for a given organization pair:

  • SELECT prvdr_org_id, recvr_org_id, prvdr_allow_cc_flag, cross_charge_code, invoice_grouping_code FROM pa.pa_cc_org_relationships WHERE prvdr_org_id = :p_provider AND recvr_org_id = :p_receiver;

Reporting queries frequently join to HR_ALL_ORGANIZATION_UNITS to resolve organization names, and filter with prvdr_allow_cc_flag = 'Y' to list active cross charge relationships. Reconciliation reports compare configured pairs against actual cross charge transactions to detect missing or misconfigured relationships.

Related Objects

The foreign keys documented for this table establish its principal dependencies:

  • HR_ALL_ORGANIZATION_UNITS — via PRVDR_ORG_ID and RECVR_ORG_ID; supplies organization definitions for both provider and receiver.
  • PA_PROJECTS_ALL — via PRVDR_PROJECT_ID; the provider project used in cross charge processing.
  • PO_VENDOR_SITES_ALL — via VENDOR_SITE_ID; the supplier site used for intercompany invoicing.
  • PA_EXPENDITURE_TYPES — via AP_INV_EXP_TYPE; the expenditure type assigned to Payables invoice transactions.
  • HR_ALL_ORGANIZATION_UNITS — via AP_INV_EXP_ORGANIZATION_ID; the organization referenced for invoice expenditure processing.

Oracle Projects cross charge setup and processing logic, along with intercompany invoicing features in the Projects and Payables modules, consume this table as the authoritative source of provider-to-receiver cross charge control attributes.