Results for “as_emp_salesforce_v”

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

Overview

The view AS_EMP_SALESFORCE_V belongs to the Oracle E-Business Suite (EBS) product family AS – Sales Foundation. Its documented description is "Employees from salesforce view," indicating that it exposes the set of employees who participate in a salesforce, either as individual sales resources or as members of a sales group. In release 12.1.1 and 12.2.2, AS – Sales Foundation provides the shared sales entities (sales groups, resources, and role definitions) consumed by downstream modules such as Oracle Sales, Oracle Telesales, and Oracle Field Sales. This view is a reporting and integration convenience layer: rather than requiring callers to join the JTF resource tables and PER_PEOPLE_X directly, it returns a denormalized, human-readable projection of sales personnel together with their group membership, contact details, and audit columns.

Underlying Base Objects

The documented view text joins six base objects. The driving table is JTF_RS_RESOURCE_EXTNS SALE, filtered to CATEGORY = 'EMPLOYEE'. Role definitions are supplied by JTF_RS_ROLES_B ROLE and JTF_RS_ROLE_RELATIONS RREL, with the role restricted to MEMBER_FLAG = 'Y' and ROLE_TYPE_CODE IN ('SALES','TELESALES','FIELDSALES'). Group membership is resolved through JTF_RS_GROUP_MEMBERS MEM and JTF_RS_GROUPS_TL GRP, and person attributes are joined from PER_PEOPLE_X PEOPLE on SALE.SOURCE_ID = PEOPLE.PERSON_ID. The membership and group joins are outer joins (the (+) operator), so employees without an assigned sales group are still returned, with null group fields. The group translation table is language-filtered via USERENV('LANG'), ensuring the group name is returned in the session language. The ETRM metadata notes the view is "Not implemented in this database" and that no base objects are separately documented, meaning these relationships are derived from the view text itself.

Key Columns

The documented column list includes the resource identifier SALESFORCE_ID (the resource ID underlying the salesforce member), the standard who-columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN, along with the effective-dating pair START_DATE_ACTIVE and END_DATE_ACTIVE. The employee person identifier is exposed as EMPLOYEE_PERSON_ID, while SALES_GROUP_ID carries the owning group. Descriptive attributes are provided by EMPLOYEE_FIRST_NAME, EMPLOYEE_LAST_NAME, EMPLOYEE_FULL_NAME (a concatenation of first and last name), SALES_GROUP_NAME, WORK_TELEPHONE, and EMAIL_ADDRESS. Fifteen flexible ATTRIBUTE columns (plus ATTRIBUTE_CATEGORY) are propagated from the resource extension record.

Common Use Cases and Queries

Typical uses include validating salesforce setup, populating pick lists of sales representatives, and building integrations that need employee-level contact data scoped to a sales context. A representative query is:

• SELECT EMPLOYEE_FULL_NAME, SALES_GROUP_NAME, WORK_TELEPHONE, EMAIL_ADDRESS FROM AS_EMP_SALESFORCE_V WHERE SALES_GROUP_ID = :group_id ORDER BY EMPLOYEE_LAST_NAME;
• SELECT SALESFORCE_ID, EMPLOYEE_PERSON_ID, EMAIL_ADDRESS FROM AS_EMP_SALESFORCE_V WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE + 1);
• Reporting the count of active employees per sales group: SELECT SALES_GROUP_NAME, COUNT(*) FROM AS_EMP_SALESFORCE_V GROUP BY SALES_GROUP_NAME;

Because group and membership joins are outer, consumers should handle null SALES_GROUP_ID and SALES_GROUP_NAME values when an employee is not currently assigned to a salesforce group.