Results for “as_ptr_salesreps_v”

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

Overview

AS_PTR_SALESREPS_V is a Sales Foundation (AS) reporting view that exposes the definition of salespersons whose type is a partner rather than an employee. In Oracle EBS 12.1.1 and 12.2.2 it consolidates salesperson records from RA_SALESREPS_ALL with the associated partner customer, contact, address, sales group, and manager information, presenting a single denormalized row per partner salesperson. The view is not implemented as a physical database object in the reference environment ("Not implemented in this database"), which indicates it is a shipped, upgrade-tolerant view generated by the AS schema rather than a table populated by data. Its practical value lies in reporting and integration: it supplies the manager name, customer name, contact names, and compensation attributes needed by commission, territory, and partner-facing reports, and it shields callers from the join logic among AS, RA, and PER objects.

Underlying Base Objects

The view text documents the following base objects: RA_CUSTOMERS, AS_SALESFORCE, AS_SALES_GROUPS, CN_PERIOD_STATUSES (aliased twice, PS and PE), FND_USER, PER_ALL_PEOPLE_F, PER_PEOPLE_X, RA_ADDRESSES, RA_CONTACTS, RA_SALESREPS_ALL, SO_SALES_CREDIT_TYPES_115, AS_LOOKUPS, and CN_PERIOD_STATUSES. AS_SALESFORCE holds the salesforce definition (type, status, partner customer, partner address and contact). RA_SALESREPS_ALL supplies the operative salesperson assignment (SALESREP_ID, active dates, compensation currency, cost center, GL accounts, processing periods). PER_ALL_PEOPLE_F and PER_PEOPLE_X resolve employee and manager person names, while AS_SALES_GROUPS provides the group name and MANAGER_PERSON_ID used to derive the manager's full name. CN_PERIOD_STATUSES resolves the start and end processing period names, FND_USER resolves the assigned user, and RA_CUSTOMERS, RA_CONTACTS and RA_ADDRESSES provide the partner-level identity and location data.

Key Columns

• SALESREP_ID, SALESFORCE_ID, SALES_GROUP_ID — identifiers linking the salesperson to the salesforce and sales group definitions.
• EMPLOYEE_PERSON_ID, PARTNER_CUSTOMER_ID, PARTNER_CONTACT_ID, PARTNER_ADDRESS_ID — the partner-side keys that distinguish partner salespersons from employees.
• MANAGER_PERSON_ID (from AS_SALES_GROUPS) plus the concatenated manager name (MGRPEOPLE.FIRST_NAME || ' ' || MGRPEOPLE.LAST_NAME) — the manager_full_name value most users search for.
• Salesperson name (PEOPLE.FIRST_NAME, PEOPLE.LAST_NAME and the concatenated form) and contact name (CONT.FIRST_NAME, CONT.LAST_NAME and concatenation).
• CUSTOMER_NAME and CUSTOMER_NUMBER — partner customer identity.
• TYPE, STATUS_CODE, LOOK.MEANING, RAREPS.STATUS — salesperson type and status lookups.
• START_DATE_ACTIVE, END_DATE_ACTIVE, START_PROCESSING_PERIOD_ID, END_PROCESSING_PERIOD_ID, PS.PERIOD_NAME, PE.PERIOD_NAME — assignment validity and period context.
• COMPENSATION_CURRENCY_CODE, COST_CENTER, CHARGE_TO_COST_CENTER, COMMISSIONABLE_FLAG, SALES_CREDIT_TYPE_ID, ST.NAME — compensation and credit configuration.
• GL_ID_REV, GL_ID_FREIGHT, GL_ID_REC, SET_OF_BOOKS_ID — accounting flexfield references.
• ASSIGNED_TO_USER_ID, U.USER_NAME — the FND user associated with the salesperson.
• ORG_ID, ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY — multi-org and descriptive flexfield context.

Common Use Cases and Queries

The view is typically queried to report partner salespersons with their manager, active dates, and customer context, or to validate that a salesperson is correctly configured before commission processing. A representative query for the manager_full_name requirement is:

• SELECT salesrep_id, customer_name, manager_full_name, start_date_active, end_date_active, status FROM as_ptr_salesreps_v WHERE org_id = :p_org_id AND NVL(end_date_active, SYSDATE+1) > SYSDATE;
• SELECT customer_number, customer_name, COUNT(*) FROM as_ptr_salesreps_v GROUP BY customer_number, customer_name;
• SELECT salesrep_id, user_name, period_name, commissionable_flag FROM as_ptr_salesreps_v WHERE sales_group_id = :p_group_id;

Because the view joins PER_ALL_PEOPLE_F and PER_PEOPLE_X for both the salesperson and the manager, reports using it should always filter on ORG_ID and, where date-sensitive, restrict to currently active rows. As the object is documented as not implemented in the reference database, administrators should confirm its presence in the target instance and treat the view text as the authoritative definition of its columns.