Results for “ast_sales_team_emp_v”

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

Overview

The view APPS.AST_SALES_TEAM_EMP_V belongs to the Oracle EBS TeleSales (AST) module and is owned by the APPS schema. It exposes sales-team employee access records, combining assignment and access data from the TeleSales access model with employee resource details, sales group names, lookup meanings, and the associated location and territory of the customer or lead. The view presents a denormalized, report-ready projection of sales-team membership for employees, including flags such as TEAM_LEADER_FLAG, OWNER_FLAG, FREEZE_FLAG, and REASSIGN_FLAG, plus role and relationship descriptions resolved from the TeleSales lookup tables.

In EBS 12.1.1 and 12.2.2, this view is typically used where a consumer needs a human-readable picture of which employees are on a sales team and the role they perform. It is not a transactional entry object; it is a read-oriented view suitable for reporting, data extraction, and integration extracts from TeleSales.

Underlying Base Objects

The documented referenced base objects are: AS_ACCESSES_ALL (VIEW), AS_LOOKUPS (VIEW), FND_TERRITORIES_VL (VIEW), HR_GENERAL (PACKAGE), HR_SECURITY (PACKAGE), HZ_LOCATIONS (SYNONYM), HZ_PARTY_SITES (SYNONYM), JTF_RS_GROUPS_TL (SYNONYM), JTF_RS_RESOURCE_EXTNS (SYNONYM), PER_ASSIGNMENTS_F (VIEW), and PER_JOBS (SYNONYM).

The central driver is AS_ACCESSES_ALL (aliased ACC), the TeleSales access table that records each assignment of a salesforce to a customer, address, or lead. Employee identity is resolved through JTF_RS_RESOURCE_EXTNS (SF), filtered to CATEGORY = 'EMPLOYEE', joined on SALESFORCE_ID = SF.RESOURCE_ID. Group names come from JTF_RS_GROUPS_TL (SG) in the user's language. Location and territory data are carried from HZ_PARTY_SITES, HZ_LOCATIONS, and FND_TERRITORIES_VL. Role and relationship lookups are resolved from AS_LOOKUPS with the outer-join symbols preserved on the lookup conditions. Job title is drawn from PER_JOBS via PER_ASSIGNMENTS_F. The HR packages HR_GENERAL and HR_SECURITY supply organization and security context used by the underlying HR views.

Key Columns

• ACCESS_ID, SALESFORCE_ID, PERSON_ID, CUSTOMER_ID, ADDRESS_ID, LEAD_ID, SALES_LEAD_ID — primary identifiers linking access, resource, person, and customer records.
• ACCESS_TYPE, SALESFORCE_ROLE_CODE, SALESFORCE_RELATIONSHIP_CODE — the nature of the access and the role/relationship, with descriptive MEANING columns resolved from AS_LOOKUPS.
• TEAM_LEADER_FLAG, OWNER_FLAG, FREEZE_FLAG, REASSIGN_FLAG, DOWNLOADABLE_FLAG — status flags for team-lead and ownership designation, freeze, reassignment, and download eligibility.
• SOURCE_FIRST_NAME, SOURCE_LAST_NAME, SOURCE_NAME, SOURCE_EMAIL, SOURCE_PHONE — employee contact attributes from JTF_RS_RESOURCE_EXTNS.
• GROUP_ID, GROUP_NAME — the assigned sales group.
• CITY, STATE, PROVINCE, COUNTY, COUNTRY, POSTAL_CODE, ADDRESS1–ADDRESS4, TERRITORY_SHORT_NAME — address and territory attributes of the associated customer or lead.
• JOB_NAME — the employee's job as derived through the HR assignment join.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID, and the ATTRIBUTE1–ATTRIBUTE15 flex field set.

Common Use Cases and Queries

Typical scenarios include identifying the sales team assigned to a customer or lead, resolving team leaders, extracting employee contact details for integration, and reporting by sales group, territory, or job.

Team members for a customer:

SELECT person_id, source_name, group_name, meaning role, owner_flag
FROM   apps.ast_sales_team_emp_v
WHERE  customer_id = :p_customer_id;

Team leaders by group:

SELECT group_name, source_name, group_id
FROM   apps.ast_sales_team_emp_v
WHERE  team_leader_flag = 'Y';

Employees assigned to a territory:

SELECT source_name, city, state, territory_short_name, job_name
FROM   apps.ast_sales_team_emp_v
WHERE  territory_short_name = :p_territory;

Because the view joins AS_ACCESSES_ALL to resource and HR data with outer joins on lookups and translated tables, results are typically filtered by customer, group, or territory to keep query cost bounded in 12.1.1 and 12.2.2 environments.