Search Results pa_cross_chargeable_ou_v




Overview
Explore in AI Chat

Overview

PA_CROSS_CHARGEABLE_OU_V is a Projects (PA) module view owned by the APPS schema. It exposes the set of operating units between which cross-charging is permitted from the perspective of the current operating unit. In Oracle EBS cross-charging terminology, a provider operating unit (the organization delivering a service or incurring an expense) and a receiver operating unit (the organization that ultimately bears the cost) are evaluated against a series of eligibility rules. This view encapsulates the outcome of those rules, offering a pre-joined, validated list of provider/receiver operating unit pairs that satisfy the cross-charge relationship defined in the underlying Project Accounting organization relationship setup.

The view plays an important role for reporting, data extraction, and integration logic that must determine whether transactions can be cross-charged between two operating units. Rather than re-implementing the intricate eligibility conditions in every report or interface, developers and functional users can query PA_CROSS_CHARGEABLE_OU_V to obtain the results of Oracle's own validation logic. This view is therefore most valuable where cross-charge eligibility drives downstream processing, such as cross-charge transaction generation, costing, and reconciliation queries.

Underlying Base Objects

The documented base objects referenced by this view are:

  • PA_CC_ORG_RELATIONSHIPS (SYNONYM) — the cross-charge organization relationships definition, keyed by provider and receiver organization IDs and carrying the setup flags that determine whether cross-charging is allowed.
  • PA_CROSS_BUSINESS_GRP (PACKAGE) — the package supplying cross-business-group comparison logic used in the eligibility evaluation.
  • PA_CROSS_CHARGEABLE_OU_BASE_V (VIEW) — the primary source of provider/receiver pairs, which PA_CROSS_CHARGEABLE_OU_V filters and completes via an outer join to the organization relationships.

The view is defined as a SELECT from PA_CC_ORG_RELATIONSHIPS (aliased CO) and PA_CROSS_CHARGEABLE_OU_BASE_V (aliased PCOUB). The join on provider and receiver organization IDs is an outer join on the CO side (the "(+)" notation), so that base rows are retained even where an explicit organization-relationship setup record does not exist. The WHERE clause then applies the cross-charge eligibility predicates. Notably, the view treats the same operating unit on both sides as always cross-chargeable, and otherwise evaluates the legal entity relationship, the PROVIDER_CC_ALLOW_IU_FLAG, and the CROSS_CHARGE_CODE values ('I', 'N', and default handling) to decide inclusion.

Key Columns

Common Use Cases and Queries

Typical uses include restricting a report of cross-chargeable expense or labor transactions to valid provider/receiver pairs, populating a list of values for cross-charge processing, and validating an interface record before it is submitted. A representative query listing all cross-chargeable receivers for a given provider operating unit is shown below.

  • SELECT prVdr_org_id, recvr_org_id, set_of_books_id FROM pa_cross_chargeable_ou_v WHERE prvdr_org_id = :p_provider_org_id;
  • SELECT prvdr_org_id, recvr_org_id, prvdr_legal_entity_id, recvr_legal_entity_id FROM pa_cross_chargeable_ou_v WHERE prvdr_legal_entity_id <> recvr_legal_entity_id;
  • SELECT DISTINCT recvr_org_id FROM pa_cross_chargeable_ou_v WHERE prvdr_org_id = :p_provider_org_id AND pa_period_type = :p_period_type;

Because the view resolves cross-charge eligibility using the documented flags and legal entity relationships, it is the preferred access path for any query that must mirror Oracle Projects cross-charge validation logic in a consistent, supported manner.