Search Results as_salesforce_v




Overview

AS_SALESFORCE_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, classified under the AS – Sales Foundation product. The ETRM metadata describes it simply: this view shows all the salesforce from the JTF resource manager. In practice, it consolidates resource identity, role assignment, and role relationship information from the JTF Resource Manager (JTF_RS) tables into a single flattened structure representing the sales organization. Its role in EBS reporting and integration is to expose who constitutes the "salesforce" — employees, partners, and parties holding sales-oriented roles — without requiring report authors or interfaces to join the underlying JTF tables manually.

Regarding the user's search term "wmt," no column, table, or attribute by that name appears in the documented metadata for this view. WMT most commonly refers to Oracle's Warehouse Management module, which is unrelated to AS_SALESFORCE_V. Within the context of this object, the abbreviation has no documented meaning, and the view contains no field bearing that designation.

Underlying Base Objects

The ETRM 12.2.2 metadata documents four referenced base objects, all accessed through APPS synonyms:

  • JTF_RS_RESOURCE_EXTNS — the resource extension table supplying the core resource record (RES).
  • JTF_RS_ROLES_B — the role definition base table (ROLEB), supplying role identity and flags.
  • JTF_RS_ROLES_TL — the role translation table (ROLETL), supplying the language-specific role name.
  • JTF_RS_ROLE_RELATIONS — the role-to-resource relationship table (RREL), supplying assignment context and active dates.

The view joins RES to RREL on RESOURCE_ID equalling ROLE_RESOURCE_ID, restricted to ROLE_RESOURCE_TYPE of 'RS_INDIVIDUAL'. RREL joins to ROLEB on ROLE_ID, and ROLEB joins to ROLETL on ROLE_ID with language matched to the session language via USERENV('LANG'). The result set is further filtered so that only roles with ROLE_TYPE_CODE in ('SALES', 'TELESALES', 'FIELDSALES', 'PRM') are returned.

Key Columns

The view exposes the resource's surrogate and business keys through SALESFORCE_ID and RESOURCE_NUMBER, with standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) carried through. Role attributes include ROLE_ID, ROLE_NAME, ROLE_TYPE_CODE, MEMBER_FLAG, ADMIN_FLAG, and MANAGER_FLAG, while RREL_DELETE_FLAG, START_DATE_ACTIVE, and END_DATE_ACTIVE describe the assignment's lifecycle. The TYPE column corresponds to the resource CATEGORY value.

Three DECODE expressions in the view text produce category-dependent identifiers: EMPLOYEE_PERSON_ID derives from SOURCE_ID where the category is EMPLOYEE (otherwise MANAGING_EMPLOYEE_ID), PARTNER_CUSTOMER_ID and PARTNER_ADDRESS_ID populate only for PARTNER resources, and PARTNER_CONTACT_ID populates only for PARTY resources. Source name, number, and email columns (SOURCE_NAME, SOURCE_FIRST_NAME, SOURCE_LAST_NAME, SOURCE_NUMBER, SOURCE_EMAIL) provide human-readable identity data, and fifteen generic ATTRIBUTE columns preserve extensibility.

Common Use Cases and Queries

Typical uses include sales organization reporting, role membership validation, and integration feeds that populate downstream CRM or territory management systems. A basic listing of active sales resources:

  • SELECT salesforce_id, resource_number, role_name, role_type_code FROM apps.as_salesforce_v;
  • SELECT * FROM apps.as_salesforce_v WHERE role_type_code = 'TELESALES';
  • SELECT salesforce_id, employee_person_id FROM apps.as_salesforce_v WHERE type = 'EMPLOYEE' AND rrel_delete_flag = 'N';
  • SELECT resource_number, role_name, start_date_active FROM apps.as_salesforce_v WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));

Because ROLE_NAME is sourced from the translation table filtered by USERENV('LANG'), result labels appear in the session language. Queries should account for the RREL_DELETE_FLAG and date-range columns when identifying currently effective salesforce membership.