Search Results pa_cross_chargeable_ou_base_v




Overview
Explore in AI Chat

Overview

PA_CROSS_CHARGEABLE_OU_BASE_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose the set of operating units that are cross-chargeable from the current operating unit. In the Oracle Projects cross-charging model, a provider operating unit can borrow or transfer expenditures to a receiver operating unit only when the pair satisfies the implementation rules configured for both organizations. This view materializes that provider-to-receiver relationship as a flat, queryable list, which makes it suitable for reporting, validation logic, and integration routines that must determine whether a given organizational combination is permitted before a cross-charge transaction is created.

The view is part of the internal supporting layer for the Oracle Projects cross-charge setup. Rather than duplicating the setup screens, it consolidates the enabled operating units, their business groups, ledgers, project and expenditure organization structures, and their respective cross-charge flags into a single relational shape. Because the view is stateless and derived from setup tables, it always reflects the current configuration of PA implementations and organization information at query time.

Underlying Base Objects

The documented base objects referenced by the view are:

  • PA_IMPLEMENTATIONS (synonym) — the provider-side implementation record, supplying the primary ORG_ID and BUSINESS_GROUP_ID.
  • PA_IMPLEMENTATIONS_ALL (synonym) — the organization-level implementation record for each operating unit, supplying ledger, period type, organization structure identifiers, and the receiver-side cross-charge flag. It is aliased IALL and is joined to the provider implementation on business group.
  • HR_ORGANIZATION_INFORMATION (synonym) — joined twice with outer joins (aliased PLE for the provider and RLE for the receiver) using the context 'OPERATING UNIT INFORMATION'. These joins retrieve ORG_INFORMATION2, which is defaulted to '-99' where no row exists, and is exposed as the provider and receiver legal entity identifiers.
  • PA_CROSS_BUSINESS_GRP (package) — a packaged function, ISCROSSBGPROFILE, is called inside the WHERE clause to determine whether cross-business-group cross-charging is enabled. When the profile returns 'N', the provider and receiver business groups must match; when it returns 'Y', the business group equality predicate is bypassed.

The join structure therefore enforces two independent conditions: the business group compatibility rule expressed through the package call, and the operating unit information lookups performed through the HR organization information joins.

Key Columns

The view exposes nineteen columns, which can be grouped as follows:

Common Use Cases and Queries

Typical uses include reporting on valid cross-charge combinations, validating source operating units during cross-charge batch processing, and driving integrations that must respect configured cross-charge relationships. A representative query lists all cross-chargeable receivers for a given provider:

  • SELECT prvdr_org_id, recvr_org_id, pr vdr_cc_allow_iu_flag, recvr_cc_allow_iu_flag FROM pa_cross_chargeable_ou_base_v WHERE prvdr_org_id = :provider_org_id;
  • Reporting inventory of enabled combinations: SELECT prvdr_org_id, recvr_org_id, set_of_books_id, pa_period_type FROM pa_cross_chargeable_ou_base_v ORDER BY prvdr_org_id, recvr_org_id;
  • Verifying a specific provider/receiver pair before processing: SELECT COUNT(*) FROM pa_cross_chargeable_ou_base_v WHERE prvdr_org_id = :p AND recvr_org_id = :r AND recvr_cc_allow_iu_flag = 'Y';

Because the view relies on the PA_CROSS_BUSINESS_GRP package profile and current PA implementation rows, callers should treat the result as configuration-dependent. Oracle Proprietary, Confidential Information — Legal Notices apply to all use of this object.