Results for “asf_partner_profile_v”

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

Overview

ASF_PARTNER_PROFILE_V is a reporting and integration view within the Oracle E-Business Suite ASF – Sales Online product family. It is designed to support the Opportunity Exchange module by exposing the complete list of valid partners who participate in that exchange. In EBS 12.1.1 and 12.2.2, partner-facing functionality such as lead distribution, lead sharing, and opportunity collaboration depends on a consolidated, query-friendly source of partner profile data; this view provides exactly that.

The view is not a transactional entity. It is a read-only projection that joins partner records to party site and location data, producing one row per qualifying partner with denormalized address information. Because the underlying partner data is filtered to a specific origin system type and party-site status, the view acts as a curated roster rather than a full partner master. This makes it well suited to reporting, LOV-style lookups, and integration payloads where only "active or inactive but valid" partners should appear.

The user search term lead_sharing_status corresponds directly to one of the view's exposed columns, indicating that consumers frequently query this view to determine whether a given partner is currently eligible to receive or share leads.

Underlying Base Objects

The view text defines three base objects joined together:

• PV_PARTNERS_V (alias A) — the primary partner source. This supplies partner identity, party identifiers, lead-sharing attributes, and the origin system reference. The join condition requires that the partner's origin system type resolve to LEAD_EXCHANGE, with a NVL(..., 'ZZ') default applied so that null origin types are excluded from the 'LEAD_EXCHANGE' match.
• HZ_PARTY_SITES (alias B) — joined on A.PARTNER_PARTY_ID = B.PARTY_ID, restricting to party sites whose STATUS is 'A' (active) or 'I' (inactive). This status filter is deliberate: it retains sites that remain structurally valid for exchange purposes while excluding other lifecycle states.
• HZ_LOCATIONS (alias C) — joined via B.LOCATION_ID = C.LOCATION_ID, supplying the address components projected by the view.

Although the documented metadata lists no owner and no referenced base objects, the embedded view text is explicit, and the joins above are the operative lineage. Administrators should note the "Not implemented in this database" annotation: in environments where the view is absent, the definition above serves as the authoritative reference for manual deployment or troubleshooting.

Key Columns

• PARTNER_ID — derived by casting A.ORIG_SYSTEM_REFERENCE to a number; the primary numeric identifier for the partner.
• PARTNER_NAME — the partner party name from A.PARTNER_PARTY_NAME.
• PARTY_ID — the trading community party identifier (A.PARTNER_PARTY_ID), used to join back to HZ tables.
• LEAD_SHARING_STATUS — the partner's current lead-sharing state; central to determining whether the partner may participate in lead exchange.
• LEAD_SHARE_APPR_FLAG — approval flag indicating whether lead sharing has been authorized for the partner.
• PV_PARTNER_ID — the source partner identifier from PV_PARTNERS_V, useful for tracing the origin record.
• ADDRESS1–ADDRESS4, CITY, POSTAL_CODE, STATE, PROVINCE, COUNTY, COUNTRY — denormalized location attributes sourced from HZ_LOCATIONS.

Common Use Cases and Queries

Typical scenarios include identifying partners eligible for lead sharing, validating a partner during opportunity creation, and feeding external systems with partner profile and address data.

To list partners whose lead sharing is active:

• SELECT partner_id, partner_name, lead_sharing_status, lead_share_appr_flag FROM asf_partner_profile_v WHERE lead_sharing_status = 'ACTIVE';

To retrieve full profile and address detail for a specific partner:

• SELECT partner_name, party_id, address1, city, state, postal_code, country FROM asf_partner_profile_v WHERE partner_id = :p_partner_id;

To audit approval coverage across the exchange:

• SELECT lead_share_appr_flag, COUNT(*) FROM asf_partner_profile_v GROUP BY lead_share_appr_flag;