Search Results selectable_flag
Overview
PV_PRTNR_CONTACTS_LOV_V is a Partner Management (PV) view in Oracle E-Business Suite that exposes a list-of-values (LOV) style result set of partner-side sales representatives and the sales groups to which they belong. In EBS 12.1.1 and 12.2.2 this object is classified as not implemented in the database in the ETRM repository, meaning that although the view definition text and column list are documented, the database object is not deployed in a standard install. Where present, it is intended to back LOV and lookup queries in PV flows that require a joined view of employees (salespersons), their employer party, their JTF resource record, and their assigned JTF sales group.
The most commonly searched attribute against this view is salesrep_full_name, which resolves to the concatenation of the person's first, middle, last name, and suffix from HZ_PARTIES. The view therefore serves as a reporting and integration convenience layer for identifying a sales representative by full name in partner management contexts.
Underlying Base Objects
The view is defined over the following base objects, all joined through HZ and JTF relationship tables:
HZ_PARTIES(aliasedPARTYandREL_NAME) — supplies the employer party and the salesperson party, including name, address, and status.HZ_PARTY_RELATIONSHIPS— the linkage between a party and the entity it is anEMPLOYEE_OF, driving the employee-to-employer association.HZ_ORG_CONTACTS— the organization contact record tied to the party relationship.JTF_RS_RESOURCE_EXTNS— the resource extension record, providing the salesforce resource ID, source phone, contact and user IDs.FND_USER— the application user, supplying user name, email address, and end-date validity.JTF_RS_GROUPS_VLandJTF_RS_GROUP_MEMBERS— the sales group header and its active members (rows filtered onDELETE_FLAG = 'N').
No additional base objects are documented in ETRM for this view.
Key Columns
SALESREP_FULL_NAME— concatenation ofPERSON_FIRST_NAME,PERSON_MIDDLE_NAME,PERSON_LAST_NAME, andPERSON_NAME_SUFFIX; the primary search target forsalesrep_full_namequeries.SALESREP_LAST_NAME— the salesperson's last name, useful for sorting or partial-match LOVs.SALES_GROUP_NAME/SALES_GROUP_ID— the JTF sales group to which the representative is assigned.EMPLOYEE_PERSON_ID— the party ID of the salesperson, returned asRELATIONSHIP.PARTY_ID.SALESFORCE_ID/RESOURCE_ID— the JTF resource identifier for the representative.EMPLOYER_NAME/EMPLOYER_PARTY_ID— the employing organization's name and party ID.EMPLOYEE_STATUS,ADDRESS,WORK_TELEPHONE,EMAIL_ADDRESS,USER_NAME,FND_USER_ID,SALESPERSON_NAME,BUSINESS_GROUP_ID, andSELECTABLE_FLAG— supporting attributes; note thatBUSINESS_GROUP_IDis hard-coded to 0 andSELECTABLE_FLAGto 0 in the view text.
Common Use Cases and Queries
Typical uses include locating a sales representative by name for partner assignment, validating that a representative is an active JTF group member, and joining the returned RESOURCE_ID to downstream PV or JTF tables. Because the member filter requires an active FND user and the group membership must be non-deleted, the view naturally restricts to currently valid salespersons.
A representative query:
SELECT salesrep_full_name, salesrep_last_name, sales_group_name, salesforce_id, employer_name, email_address
FROM PV_PRTNR_CONTACTS_LOV_V
WHERE UPPER(salesrep_full_name) LIKE UPPER(:p_name)||'%'
ORDER BY salesrep_full_name;
To resolve a specific representative to a resource:
SELECT salesforce_id, resource_id, fnd_user_id, user_name
FROM PV_PRTNR_CONTACTS_LOV_V
WHERE employee_person_id = :l_party_id;
Before deploying any form or report that references this view, confirm whether it actually exists in the target instance, since ETRM records it as not implemented in a standard database.
-
View: PV_PRTNR_CONTACTS_LOV_V
12.2.2
product: PV - Partner Management , implementation_dba_data: Not implemented in this database ,
-
View: PV_PRTNR_CONTACTS_LOV_V
12.1.1
product: PV - Partner Management , implementation_dba_data: Not implemented in this database ,