Search Results proj_start_org_id




Overview
Explore in AI Chat

Overview

APPS.PA_CROSS_CHARGEABLE_OU_BASE_V is an Oracle EBS internal view owned by the APPS schema in the Projects (PA) module. It is a foundational, base-level view that identifies which operating units can participate in cross-charge transactions — that is, which provider and receiver operating unit combinations are permitted to exchange project costs and expenditures across legal entities, sets of books and business groups. The view is marked with the standard Oracle warning that it is designated for Oracle Internal Use Only, meaning it is not supported for direct customer access except through standard Oracle Applications programs. In release 12.1.1 and 12.2.2 it serves as the internal data source consumed by the public-facing view PA_CROSS_CHARGEABLE_OU_V, which surfaces the derived cross-charge eligibility to application logic and reporting.

Underlying Base Objects

The view is defined over four documented objects. HR_ORGANIZATION_INFORMATION provides the organization classification and organization structure version attributes used to resolve provider and receiver operating units. PA_IMPLEMENTATIONS and PA_IMPLEMENTATIONS_ALL supply the implementation-level operating unit, business group and set of books context for each provider and receiver. The PA_CROSS_BUSINESS_GRP package encapsulates the business rules that determine whether cross-charging between two organizations, business groups or legal entities is allowed. The view therefore acts as a join and de-normalization layer: it combines organizational hierarchy data with implementation parameters and applies the PA_CROSS_BUSINESS_GRP logic to produce a row-level matrix of allowable cross-charge operating unit pairs. PA_CROSS_CHARGEABLE_OU_V is the only documented dependent object, inheriting and filtering the base rows for broader consumption.

Key Columns

Common Use Cases and Queries

This view is typically queried to diagnose cross-charge configuration issues — for example, when a cross-charge transaction fails because the provider/receiver operating unit combination is not permitted. A representative query echoing the column list is:

SELECT PRVDR_ORG_ID, RECVR_ORG_ID, BUSINESS_GROUP_ID, SET_OF_BOOKS_ID,
       PROJ_START_ORG_ID, EXP_START_ORG_ID, START_ORGANIZATION_ID,
       PRVDR_CC_ALLOW_IU_FLAG, RECVR_CC_ALLOW_IU_FLAG
FROM   APPS.PA_CROSS_CHARGEABLE_OU_BASE_V
WHERE  PRVDR_ORG_ID = :p_provider_org
AND    RECVR_ORG_ID = :p_receiver_org;

Because the object carries the Oracle Internal Use Only restriction, production queries should reference PA_CROSS_CHARGEABLE_OU_V or call standard Oracle APIs rather than depend on the base view directly.