Search Results rsc_contact_id

Overview

APPS.PV_RESOURCE_INFO_V is a PL/SQL view owned by the APPS schema and registered in Oracle E-Business Suite under the FND design data object PV.PV_RESOURCE_INFO_V. Its status is VALID. The "PV" prefix associates the object with Oracle Partner Management and related partner/resource functionality within the EBS 12.1.1 and 12.2.2 technology stacks.

The view presents a denormalized, read-oriented projection of resource information that links FND user identities, JTF resource records, HZ party records, and partner relationship data into a single row per resource. Because it joins contact, party, and relationship information, the view is a convenient access point for reporting and integration logic that must resolve a resource to both its primary party and its associated partner party. Oracle classifies the object as Internal and warns that it is not supported for direct customer access; consumers should treat it as a source for standard Oracle Applications programs and for read-only reporting rather than as a controlled integration interface.

Underlying Base Objects

The documented dependencies of PV_RESOURCE_INFO_V are APPS.HZ_ORG_CONTACTS, APPS.HZ_PARTIES, APPS.HZ_RELATIONSHIPS, and APPS.JTF_RS_RESOURCE_EXTNS, each accessed through a synonym in the APPS schema. The view therefore sits on top of the Trading Community Architecture (HZ) model plus the JTF resource extension table.

• JTF_RS_RESOURCE_EXTNS supplies the resource identity and category information that anchors each row.
• HZ_PARTIES supplies party names, including both the resource party and the partner party.
• HZ_ORG_CONTACTS relates the resource contact record to its organization contact definition.
• HZ_RELATIONSHIPS provides the relationship type that links the resource party to the partner party.

The view is referenced by APPS.OZF_BUDGETAPPROVAL_PVT, a PL/SQL package used in budget approval processing, which confirms that the view is intended primarily as an internal data source for Oracle application modules rather than as an end-user query object.

Key Columns

• RSC_USER_ID — Numeric user identifier originating from FND_USER.
• RSC_RESOURCE_ID — The resource identifier for the JTF resource record.
• RSC_CONTACT_ID — Contact identifier, foreign key to HZ_ORG_CONTACTS.
• RSC_CATEGORY_ID — Resource category, validated against JTF_OBJECTS_VL. Documented values include EMPLOYEE, PARTNER, PARTY, SUPPLIER_CONTACT, and OTHER.
• RSC_RELATIONSHIP — Relationship type name, for example CUSTOMER_SUPPLIER.
• RSC_PARTY_ID / RSC_PARTY_NAME — Identifier and name of the primary resource party.
• PARTNER_PARTY_ID / PARTNER_PARTY_NAME — Identifier and name of the partner party associated with the resource. The PARTNER_PARTY_NAME column, with a documented length of 360, is the element returned when users search for "partner_party_name," making it the primary output for partner-name reporting.

Common Use Cases and Queries

The most common scenario is resolving partner names for resource and user records, particularly for partner-facing reports and approval workflows such as OZF_BUDGETAPPROVAL_PVT. The following query retrieves partner details for all partner-category resources:

SELECT RSC_RESOURCE_ID, RSC_USER_ID, RSC_PARTY_NAME, PARTNER_PARTY_ID, PARTNER_PARTY_NAME FROM APPS.PV_RESOURCE_INFO_V WHERE RSC_CATEGORY_ID = 'PARTNER';

To locate the partner associated with a specific user or resource:

SELECT RSC_USER_ID, RSC_RESOURCE_ID, PARTNER_PARTY_NAME FROM APPS.PV_RESOURCE_INFO_V WHERE RSC_USER_ID = :p_user_id;

Because the view is documented as Oracle Internal Use Only, direct SQL access is unsupported. Oracle recommends that customers consume this data through standard Oracle Applications programs, or build a custom view over the same underlying HZ and JTF tables when a supported reporting interface is required. All queries should be executed with the APPS schema context or an appropriately privileged reporting account.