Search Results provider_project_id




Overview
Explore in AI Chat

Overview

APPS.PA_PRVDR_CC_ORG_REL_V is a supplementary view owned by the APPS schema and registered under the FND Design Data name PA.PA_PRVDR_CC_ORG_REL_V. Oracle classifies it as a "supplementary view used to simplify forms coding," meaning it exists primarily to flatten and denormalize data consumed by Oracle Projects cross-charging forms rather than to serve as a formally supported integration interface. Oracle's standard warning applies: querying or altering data through this view is not recommended, because its column list and join logic may change dramatically between minor or major releases.

Functionally, the view presents provider and receiver organization relationships used in cross-charge processing, enriched with supplier, supplier site, legal entity, operating unit, and invoice expenditure information. Because it exposes both PRVDR_ORG_ID and RECVR_ORG_ID together with PROVIDER_PROJECT_ID, it answers the question of which provider organization is associated with which receiving organization for a given project and cross-charge arrangement. The view status is VALID in both 12.1.1 and 12.2.2, and the object type is VIEW, so no physical storage is associated with it.

Underlying Base Objects

The documented base objects reveal the view's composition. PA_CC_ORG_RELATIONSHIPS (synonym) supplies the core provider-to-receiver organization relationship and is the principal driver of the view. HR_ORG_UNITS_NO_JOIN and HR_ALL_ORGANIZATION_UNITS_TL (synonym) provide organization identifiers and translated organization names, while HR_OPERATING_UNITS supplies operating unit context. HR_SECURITY, HR_GENERAL, and FND_GLOBAL (package) enforce organization-level and session-level security, so rows returned are filtered according to the responsibility and user context in which the query executes.

Supplier data is drawn from PO_VENDORS (view) and PO_VENDOR_SITES_ALL (view), supplying SUPPLIER_NAME, SUPPLIER_ID, SUPPLIER_SITE_NAME, and SUPPLIER_SITE_ID. XLE_ENTITY_PROFILES (synonym) provides legal entity identification and naming for PRVDR_LEGAL_ENTITY_ID and PRVDR_LEGAL_ENTITY_NAME. PA_IMPLEMENTATIONS_ALL supplies implementation-level configuration, and HR_OPERATING_UNITS supports the AP invoice expenditure organization columns. The presence of HR_SECURITY and FND_GLOBAL means the view is not a simple three-table join; it is a security-aware construct intended for form runtime.

Key Columns

The columns most relevant to the user's search term, provider_project_id, sit alongside the cross-charge configuration columns. PROVIDER_PROJECT_ID (NUMBER) identifies the provider project associated with the relationship, and PRVDR_ORG_ID and RECVR_ORG_ID identify the two participating organizations. PRVDR_ORG_NAME and PRVDR_LEGAL_ENTITY_NAME provide descriptive text, while PRVDR_LEGAL_ENTITY_ID carries a VARCHAR2(150) datatype, an unusual choice that reflects the view's denormalized purpose.

Common Use Cases and Queries

Typical usage is diagnostic rather than transactional: confirming which provider project and cross-charge code are associated with a provider/receiver organization pair, or verifying supplier and invoice expenditure setup before a cross-charge run. A simple query retrieving the provider project and related configuration is shown below.

SELECT prvdr_org_id, prvdr_org_name, recvr_org_id, provider_project_id, cross_charge_code, prvdr_allow_cc_flag, invoice_grouping_code FROM apps.pa_prvdr_cc_org_rel_v WHERE prvdr_org_id = :p_org_id;

Because HR security is applied through HR_SECURITY and FND_GLOBAL, results depend on the operating unit and responsibility under which the query runs. Developers should apply the APPS schema prefix, avoid DML against the view, and treat results as informational only, consistent with Oracle's guidance that the view may change without notice.