Results for “as_ptr_salesforce_v”

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

Overview

The view AS_PTR_SALESFORCE_V belongs to the Oracle E-Business Suite product family AS – Sales Foundation. Its documented description, "Partners from salesforce view," identifies its purpose precisely: it exposes records representing sales partners (channel partners, resellers, or selling partners) that have been designated through the Sales Foundation "salesforce" mechanism. The "salesforce" terminology in EBS Sales Foundation is unrelated to the Salesforce.com CRM platform; it refers to a defined selling organization or roster of selling parties maintained within the AS module. Users who search for "what is sflsc in salesforce" are typically encountering the abbreviation within EBS data dictionaries and view names rather than any external ecosystem.

The view consolidates partner-related columns with denormalized descriptive data drawn from customer, address, and human-resources person sources. It provides a single reporting surface for partner identification, address, and the assigned employee, which makes it suitable for operational reporting, extracts, and integration feeds where a flattened partner record is preferable to joins across multiple party and HR views.

Underlying Base Objects

Per the documented view text, AS_PTR_SALESFORCE_V is defined over four referenced objects:

• AS_SALESFORCE_V SALE – the driving source of salesforce partner rows, supplying the salesforce identifier, effective dates, party and address keys, and the DFF attribute columns.
• AS_PARTY_CUSTOMERS_V CUST – supplies the customer name associated with the partner's party/customer record.
• AS_PARTY_ADDRESSES_V ADDR – supplies address attributes such as city and address line 1.
• PER_ALL_PEOPLE_F PEOPLE – supplies the first and last name of the employee person associated with the partner.

Join conditions enforce that the partner address matches the address key, the member flag equals 'Y', the address customer matches the customer record, and the type equals 'PARTNER'. The employee join is an outer join (PEOPLE.PERSON_ID(+)) additionally qualified by the effective date range bracketing TRUNC(SYSDATE), so rows without a currently effective employee assignment are retained. Note that the metadata records this view as "Not implemented in this database" in the ETRM reference, indicating that availability depends on the specific environment and Sales Foundation configuration.

Key Columns

• SALESFORCE_ID – primary identifier of the salesforce (selling organization) record.
• TYPE – constrained in the view definition to 'PARTNER'.
• START_DATE_ACTIVE / END_DATE_ACTIVE – the active date range for the partner assignment.
• PARTNER_CUSTOMER_ID, PARTNER_ADDRESS_ID, EMPLOYEE_PERSON_ID – foreign keys to the customer party, address, and HR person respectively.
• CUSTOMER_NAME, CITY, ADDRESS1 – denormalized descriptive attributes.
• EMPLOYEE_FIRST_NAME, EMPLOYEE_LAST_NAME (aliased from PEOPLE.FIRST_NAME, PEOPLE.LAST_NAME) – the assigned employee's name.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – descriptive flexfield columns for client-extensible partner data.
• Standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include generating active partner rosters, validating partner-address data quality, and exporting partner lists for downstream systems.

SELECT SALESFORCE_ID, CUSTOMER_NAME, CITY, ADDRESS1,
       EMPLOYEE_FIRST_NAME, EMPLOYEE_LAST_NAME,
       START_DATE_ACTIVE, END_DATE_ACTIVE
FROM   AS_PTR_SALESFORCE_V
WHERE  TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE
                          AND NVL(END_DATE_ACTIVE, TRUNC(SYSDATE));

A second pattern examines flexfield attribute usage:

SELECT SALESFORCE_ID, CUSTOMER_NAME,
       ATTRIBUTE_CATEGORY, ATTRIBUTE1, ATTRIBUTE2
FROM   AS_PTR_SALESFORCE_V
WHERE  ATTRIBUTE_CATEGORY IS NOT NULL;

Because the view is documented as not implemented in the reference database, developers should confirm its presence in the target environment before relying on it in concurrent programs, BI Publisher data models, or integration interfaces.