Search Results source_email

Overview

The AS_FC_SALESFORCE_V view is a Sales Foundation (AS) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As documented in the ETRM repository, it "shows all the salesforce from JTF resource manager," meaning it consolidates resource, group membership, and role relationship data maintained in the Oracle JTF Resource Manager (part of CRM Foundation / Trading Community Architecture) into a single denormalized salesforce-oriented result set.

The view's principal role is to expose a reporting-friendly projection of the sales organization for downstream consumption by Sales Foundation functionality and custom reporting. Rather than requiring consumers to join the JTF resource tables themselves, the view pre-composes the resource-to-group-to-role relationships and restricts the output to sales-oriented role types, namely SALES, TELESALES, FIELDSALES, and PRM. This makes it useful for territory, quota, and compensation processing, as well as for integration or extract routines that need a current picture of who belongs to the salesforce and in what capacity.

The view is marked VALID in the ETRM metadata, confirming that it compiles successfully against the referenced base objects in the certified 12.2.2 environment.

Underlying Base Objects

The view definition joins five JTF resource objects, each referenced through APPS synonyms:

• JTF_RS_RESOURCE_EXTNS — the resource extension table supplying the core salesforce member attributes (RESOURCE_ID, RESOURCE_NUMBER, dates, audit columns, category, addressing, DFF attributes, and source name/email/number information).
• JTF_RS_GROUP_MEMBERS — the group membership table linking resources to sales groups via GROUP_MEMBER_ID and GROUP_ID.
• JTF_RS_ROLE_RELATIONS — the relationship table that associates a group member (ROLE_RESOURCE_TYPE = 'RS_GROUP_MEMBER') with a role, and carries the active date range and delete flag for that association.
• JTF_RS_ROLES_B — the role base table providing role metadata such as ROLE_TYPE_CODE, MEMBER_FLAG, ADMIN_FLAG, and MANAGER_FLAG, and constraining the result to sales role types.
• JTF_RS_ROLES_TL — the role translation table supplying the language-specific ROLE_NAME, joined on the session language via USERENV('LANG').

The join path is: resource to group member, group member to role relation, role relation to role base, and role base to role translation. The role type filter and the language filter are applied at the outer levels, so the view always returns translated role names for sales-related roles only.

Key Columns

• SALESFORCE_ID — aliases RESOURCE_ID, the primary identifier of the salesforce member.
• RESOURCE_NUMBER, TYPE (from RES.CATEGORY), and the source name/first/last/number/email columns — identity and classification attributes of the member.
• ROLE_ID, ROLE_NAME, ROLE_TYPE_CODE — the assigned sales role and its type; ROLE_NAME is language-translated.
• MEMBER_FLAG, ADMIN_FLAG, MANAGER_FLAG — role capability indicators.
• START_DATE_ACTIVE, END_DATE_ACTIVE — effective dating of the role relationship.
• EMPLOYEE_PERSON_ID — derived via DECODE: for EMPLOYEE resources returns SOURCE_ID; for PARTNER resources returns MANAGING_EMPLOYEE_ID.
• SALES_GROUP_ID — the group identifier from membership.
• PARTNER_CUSTOMER_ID, PARTNER_ADDRESS_ID — populated for PARTNER-category resources via DECODE.
• MEMBER_DELETE_FLAG, RREL_DELETE_FLAG — soft-delete indicators on the membership and relationship records.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the descriptive flexfield segments carried from the resource extension.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

Typical uses include listing all active salesforce members, resolving a resource to its current sales role, and driving downstream processes that must distinguish employees from partners. A representative query listing active members and their roles follows:

• SELECT salesforce_id, resource_number, role_name, role_type_code, sales_group_id FROM as_fc_salesforce_v WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE) AND NVL(rrel_delete_flag,'N') = 'N' AND NVL(member_delete_flag,'N') = 'N';
• To retrieve only partner-organisation members: SELECT salesforce_id, partner_customer_id, partner_address_id, role_type_code FROM as_fc_salesforce_v WHERE type = 'PARTNER' AND partner_customer_id IS NOT NULL;
• To obtain employee person identifiers for a role: SELECT salesforce_id, employee_person_id, role_name FROM as_fc_salesforce_v WHERE role_type_code = 'SALES';

Because the view restricts to the SALES, TELESALES, FIELDSALES, and PRM role types, queries against it will not surface non-sales roles even when the underlying resource holds additional roles. Consumers should also note that duplicate rows can appear when a resource participates in multiple sales groups or roles, so aggregation or DISTINCT may be required depending on the reporting intent.