Results for “as_lead_contacts”

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

Overview

The AS_LEAD_CONTACTS view is a multi-org reporting and integration object in the Oracle E-Business Suite Sales Foundation (AS) product family. It presents the association between sales leads (opportunities) and the contacts linked to them, exposing one row per lead–contact relationship. In the EBS 12.1.1 and 12.2.2 data models, the view provides a secured, application-facing window onto the underlying AS_LEAD_CONTACTS_ALL table, which is the physical, multi-org partitioned store of opportunity contact data.

Because AS_LEAD_CONTACTS applies the operating unit (ORG_ID) security predicate through the multi-org views (MO: Security Profile / MO: Operating Unit) built into the "ALL" table synonym, it is the preferred object for reporting, concurrent programs, and custom integrations that must respect organizational access. Application code, OBIEE-style extracts, and reconciliation scripts query this view rather than the base table to ensure data is filtered by the current organization context. The view status is documented as VALID and is owned by the APPS schema, consistent with standard EBS seeded view conventions.

Underlying Base Objects

Per the ETRM metadata, the sole referenced base object is AS_LEAD_CONTACTS_ALL, exposed to the APPS schema as a synonym. The view definition is a direct projection: every column in the view is selected from AS_LEAD_CONTACTS_ALL without joins, aggregation, or transformation. This means AS_LEAD_CONTACTS is a security-filtered passthrough view, and the relationship cardinality, column semantics, and data types are inherited verbatim from the base table.

Operationally, the multi-org filtering is supplied by the underlying _ALL object’s synonym layer (e.g., AS_LEAD_CONTACTS_ALL typically resolves through a secured synonym pointing to AS_LEAD_CONTACTS with the ORG_ID predicate). Because the view is defined directly over the ALL object, the effective row set returned to a session depends on the operating unit or security profile assigned to the logged-in user. No DML should be performed against the view from custom code; inserts and updates must go through the application APIs that manage the base table.

Key Columns

• LEAD_CONTACT_ID – Primary key uniquely identifying the lead–contact association row.
• LEAD_ID – Foreign key to the sales lead (opportunity) header.
• CONTACT_ID – Foreign key to the contact record associated with the lead.
• CONTACT_PARTY_ID – Trading Community Architecture (TCA) party identifier for the contact; used for 360-degree party joins.
• CUSTOMER_ID / ADDRESS_ID – Customer and address context for the contact at the point of association.
• PHONE_ID – Identifier of the phone number (from TCA phone/contact-point tables) linked to the contact for this lead. This is the column most often searched for phone-related joins.
• PRIMARY_CONTACT_FLAG – Indicates whether this contact is the primary contact for the lead.
• ROLE – Role the contact plays on the opportunity (e.g., decision maker, influencer).
• RANK – Ordering/priority value for the contact within the lead.
• ENABLED_FLAG – Active/inactive status of the association.
• ORG_ID – Operating unit that owns the row; drives multi-org security.
• Who columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus the concurrent request audit columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 – Descriptive flexfield segments for extensibility.

Common Use Cases and Queries

Typical scenarios include listing contacts per opportunity, identifying primary contacts, and resolving the phone number associated with a contact. The PHONE_ID column satisfies searches for phone information, though a join to the phone/contact-point table is normally required to retrieve the actual number.

• Contacts for a lead: SELECT contact_id, contact_party_id, role, primary_contact_flag, phone_id FROM as_lead_contacts WHERE lead_id = :p_lead_id AND enabled_flag = 'Y';
• Primary contact lookup: filter on PRIMARY_CONTACT_FLAG = 'Y' for a given LEAD_ID.
• Phone association: SELECT lead_id, contact_id, phone_id FROM as_lead_contacts WHERE phone_id IS NOT NULL; then resolve numbers against the phone/contact-point table using PHONE_ID.
• Org-scoped extract: rely on the view’s built-in ORG_ID security rather than adding an explicit predicate, since the underlying synonym enforces the operating unit.

All queries return only rows permitted by the session’s operating unit or security profile, making the view suitable for both ad-hoc reporting and feed-style integrations.