Results for “pv_resource_info_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.PV_RESOURCE_INFO_V view is a Partner Management (PV) reporting and integration object shipped with Oracle E-Business Suite 12.1.1 and 12.2.2. It is a denormalized, read-only view that correlates a JTF resource record (a resource, often a partner contact or user, defined in the JTF Resource Manager schema) with its associated Oracle Trading Community Architecture (TCA) party and the directional relationship linking that party to a partner organization. In effect, the view answers the question: "Given a resource and its contact record, which TCA party is it, and which partner party is it related to?" Because the view joins the resource extensions table to the TCA relationship and party tables, it is commonly used in Partner Management dashboards, channel/partner reporting, and downstream integrations that need a flat resource-to-partner mapping rather than navigating the TCA relationships model directly. The view is owned by the APPS schema and has a status of VALID. It is documented in ETRM 12.2.2 and is also present in 12.1.1, where the same underlying TCA/JTF base objects apply.

Underlying Base Objects

The view is defined over four base objects, all referenced through APPS synonyms in the documented metadata:

• JTF_RS_RESOURCE_EXTNS — the JTF Resource Manager extensions table, aliased A. Supplies the resource, user, contact, and category identifiers, and is the driving table (restricted by CONTACT_ID IS NOT NULL).
• HZ_ORG_CONTACTS — the TCA organization contacts table, aliased B. Links the resource contact to a party relationship.
• HZ_RELATIONSHIPS — the TCA relationships table, aliased C. Provides the party-to-party relationship and the relationship code.
• HZ_PARTIES — used twice (aliases D and E) to resolve the subject party and the object party of the relationship into party IDs and party names.

The join path flows from JTF_RS_RESOURCE_EXTNS.CONTACT_ID to HZ_ORG_CONTACTS.ORG_CONTACT_ID, then to HZ_RELATIONSHIPS via PARTY_RELATIONSHIP_ID, and finally to the two HZ_PARTIES instances via SUBJECT_ID and OBJECT_ID. The view is constrained to relationships where both endpoints are TCA parties (SUBJECT_TABLE_NAME and OBJECT_TABLE_NAME equal 'HZ_PARTIES') and where the relationship is non-directional in the forward sense (DIRECTIONAL_FLAG = 'F').

Key Columns

The view exposes the following columns (documented names shown with the underlying select expression):

• RSC_USER_ID (A.USER_ID) — the FND user identifier associated with the resource.
• RSC_RESOURCE_ID (A.RESOURCE_ID) — the JTF resource identifier.
• RSC_CONTACT_ID (A.CONTACT_ID) — the TCA organization contact identifier.
• RSC_CATEGORY_ID (A.CATEGORY) — the resource category classification.
• RSC_RELATIONSHIP (C.RELATIONSHIP_CODE) — the relationship code describing how the resource party relates to the partner party.
• RSC_PARTY_ID / RSC_PARTY_NAME (D.PARTY_ID, D.PARTY_NAME) — the TCA party (subject) representing the resource.
• PARTNER_PARTY_ID / PARTNER_PARTY_NAME (E.PARTY_ID, E.PARTY_NAME) — the related partner party (object) in the relationship.

Common Use Cases and Queries

Typical scenarios include listing resources by their associated partner party, reporting partner contacts with their relationship codes, and feeding partner data into integrations that expect a flat party mapping.

• Partner-to-resource roster by partner party name.
• Resource lookup by user or resource identifier.
• Relationship-code filtering for specific partner associations.

SELECT rsc_user_id,
       rsc_resource_id,
       rsc_party_name,
       partner_party_id,
       partner_party_name,
       rsc_relationship
  FROM apps.pv_resource_info_v
 WHERE partner_party_name LIKE :partner_name
 ORDER BY partner_party_name;

SELECT rsc_resource_id, rsc_party_id, partner_party_id
  FROM apps.pv_resource_info_v
 WHERE rsc_user_id = :user_id;

Because the view joins several TCA tables, queries should filter on indexed identifiers (party ID, resource ID, user ID) where possible and avoid unconstrained full scans on large TCA data sets.