Results for “asbv_sales_force”

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

Overview

ASBV_SALES_FORCE is a read-only reporting view in the Oracle E-Business Suite Sales Foundation (AS) module. It presents a denormalized, business-friendly projection of sales force records maintained in the underlying AS_SALESFORCE table, exposing salesperson assignments, sales group membership, and partner/customer relationships in a single queryable object.

In EBS 12.1.1 and 12.2.2, the view is part of the Applications View (ASBV_ prefix) family, which is intended primarily for reporting and integration rather than transactional data entry. The "_BV" naming convention signals that the object is a view owned by the APPS schema and intended to be queried by reporting tools such as Oracle Reports, Oracle Discoverer, BI Publisher, and custom PL/SQL packages. The view text carries a WITH READ ONLY constraint, confirming that it cannot be used for INSERT, UPDATE, or DELETE operations.

Because the view filters the underlying sales force data through a defined column projection, it is frequently the target object used by external systems and interfaces that need to resolve a salesperson to a customer or partner relationship without joining the full AS_SALESFORCE table.

Underlying Base Objects

The documented view text defines ASBV_SALES_FORCE entirely over a single base table:

• AS_SALESFORCE SF — the primary sales force assignment table in Oracle Sales Foundation. The view aliases this table as SF and selects a fixed set of columns from it.

The view does not join to any other base objects per the documented metadata. All columns exposed by ASBV_SALES_FORCE map one-to-one to columns in AS_SALESFORCE, with the exceptions of the two derived expression columns described below. The ETRM metadata notes that referenced base objects are "none documented," reinforcing that AS_SALESFORCE is the sole source object.

Key Columns

The view exposes the following columns, with the most business-relevant ones described below:

• "_LA:TYPE" — a lookup-type descriptor rendered as the literal string '_LA:SF.TYPE:AS_LOOKUPS:SALESFORCE_TYPE:MEANING'. This is a flexfield/lookup attribute marker used by EBS reporting engines to resolve the lookup code into its display meaning.
• STATUS_CODE — the current status of the sales force record, typically referencing a value in the AS_LOOKUPS lookup for sales force status.
• CLIENT_NUMBER — the client identifier associated with the sales force record. This is the column most relevant to users searching for "client_number," since it links a salesperson record to a client account.
• "_DF" — a display/flex descriptor marker rendered as '_DF:AS:AS_SALESFORCE:SF', used by EBS to indicate the descriptive flexfield context for the sales force entity.
• SALESFORCE_ID — the primary key of the underlying AS_SALESFORCE record.
• EMPLOYEE_PERSON_ID — the HR employee or person identifier for the assigned salesperson, enabling joins to PER_PEOPLE_F.
• SALES_GROUP_ID — the identifier of the sales group to which the salesperson belongs.
• PARTNER_CUSTOMER_ID, PARTNER_ADDRESS_ID, PARTNER_CONTACT_ID — the customer, address, and contact identifiers that define the partner side of the sales force relationship.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — the standard EBS "WHO" and auditing columns.

Common Use Cases and Queries

Typical uses of ASBV_SALES_FORCE include resolving client numbers to salespeople, reporting on sales group coverage, and driving partner-facing integrations.

To find all sales force records for a specific client number:

SELECT salesforce_id, client_number, employee_person_id, sales_group_id, status_code FROM apps.asbv_sales_force WHERE client_number = :client_number;

To list active salespeople within a sales group:

SELECT sf.employee_person_id, sf.status_code FROM apps.asbv_sales_force sf WHERE sf.sales_group_id = :group_id AND sf.status_code = 'ACTIVE';

Because the view is read-only and defined over AS_SALESFORCE only, any reporting that requires customer names, addresses, or person details must join ASBV_SALES_FORCE to the relevant customer or HR views using the PARTNER_CUSTOMER_ID or EMPLOYEE_PERSON_ID columns.