Results for “as_sales_team_ptr_v”

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

Overview

AS_SALES_TEAM_PTR_V is a seeded, VALID database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the AS – Sales Foundation product family and is documented as a "Sales team view for partner." The view exposes the membership of sales teams in which the partner organization is the team member rather than the customer being served. It therefore presents a partner-centric projection of the underlying access records held in AS_ACCESSES_ALL, enriched with party, address, and lookup descriptions.

Because sales team assignments in Oracle EBS are stored generically as access rows, a partner-oriented vantage point is required for partner channel reporting, partner portal integration, and territory/compensation analytics. AS_SALES_TEAM_PTR_V supplies that vantage point. It is read-only by convention: no DML should be issued against the view. It is most commonly consumed by concurrent reports, OAF pages, and outbound interfaces that need to publish partner team membership to external CRM or partner-management systems.

Underlying Base Objects

The view is defined over five referenced objects, as documented in ETRM 12.2.2:

• AS_ACCESSES_ALL (VIEW) — the driving object; holds the sales team access rows, including role, relationship, freeze, reassignment, and leader flags.
• HZ_PARTIES (SYNONYM) — provides the partner party name, party number, and party type.
• HZ_PARTY_SITES (SYNONYM) — links the partner address to its location record via an outer join.
• HZ_LOCATIONS (SYNONYM) — supplies the address components (city, postal code, state, province, county, country, address lines) through an outer join.
• AS_LOOKUPS (VIEW) — joined twice, under the aliases ASLKP2 and ASLKP3, to decode the role and relationship codes into meaningful text.

The join predicates are significant. ACC.PARTNER_CUSTOMER_ID = CUST.PARTY_ID is the only inner join; every other join is outer. This design deliberately preserves access rows even when the partner address, location, or lookup translation is missing, which is essential for reconciliation and cleanup reporting. The lookup joins are constrained by ASLKP2.LOOKUP_TYPE(+) = 'ROLE_TYPE' and ASLKP3.LOOKUP_TYPE(+) = 'SALESFORCE_RELATIONSHIP'.

Key Columns

• ACCESS_ID — primary identifier of the underlying access row; the join key back to AS_ACCESSES_ALL.
• ACCESS_TYPE — discriminates the kind of access granted.
• SALESFORCE_ROLE_CODE and MEANING (from ASLKP2) — the partner's role on the team, resolved through the ROLE_TYPE lookup. This is the column most often targeted by users searching for "role_type".
• SALESFORCE_RELATIONSHIP_CODE and MEANING (from ASLKP3) — the relationship between the partner and the customer, resolved through the SALESFORCE_RELATIONSHIP lookup.
• TEAM_LEADER_FLAG, FREEZE_FLAG, REASSIGN_FLAG, DOWNLOADABLE_FLAG — status flags controlling team behaviour and synchronization.
• CUSTOMER_ID, ADDRESS_ID, PARTNER_CUSTOMER_ID, PARTNER_ADDRESS_ID, PARTNER_CONT_PARTY_ID — party and address identifiers for the served customer and the partner.
• PARTY_NAME, PARTY_NUMBER, PARTY_TYPE — partner identification attributes.
• CITY, POSTAL_CODE, STATE, PROVINCE, COUNTY, COUNTRY, ADDRESS1–ADDRESS4 — partner address detail.
• FREEZE_DATE, REASSIGN_REQUEST_DATE, REASSIGN_REQUESTED_PERSON_ID, REASSIGN_REASON — reassignment workflow state.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns.
• Standard audit columns: ROWID, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include auditing partner sales team composition, validating role assignments against the ROLE_TYPE lookup, and feeding partner portal or CRM extracts.

Locating all access rows bearing a specific partner role:

SELECT ACCESS_ID, PARTY_NAME, SALESFORCE_ROLE_CODE, MEANING
FROM   AS_SALES_TEAM_PTR_V
WHERE  MEANING = 'Partner Manager';

Listing team leaders for a partner organization:

SELECT PARTY_NAME, PARTY_NUMBER, SALESFORCE_ROLE_CODE,
       SALESFORCE_RELATIONSHIP_CODE
FROM   AS_SALES_TEAM_PTR_V
WHERE  TEAM_LEADER_FLAG = 'Y'
AND    PARTY_NUMBER = :party_number;

Reporting frozen or reassignment-pending rows for operational follow-up:

SELECT ACCESS_ID, PARTY_NAME, CITY, STATE, FREEZE_DATE,
       REASSIGN_REQUEST_DATE, REASSIGN_REASON
FROM   AS_SALES_TEAM_PTR_V
WHERE  FREEZE_FLAG = 'Y' OR REASSIGN_FLAG = 'Y';