Search Results as_salesforce_sub_v




Overview
Explore in AI Chat

Overview

AS_SALESFORCE_SUB_V is a seeded Oracle E-Business Suite view owned by the APPS schema and delivered as part of the AS – Sales Foundation product. Its documented purpose is to present "all the salesforce from JTF resource manager who are members or managers." In practical terms, the view resolves the membership hierarchy maintained in the JTF Resource Manager tables into a single, denormalized list of sales resources, together with the sales group to which each resource belongs and the active date range of that assignment.

The view has a status of VALID in both the 12.1.1 and 12.2.2 releases covered by the ETRM documentation, and it is exposed through a synonym so that it can be queried without schema qualification. Because it flattens role, resource, and group information into a compact result set, it is typically consumed by reports, concurrent programs, and integrations that need to identify which resources are currently effective as sales members or sales managers, rather than by direct end-user forms. The user query "source_last_name" corresponds directly to one of the view's projected columns, which is the column most often used to search or filter sales personnel by surname.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through synonyms in the APPS schema:

The joins are driven by RESOURCE_ID between the resource extension table and the group members table, and by GROUP_MEMBER_ID between the group members table and the role relations table. The role relations row is then matched to the role definition on ROLE_ID, constrained to ROLE_RESOURCE_TYPE = 'RS_GROUP_MEMBER'. Records with DELETE_FLAG = 'Y' in either the membership or the role relation table are excluded, ensuring that only active, non-obsolete assignments are returned.

Key Columns

  • SALESFORCE_ID – the resource identifier of the sales person, sourced from RES.RESOURCE_ID.
  • SALES_GROUP_ID – the group identifier to which the resource belongs, sourced from MEM.GROUP_ID.
  • START_DATE_ACTIVE – the date on which the membership/role assignment becomes effective.
  • END_DATE_ACTIVE – the date on which the assignment ceases to be effective.
  • SOURCE_NAME – the resource's formatted display name.
  • SOURCE_FIRST_NAME – the resource's first name.
  • SOURCE_LAST_NAME – the resource's last name, and the column most frequently used for lookups and sorting.

Common Use Cases and Queries

The view is commonly used to enumerate the effective sales force for a group, to validate that a resource is a member or manager of a sales role, and to drive downstream reporting by name. A representative query that locates a sales person by surname is:

SELECT salesforce_id, sales_group_id, source_name, source_last_name, start_date_active, end_date_active FROM apps.as_salesforce_sub_v WHERE source_last_name = 'SMITH' ORDER BY source_last_name, source_first_name;

To list all currently active members for a given group, the effective-date columns can be used as follows:

SELECT salesforce_id, source_name, start_date_activate FROM apps.as_salesforce_sub_v WHERE sales_group_id = :p_group_id AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE + 1);

Because the view already restricts results to the SALES, TELESALES, FIELDSALES, and PRM role types and applies the MEMBER_FLAG/MANAGER_FLAG logic, consumers do not need to re-implement that filtering; they can join this view to sales group, territory, or opportunity tables on SALESFORCE_ID and SALES_GROUP_ID to attribute transactions to the correct sales representative.