Results for “asfv_sales_force”

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

Overview

The ASFV_SALES_FORCE view is a read-only denormalized reporting object belonging to the AS (Sales Foundation) module in Oracle EBS 12.1.1 and 12.2.2. It resolves the raw foreign-key identifiers stored on the AS_SALESFORCE entity into business-friendly descriptive values by joining to the underlying people, customer, address, contact, and sales group tables. This makes the view suitable for direct query use by reporting tools, ad-hoc SQL, and integration extracts that require human-readable sales force information without embedding the join logic themselves.

The view is declared WITH READ ONLY, meaning no DML is permitted against it; it is purely a query surface. In the ETRM metadata, the view is noted as "Not implemented in this database," which indicates that the object may not be deployed in every environment and that its presence depends on the relevant AS Sales Foundation install or patch level.

Underlying Base Objects

The formal metadata does not enumerate referenced base objects, but the view text exposes them explicitly. The driving table is AS_SALESFORCE (aliased SF). It is outer-joined ((+) syntax) to:

• PER_ALL_PEOPLE_F (PER) — the employee/person record, filtered by an effective-date window using TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND NVL(EFFECTIVE_END_DATE, SYSDATE).
• RA_CUSTOMERS (CUST) — the partner customer.
• RA_ADDRESSES_ALL (ADDR) — the partner address.
• RA_CONTACTS (CONT) — the partner contact.
• AS_SALES_GROUPS (GRP) — the sales group.

Because every dependent table is outer-joined, the view preserves all AS_SALESFORCE rows even when descriptive attributes are missing.

Key Columns

The view exposes both surrogate IDs and resolved descriptive columns. Notable attributes include:

• SALESFORCE_ID, EMPLOYEE_PERSON_ID, SALES_GROUP_ID, PARTNER_CUSTOMER_ID, PARTNER_ADDRESS_ID, PARTNER_CONTACT_ID — primary and foreign key identifiers.
• STATUS_CODE, CLIENT_NUMBER — status and client identifiers from AS_SALESFORCE.
• _LA:TYPE and _DF — lookup/descriptive flexfield resolution columns. The literal _LA:SF.TYPE:AS_LOOKUPS:SALESFORCE_TYPE:MEANING instructs the reporting layer to resolve the sales force type from AS lookups, while _DF:AS:AS_SALESFORCE:SF marks the descriptive flexfield context.
• SALES_GROUP_NAME, FIRST_NAME/LAST_NAME, PARTNER_CUSTOMER_NAME, PARTNER_CITY, PARTNER_COUNTRY, PARTNER_CONTACT_FIRST_NAME/PARTNER_CONTACT_LAST_NAME — resolved descriptive values.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY.

Common Use Cases and Queries

The view is commonly used to report on sales force membership, territory alignment, and partner relationships. A typical query listing active sales force records with their owners and partners:

• SELECT SALESFORCE_ID, FIRST_NAME, LAST_NAME, SALES_GROUP_NAME, PARTNER_CUSTOMER_NAME, STATUS_CODE FROM ASFV_SALES_FORCE WHERE STATUS_CODE = 'A';
• SELECT SALES_GROUP_NAME, COUNT(*) FROM ASFV_SALES_FORCE GROUP BY SALES_GROUP_NAME;
• SELECT CLIENT_NUMBER, PARTNER_CUSTOMER_NAME, PARTNER_CITY, PARTNER_COUNTRY FROM ASFV_SALES_FORCE WHERE PARTNER_CONTACT_LAST_NAME IS NOT NULL;

Because the effective-dated person join is already applied, results reflect the person record valid as of the current date, simplifying point-in-time reporting without additional date logic.