Search Results rrel_delete_flag




Overview
Explore in AI Chat

Overview

APPS.AS_SALESFORCE_V is a reporting and integration view in Oracle E-Business Suite (EBS) Releases 12.1.1 and 12.2.2 that consolidates Oracle Sales resource, role, and role-assignment data into a single, denormalized result set. It is owned by the APPS schema and exposed as a synonym so it can be referenced without schema qualification from custom reports, concurrent programs, and outbound interfaces. The view is commonly employed as the extract source for customer relationship management (CRM) systems, most notably Salesforce, hence its name: it produces a flattened representation of sales resources joined to their active role relationships, suitable for bulk export or scheduled interface processing.

Because the view is defined on the JTF resource foundation tables, it presents only individual resources assigned to sales-oriented roles. The role-type filter restricts output to the SALES, TELESALES, FIELDSALES, and PRM role categories, ensuring that non-selling resources (for example, service or support personnel) are excluded. The view is non-key-preserving in the sense that a single resource may appear multiple times when assigned to more than one qualifying role; consumers must account for this duplication in downstream logic.

Underlying Base Objects

The view is defined over four base objects, referenced through APPS synonyms:

Joins are equi-joins on RESOURCE_ID = ROLE_RESOURCE_ID (resource side) and ROLE_ID = ROLEB.ROLE_ID = ROLETL.ROLE_ID (role side). The WHERE clause applies the role-type restriction and the individual-resource-type restriction, plus the language predicate.

Key Columns

  • RESOURCE_ID, RESOURCE_NUMBER — unique identifier and human-readable number of the sales resource.
  • CATEGORY — resource classification (EMPLOYEE, PARTNER, PARTY), which drives the conditional DECODE expressions.
  • ROLE_ID, ROLE_NAME, ROLE_TYPE_CODE — the assigned role and its localized name and type category.
  • MEMBER_FLAG, ADMIN_FLAG, MANAGER_FLAG — role-level participation indicators.
  • START_DATE_ACTIVE, END_DATE_ACTIVE, DELETE_FLAG — role-relationship validity and soft-delete state.
  • DECODE expressions — return SOURCE_ID, MANAGING_EMPLOYEE_ID, ADDRESS_ID, or NULL depending on CATEGORY, normalizing heterogeneous resource identities into uniform columns.
  • SOURCE_NAME, SOURCE_FIRST_NAME, SOURCE_LAST_NAME, SOURCE_NUMBER, SOURCE_EMAIL — descriptive resource identity attributes.
  • ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY — the standard DFF/descriptive flexfield columns for extensibility.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns supporting incremental extraction.

Common Use Cases and Queries

Typical applications include Salesforce user provisioning extracts, sales-resource roster reports, role-assignment audits, and CRM data synchronization programs. A representative query retrieves active sales resources with role information:

  • SELECT RESOURCE_ID, RESOURCE_NUMBER, ROLE_NAME, ROLE_TYPE_CODE, START_DATE_ACTIVE, END_DATE_ACTIVE FROM APPS.AS_SALESFORCE_V WHERE DELETE_FLAG = 'N' AND (END_DATE_ACTIVE IS NULL OR END_DATE_ACTIVE > SYSDATE);

Incremental interfaces commonly filter on the audit columns to capture changed rows since a prior run:

  • SELECT RESOURCE_ID, SOURCE_NAME, SOURCE_EMAIL FROM APPS.AS_SALESFORCE_V WHERE LAST_UPDATE_DATE >= :p_since;

For Salesforce-style export, a client may join this view to resource address or party tables to enrich the identity data, using RESOURCE_NUMBER as the natural external key. Because a resource can be returned once per qualifying role, reports that require one row per resource should aggregate on RESOURCE_ID or select a specific ROLE_TYPE_CODE.