Results for “as_opportunity_contacts”

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

Overview

The AS_OPPORTUNITY_CONTACTS view is a multi-org (organization-specific) reporting and integration object owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It resides within the AS – Sales Foundation product family and presents the association between sales opportunities (leads) and the contacts linked to them. Functionally, the view exposes the contents of the underlying AS_LEAD_CONTACTS_ALL table, filtered at runtime by the organization identifier (ORG_ID) belonging to the current session, so that users and concurrent programs only see contact records scoped to the operating unit (or organization) in which they are working.

Because opportunity contacts are used throughout the Sales Foundation and related modules — for identifying buying influencers, tracking roles and ranks, and linking contacts to customer sites and phone numbers — this view serves as the primary read interface for reports, OBIEE/EBS extracts, and custom integrations that must respect multi-org security.

Underlying Base Objects

The view is defined over a single referenced base object:

• AS_LEAD_CONTACTS_ALL (referenced via a synonym in the APPS schema) — the multi-org base table that physically stores the opportunity/lead contact relationships.

The view text is a straightforward projection of all columns from AS_LEAD_CONTACTS_ALL, constrained by a multi-org filter. The filter compares ORG_ID with the value derived from USERENV('CLIENT_INFO') (the first 10 characters, after trimming the leading blank), defaulting to -99 when no organization context is established. This is the standard Oracle EBS multi-org security pattern used to isolate data by operating unit.

Key Columns

• LEAD_CONTACT_ID — Primary key of the lead/opportunity contact record.
• LEAD_ID — Identifier of the parent opportunity/lead; the join key back to the lead header.
• CONTACT_ID — The contact person associated with the opportunity.
• CUSTOMER_ID, ADDRESS_ID, PHONE_ID — Customer, address, and phone identifiers linked to the contact.
• RANK — Relative ranking or priority of the contact within the opportunity.
• ENABLED_FLAG — Indicates whether the contact association is active.
• ORG_ID — Operating unit / organization driving the multi-org filter.
• LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program / who-columns for traceability.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield (DFF) segments for extensibility.

Common Use Cases and Queries

The view is used to drive opportunity-contact reporting, integration extractions, and influence-role analyses. A typical listing query is:

SELECT lead_contact_id, lead_id, contact_id, customer_id, address_id,
      rank, enabled_flag, org_id
FROM  apps.as_opportunity_contacts
WHERE  lead_id = :p_lead_id
AND    enabled_flag = 'Y';

Because the multi-org predicate is embedded in the view, callers must ensure that CLIENT_INFO is initialized (via FND_CLIENT_INFO.SET_CLIENT_INFO or the standard Forms/Concurrent Manager context) before querying, otherwise records defaulting to organization -99 may be returned. Common scenarios include:

• Populating opportunity detail reports with associated decision-makers and influencers.
• Extracting contact-to-opportunity mappings into data warehouses or CRM integrations.
• Enforcing operating-unit security in custom APPS-schema views and programs.

Only records matching the active organization context are exposed, preserving the multi-org architecture of the Sales Foundation module.