Search Results resource_source_id




Overview
Explore in AI Chat

Overview

PA_PROJECT_PARTIES_ALL_V is a Projects (PA) module view that resolves the relationship between project-level resource assignments and their corresponding Trading Community Architecture (TCA) party records. Its principal role is to translate the internal resource identifier carried on a project assignment (RESOURCE_SOURCE_ID, typically a PERSON_ID from the HR/per-person source) into the HZ_PARTIES.PARTY_ID and PARTY_NAME values used throughout Oracle E-Business Suite for party-centric reporting and integration.

Because project staffing records in PA reference resources through the resource source identifier, downstream consumers — receivables, CRM, grants, and custom reporting layers — often need the TCA party identifier instead. This view performs that translation directly, joining the project parties data to HZ_PARTIES on a derived original-system reference. It is therefore a convenience view for reporting and integration rather than a transactional base object. Per the ETRM metadata, the view is not documented as implemented in this database, and no base objects are formally listed, so its column contract is best confirmed against the live data dictionary in the target instance.

Underlying Base Objects

The documented view text is:

Accordingly, the view is defined over two documented sources: the base view PA_PROJECT_PARTIES_V and the TCA table HZ_PARTIES. The join is not a direct key relationship; it is constructed by concatenating the literal prefix 'PER:' with the RESOURCE_SOURCE_ID and matching that composite string against HZ_PARTIES.ORIG_SYSTEM_REFERENCE. In TCA, ORIG_SYSTEM_REFERENCE identifies the originating application record for a party — here, a person in the PER (Human Resources) source. This construction means the view only returns rows where the party was created from a matching person source, and the DISTINCT clause eliminates duplicate projections caused by the many-to-many potential of the join. The ETRM metadata lists no further base objects, so no additional PA tables such as PA_PROJECT_PARTIES or PA_RESOURCES are documented as participating.

Key Columns

  • PARTY_ID — The unique TCA party identifier for the person associated with the project resource. This is the canonical party key used across HZ tables and downstream applications.
  • PARTY_NAME — The party name as stored in HZ_PARTIES, typically the person's display name.
  • PROJECT_ID — The project to which the resource/party assignment applies; the primary link back into the PA project hierarchy.
  • RESOURCE_SOURCE_ID — The source-system identifier for the assigned resource, resolved as a person ID in this view. This is the column users most often search for when tracing staffing records.

Common Use Cases and Queries

Typical uses include listing project team members with their TCA party identity, reconciling PA resource assignments to party records, and feeding project-party data into integrations that require PARTY_ID rather than a resource identifier.

Example — project parties for a specific project:

  • SELECT project_id, party_id, party_name, resource_source_id FROM pa_project_parties_all_v WHERE project_id = :project_id;

Example — resolve a known resource to its party:

  • SELECT party_id, party_name, project_id FROM pa_project_parties_all_v WHERE resource_source_id = :resource_source_id;

Because the join depends on the 'PER:'||RESOURCE_SOURCE_ID format of ORIG_SYSTEM_REFERENCE, confirm that the instance uses this convention and that the target party records originated from the PER source before relying on the view for reconciliation.