Results for “asf_partners_lov_v”

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

Overview

ASF_PARTNERS_LOV_V is a reporting and list-of-values view documented under the ASF – Sales Online product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to expose a consolidated, flattened record set of sales-related partners and party resources for use by Oracle Forms LOV (List of Values) components, concurrent reporting, and integration extracts within the Sales Online module. The view joins resource extension data, role relationships, party master data, and party site address data to present sales resources – including indirect, telesales, field sales, and partner (PRM) roles – alongside their associated party names, types, statuses, and addresses.

Per the ETRM documentation, the view is not implemented in the reference database, meaning no runtime data dictionary row or materialized copy exists in the documented environment. The object is documented instead as a metadata definition (view text and column list), which indicates it is provided by the ASF application schema for consumption when the Sales Online module is licensed and installed.

Underlying Base Objects

The documented ETRM metadata lists no explicit base objects, but the view text reveals its composition over the following Oracle EBS tables:

• JTF_RS_RESOURCE_EXTNS (alias A) – Resource extension attributes supplying SOURCE_ID, RESOURCE_ID, ADDRESS_ID, CATEGORY, and the active date range.
• JTF_RS_ROLE_RELATIONS (alias RL) – Links resources to roles; the join is restricted to RL.ROLE_RESOURCE_TYPE = 'RS_INDIVIDUAL'.
• JTF_RS_ROLES_B (alias R) – Role definitions, filtered to ROLE_TYPE_CODE in ('SALES','TELESALES','FIELDSALES','PRM').
• HZ_PARTIES (alias B) – Party master, supplying PARTY_NAME, PARTY_TYPE, and STATUS (limited to 'A' and 'I').
• HZ_PARTY_SITES (alias C) and HZ_LOCATIONS (alias D) – Combined in an inline subquery to resolve address attributes through PARTY_SITE_ID, filtered to site statuses 'A' and 'I'.

The join between resource extensions and party sites is an outer join (A.ADDRESS_ID = H.PARTY_SITE_ID(+)), so partners without a resolved address still appear with null address columns.

Key Columns

• PARTY_ID / PARTY_NAME / PARTY_TYPE – Identity of the underlying trading party from HZ_PARTIES.
• ADDRESS1–ADDRESS4, CITY, PROVINCE, COUNTY, STATE, POSTAL_CODE, COUNTRY – Address elements resolved via HZ_LOCATIONS for the party site.
• STATUS – Party status ('A' active, 'I' inactive).
• RESOURCE_ID / ADDRESS_ID – Resource and party site identifiers used for downstream lookups.
• CATEGORY – Restricted to 'PARTNER' or 'PARTY', distinguishing partner records from generic parties.
• START_DATE_ACTIVE / END_DATE_ACTIVE – Effective date boundaries for the resource extension record.

Common Use Cases and Queries

Typical usage includes populating partner selection LOVs on Sales Online forms, driving partner territory reports, and feeding downstream order or commission extracts. Because the view restricts roles to sales-related codes and category to partner/party values, it functions as a purpose-built subset rather than a general party query.

• Locating active sales partners by name: SELECT party_name, resource_id, status FROM asf_partners_lov_v WHERE status = 'A' AND category = 'PARTNER' ORDER BY party_name;
• Reviewing address completeness for a partner: SELECT party_name, city, state, postal_code, country FROM asf_partners_lov_v WHERE resource_id = :resource_id;
• Filtering by effective dates: SELECT party_id, party_name, start_date_active, end_date_active FROM asf_partners_lov_v WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

Query performance benefits from indexing on JTF_RS_RESOURCE_EXTNS.SOURCE_ID, JTF_RS_ROLE_RELATIONS.ROLE_RESOURCE_ID, and HZ_PARTY_SITES.PARTY_SITE_ID, given the multi-table outer join structure.