Results for “close_reason_code”

10 results




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

Overview

The view APPS.AST_OPPORTUNITY_CONTACT_V is a TeleSales (AST) reporting and integration object in Oracle E-Business Suite, exposing opportunity (lead) header data from the sales pipeline joined with related party, contact, channel, stage, and status descriptive attributes. Its primary role is to present a denormalized, ready-to-query result set that combines the core opportunity row from AS_LEADS_ALL with the associated contact party, phone, and lookup meanings, so that concurrent programs, OA Framework pages, and custom reports do not have to reconstruct the joins themselves.

The view is defined in the APPS schema and carries a VALID status in both 12.1.1 and 12.2.2. It surfaces the PRIMARY_CONTACT attribute referenced in the underlying definition, which is derived from the contact party relationship rather than stored directly on the opportunity record. This distinction is central to understanding the object: TeleSales opportunities relate to contacts through association tables, and the view materializes the primary contact's name and party identifier so consumers can filter, sort, or display opportunities by contact without extra lookups.

Underlying Base Objects

According to the ETRM metadata, the view is defined over the following referenced objects:

Key Columns

  • LEAD_ID / LEAD_NUMBER — unique opportunity identifier and the user-visible opportunity number.
  • PRIMARY_CONTACT / PRIMARY_CONTACT_PARTY_ID — the name and party identifier of the primary contact associated with the opportunity; the column most frequently searched by users.
  • PARTY_NAME, PARTY_TYPE, PARTY_NUMBER — the end customer or party the opportunity belongs to.
  • CUSTOMER_ID and ADDRESS_ID — the customer and address on the opportunity header.
  • SALES_STAGE_ID with STGTL.NAME — stage identifier and its translated name.
  • STATUS with ASSTATUSES.MEANING — status code and its lookup meaning.
  • CHANNEL_CODE with ASOCHANNELS.MEANING — channel code and decoded description.
  • TOTAL_AMOUNT, CURRENCY_CODE, WIN_PROBABILITY, CLOSE_REASON — pipeline value and forecasting fields.
  • ORG_ID — operating unit, critical for multi-org security filtering.
  • ATTRIBUTE_CATEGORY / ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns.
  • DELETED_FLAG — indicates logically deleted opportunities.

Common Use Cases and Queries

Typical usages include opportunity pipeline reports, contact-centric list pages, and integration extracts that need contact and customer context in a single row. Users searching for "primary_contact" are usually building a report filtered or grouped by the primary contact name.

Sample query returning opportunities with their primary contact and status:

  • SELECT lead_number, party_name, primary_contact, meaning status_meaning, total_amount, currency_code FROM apps.ast_opportunity_contact_v WHERE org_id = :p_org_id AND deleted_flag = 'N' ORDER BY lead_number;
  • SELECT primary_contact, count(*) opp_count, sum(total_amount) pipeline_value FROM apps.ast_opportunity_contact_v WHERE deleted_flag = 'N' GROUP BY primary_contact ORDER BY pipeline_value DESC;
  • SELECT lead_number, party_name, primary_contact, primary_contact_party_id FROM apps.ast_opportunity_contact_v WHERE primary_contact LIKE :search_text;

When querying, always include the ORG_ID predicate to respect operating unit security, and filter DELETED_FLAG = 'N' unless the report intentionally includes removed records. Because the view joins multiple HZ and lookup objects, it is best used as a reporting layer rather than as the target of DML.