Search Results primary_contact_party_id




Overview
Explore in AI Chat

Overview

AS_SALES_LEADS is a core transactional table in the Oracle E-Business Suite AS – Sales Foundation product family. The table is owned by the OSM schema and holds sales lead records — the pre-qualification entities that capture prospective customer interest before an opportunity or quote is created. Each row represents a single lead, tracking its origin, ranking, assignment, budget, and lifecycle status. In Oracle EBS 12.1.1 and 12.2.2, this object acts as the integration point between lead capture channels (such as marketing campaigns, telemarketing, referrals, and Partner Relationship Management) and downstream sales execution activities.

From a data-modeling perspective, the ETRM metadata classifies AS_SALES_LEADS as hub-leaning. This should be read as a modeling suggestion: the table behaves primarily as a hub that anchors a stable business key (the lead) with a surrogate identifier, while its descriptive status, scoring, and assignment attributes are candidates for satellite separation in a Data Vault design. The presence of numerous foreign keys into HZ parties, party sites, resources, and reference tables reinforces the hub interpretation.

Key Information Stored

The table contains 98 documented columns. The surrogate primary key, enforced by AS_SALES_LEADS_PK, is SALES_LEAD_ID. A unique index, AS_SALES_LEADS_U1 (SALES_LEAD_ID), provides the business-key candidate. Among the most operationally significant columns:

Common Use Cases and Queries

Typical uses include lead pipeline reporting, conversion analysis, sales-assignment auditing, and referral tracking. A common query joins the lead to its customer and status:

  • Reporting open leads by sales representative: join ASSIGN_TO_SALESFORCE_ID to JTF_RS_RESOURCE_EXTNS.
  • Pipeline value by status: aggregate BUDGET_AMOUNT grouped by STATUS_CODE (joined to AS_STATUSES_B).
  • Lead scoring analytics: filter on TOTAL_SCORE or LEAD_RANK_SCORE with SCORECARD_ID.
  • Referral analysis: use REFERRAL_STATUS, REFERRED_BY, and REFERRAL_TYPE columns for partner-sourced leads.
  • Conversion tracing: link AS_SALES_LEAD_OPPORTUNITY via SALES_LEAD_ID to measure lead-to-opportunity conversion.

Because the table carries standard WHO columns (CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, SECURITY_GROUP_ID), reporting queries commonly apply Multi-Org and security-group filters.

Related Objects

AS_SALES_LEADS participates in a dense dependency network. The most significant related objects include:

  • HZ_PARTIES / HZ_PARTY_SITES / HZ_CONTACT_POINTS — joined via CUSTOMER_ID, ADDRESS_ID, and contact columns for the customer and contact entity model.
  • AS_STATUSES_B — joined via STATUS_CODE for lifecycle state.
  • JTF_RS_RESOURCE_EXTNS and JTF_RS_GROUPS_B — assignment of the lead to a sales resource or group.
  • AS_SALES_LEAD_CONTACTS and AS_SALES_LEAD_OPPORTUNITY — child tables referencing SALES_LEAD_ID, capturing associated contacts and opportunities.
  • AS_SALES_LEAD_LINES — line-level lead detail keyed by SALES_LEAD_ID.
  • AML_INTERACTION_LEADS — links interaction records to the originating lead.
  • AS_SALES_LEADS_LOG — audit history of changes to lead records.
  • ASO_QUOTE_RELATED_OBJECTS — associates a quote with the lead through OBJECT_ID.

These relationships make AS_SALES_LEADS the central hub for lead-related data within Sales Foundation and its CRM integrations.