Search Results provider_project_name

Overview

PA_RECVR_CC_ORG_REL_V is a Projects (PA) module view owned by the APPS schema. It exposes cross-charge organization relationship data configured between a provider organization and a receiver organization, enriched with the descriptive names of the operating units, legal entities, and provider projects involved. The view is used primarily for reporting, validation, and integration of inter-organization cross-charge setups, including the invoicing attributes that govern how cross-charge transactions flow into Payables.

For users searching on invoice_grouping_code, this view is the principal reference: it projects the INVOICE_GROUPING_CODE column from the underlying relationship table, allowing cross-charge invoice grouping behavior to be reported alongside the organization pair it applies to. The view also joins to HR_OPERATING_UNITS and XLE_ENTITY_PROFILES so that receiver operating unit names and legal entity names are available without additional lookups, and it joins to PA_PROJECTS_ALL to resolve the provider project name.

Underlying Base Objects

The view is defined over four documented objects:

• PA_CC_ORG_RELATIONSHIPS (synonym, aliased E) — the driving table holding the cross-charge organization relationship rows, including the invoice grouping code and cross-charge code attributes.
• HR_OPERATING_UNITS (view, aliased H) — supplies the receiver operating unit name, business group, and the default legal context identifier.
• XLE_ENTITY_PROFILES (synonym, aliased XEP) — supplies the legal entity name corresponding to the receiver's default legal context.
• PA_PROJECTS_ALL (synonym, aliased P) — supplies the provider project segment1 value as the provider project name; joined with an outer (+) so relationships without an assigned provider project are still returned.

The join conditions are: E.PRVDR_PROJECT_ID = P.PROJECT_ID(+), E.RECVR_ORG_ID = H.ORGANIZATION_ID, and H.DEFAULT_LEGAL_CONTEXT_ID = XEP.LEGAL_ENTITY_ID. The ROWID of the base relationship row is exposed as ROW_ID.

Key Columns

• ROW_ID — the ROWID of the underlying PA_CC_ORG_RELATIONSHIPS row, uniquely identifying the relationship.
• RECVR_ORG_ID / PRVDR_ORG_ID — the receiver and provider organization identifiers defining the cross-charge relationship.
• RECVR_ORG_NAME — the receiver operating unit name from HR_OPERATING_UNITS.
• RECVR_LEGAL_ENTITY_ID / RECVR_LEGAL_ENTITY_NAME — the receiver's legal entity identifier and corresponding name.
• PRVDR_ALLOW_CC_FLAG — indicates whether the provider permits cross-charging for this relationship.
• CROSS_CHARGE_CODE — the cross-charge arrangement code associated with the relationship.
• PROVIDER_PROJECT_ID / PROVIDER_PROJECT_NAME — the provider project and its segment1 name, where assigned.
• INVOICE_GROUPING_CODE — the code controlling how cross-charge invoices are grouped when generated in Payables; central to cross-charge invoicing configuration.
• AP_INV_EXP_TYPE, AP_INV_EXP_ORGANIZATION_ID, VENDOR_SITE_ID (SUPPLIER_SITE_ID) — Payables invoice defaults for expenditure type, expenditure organization, and supplier site.
• RECVR_BUSINESS_GROUP_ID — the receiver's business group identifier.
• Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard descriptive flexfield columns for the relationship.

Common Use Cases and Queries

The view is commonly queried to audit cross-charge relationships for a given organization pair, to confirm the invoice grouping assignment before generating cross-charge invoices, and to join cross-charge setup data into custom reports or extracts.

SELECT recvr_org_name,
       recvr_legal_entity_name,
       provider_project_name,
       cross_charge_code,
       invoice_grouping_code,
       prvdr_allow_cc_flag,
       ap_inv_exp_type,
       vendor_site_id
  FROM apps.pa_recvr_cc_org_rel_v
 WHERE recvr_org_id = :p_receiver_org_id;

To locate all relationships configured with a specific grouping behavior:

SELECT recvr_org_id, prvdr_org_id, invoice_grouping_code
  FROM apps.pa_recvr_cc_org_rel_v
 WHERE invoice_grouping_code IS NOT NULL
 ORDER BY recvr_org_id, prvdr_org_id;

Because the view joins HR_OPERATING_UNITS to XLE_ENTITY_PROFILES on the default legal context, any receiver operating unit without a valid default legal context mapping will not appear in the result set. Queries intended for completeness should therefore account for that inner-join restriction, while the outer join to PA_PROJECTS_ALL ensures relationships without a provider project remain visible.