Results for “source_promotion_name”
45 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AS_OPPORTUNITY_DETAILS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, belonging to the AS - Sales Foundation product family. It consolidates opportunity (lead) data sourced primarily from AS_LEADS_ALL and enriches it with decoded lookup meanings, customer party attributes, offer information, and sales stage data. The view exposes a denormalized, readable projection of the opportunity record, making it suitable for operational reporting, dashboards, and outbound interfaces that must not query the transactional base tables directly. In EBS 12.1.1 and 12.2.2 the object is documented as VALID, and it remains a stable read-only interface for Sales Foundation opportunity data. It is particularly relevant to users searching on methodology_name, because the view exposes both SALES_METHODOLOGY_ID and METHODOLOGY_CODE columns associated with the opportunity's sales methodology, though the METHODOLOGY_NAME column is returned as a literal NULL in the documented view text.
Underlying Base Objects
The documented view metadata identifies the following referenced objects:
- AS_LEADS_ALL (synonym) — the primary transactional table for opportunities and leads; nearly all exposed columns derive from this source (aliased OPP).
- AS_LOOKUPS (view) and AMS_P_SOURCE_CODES_V (view) — provide decoded meanings such as VEHICLE_RESPONSE and offer name/source code.
- AS_SALES_STAGES_ALL_B and AS_SALES_STAGES_ALL_TL (synonyms) — supply sales stage identifiers and translated stage names referenced by SALES_STAGE_ID.
- AS_STATUSES_TL (synonym) — provides translated status descriptions for the opportunity status code.
- HZ_PARTIES (synonym) — the Trading Community Architecture party table, joined to return CUSTOMER_NAME, PERSON_FIRST_NAME, and PERSON_LAST_NAME.
- OE_LOOKUPS (view) — an Order Management lookup view used for additional decoded values.
The joins are implemented as outer joins so that opportunities lacking an associated party, offer, or lookup value are still returned.
Key Columns
- ROW_ID, LEAD_ID, LEAD_NUMBER — unique row identifier and the opportunity/lead key and business-facing number.
- STATUS_CODE — the opportunity status, decoded through AS_STATUSES_TL.
- CUSTOMER_ID, ADDRESS_ID, CUSTOMER_NAME, PERSON_FIRST_NAME, PERSON_LAST_NAME — customer and contact details sourced from AS_LEADS_ALL and HZ_PARTIES.
- SALES_METHODOLOGY_ID, METHODOLOGY_CODE, METHODOLOGY_NAME — the sales methodology linkage. The name column is hard-coded as NULL in the view definition, so consumers requiring the methodology description must join to the methodology table or the AS_LOOKUPS view on the code.
- SALES_STAGE_ID, WIN_PROBABILITY, TOTAL_AMOUNT, CURRENCY_CODE, DECISION_DATE — pipeline and forecast attributes.
- OFFER_ID, OFFER_NAME, OFFER_CODE — offer information resolved via AMS_P_SOURCE_CODES_V.
- ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the standard DFF flexfield columns for descriptive flexfield data.
- DELETED_FLAG, DELETE_ALLOWED_FLAG, NO_OPP_ALLOWED_FLAG — lifecycle and deletion control flags.
- WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, etc.) — audit and concurrency columns.
Common Use Cases and Queries
Typical uses include pipeline reports, opportunity extracts for CRM or data warehouse loads, and interfaces that need a single flattened source. A sample query retrieving methodology-linked opportunities follows:
SELECT lead_number, status_code, sales_methodology_id, methodology_code, total_amount, currency_code FROM apps.as_opportunity_details_v WHERE deleted_flag = 'N';SELECT lead_number, customer_name, win_probability, decision_date FROM apps.as_opportunity_details_v WHERE sales_stage_id = :stage_id ORDER BY decision_date;SELECT o.lead_number, o.mean_vehicle_response FROM apps.as_opportunity_details_v o WHERE o.vehicle_response_code IS NOT NULL;
Because METHODOLOGY_NAME is null, join AS_LOOKUPS or the methodology base table on METHODOLOGY_CODE to obtain the descriptive name. All queries should filter on DELETED_FLAG to exclude soft-deleted opportunities.
-
APPS.AS_OPPORTUNITY_DETAILS_V·↳ AMS_P_SOURCE_CODES_V·↳ AS_LEADS_ALL·↳ AS_LOOKUPS·Explore AS module →
-
View: IGR_I_APPL_V 12.1.1
This view will be based on OMO public view AS_SALES_LEADS_V and IGR_I_APPL_ALL junction table.
APPS.IGR_I_APPL_V·↳ AMS_LOOKUPS·↳ AMS_P_SOURCE_CODES_V·↳ AS_STATUSES_VL·Explore IGS module →
-
APPS.AS_OPPORTUNITY_DETAILS_V·↳ AMS_P_SOURCE_CODES_V·↳ AS_LEADS_ALL·↳ AS_LOOKUPS·Explore AS module →
-
View: AS_SALES_LEADS_V 12.1.1
sales lead header details
APPS.AS_SALES_LEADS_V·↳ AMS_P_SOURCE_CODES_V·↳ ASO_I_SALES_CHANNELS_V·↳ AS_LOOKUPS·Explore AS module →
-
View: AMS_DS_SALES_LEADS_V 12.2.2
APPS.AMS_DS_SALES_LEADS_V·↳ AMS_P_SOURCE_CODES_V·↳ ASO_I_SALES_CHANNELS_V·↳ AS_LOOKUPS·Explore AMS module →
-
View: AMS_DS_SALES_LEADS_V 12.1.1
APPS.AMS_DS_SALES_LEADS_V·↳ AMS_P_SOURCE_CODES_V·↳ ASO_I_SALES_CHANNELS_V·↳ AS_LOOKUPS·Explore AMS module →
-
View: AS_SALES_LEADS_V 12.2.2
sales lead header details
APPS.AS_SALES_LEADS_V·↳ AMS_P_SOURCE_CODES_V·↳ ASO_I_SALES_CHANNELS_V·↳ AS_LOOKUPS·Explore AS module →
-
View: IGS_RC_I_APPL_V 12.1.1
This view will be based on OMO public view AS_SALES_LEADS_V and IGS_RC_I_APPL_ALL junction table.
Not implemented in this database·Explore IGS module →
-
View: IGS_RC_I_APPL_V 12.2.2
This view will be based on OMO public view AS_SALES_LEADS_V and IGS_RC_I_APPL_ALL junction table.
Not implemented in this database·Explore IGS module →
-
Not implemented in this database·Explore AS module →
-
Not implemented in this database·Explore AS module →
-
View: IGR_I_APPL_V 12.2.2
This view will be based on OMO public view AS_SALES_LEADS_V and IGR_I_APPL_ALL junction table.
Not implemented in this database·Explore IGS module →
-
Not implemented in this database·Explore AS module →
-
Not implemented in this database·Explore AS module →
-
VIEW: APPS.AS_SALES_LEADS_V 12.1.1
-
Sales Opportunities List View
Not implemented in this database·Explore AS module →
-
Sales Opportunities List View
Not implemented in this database·Explore AS module →
-
VIEW: APPS.IGR_I_APPL_V 12.1.1
-
VIEW: APPS.AS_SALES_LEADS_V 12.2.2
-
VIEW: APPS.AS_SALES_LEADS_V 12.2.2
-
VIEW: APPS.AS_SALES_LEADS_V 12.1.1
-
VIEW: APPS.IGR_I_APPL_V 12.1.1
-
View: AS_SALES_LEADS_LISTS_V 12.2.2
Sales Leads List View
Not implemented in this database·Explore AS module →
-
View: AS_SALES_LEADS_LISTS_V 12.1.1
Sales Leads List View
Not implemented in this database·Explore AS module →
-
eTRM - AS Tables and Views 12.2.2
- Retrofitted
-
eTRM - AS Tables and Views 12.1.1
- Retrofitted
-
eTRM - AMS Tables and Views 12.1.1
This table is used to store tracking data for web advertisement and offer type schedules
-
eTRM - AMS Tables and Views 12.2.2
This table is used to store tracking data for web advertisement and offer type schedules
-
eTRM - IGS Tables and Views 12.1.1
Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'.