Search Results address_status_code




Overview
Explore in AI Chat

Overview

AS_OPPORTUNITY_DET_ADDR_V is a Sales Foundation (AS) database view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes opportunity header detail together with associated address and party information. The view header objects to the AS_OPPORTUNITY_DETAILS entity and joins it to party/address data, producing a denormalized projection that is convenient for reporting, integration extracts, and concurrent program queries against sales opportunity records. According to the ETRM metadata, the object is documented as a view but is marked "Not implemented in this database," meaning there is no shipped DDL in all instances; it may exist only where specific module scripts have been applied. In the 12.2.2 metadata the owner is not specified and no referenced base objects are documented, so the view text itself is the only authoritative structural definition available.

Underlying Base Objects

The documented ETRM metadata lists no explicit base tables for this view. However, the view text references the opportunity table (aliased OPP, which is AS_OPPORTUNITY or equivalent), the offer table aliased OFR (OFFER_CODE), and a party table aliased PARTY providing PARTY_NAME, PERSON_FIRST_NAME, PERSON_LAST_NAME, and the corresponding phonetic name columns. Lookup meaning is derived through aliases ASL8 (VEHICLE_RESPONSE) and ASL3 (METHODOLOGY), which correspond to FND_LOOKUP_VALUES style lookups keyed by lookup code. Because the view exposes OPP.ROWID as ROW_ID and includes the standard WHO columns plus ORG_ID, it behaves like a normal updatable-style projection over the opportunity entity, though it is intended primarily for read access.

Key Columns

Common Use Cases and Queries

Typical usage is a lead/opportunity address roster for selling-cycle reporting, or extracting opportunity records for integration. Note that the user query "end poverty assistant manager address" does not correspond to any documented column; END_USER_CUSTOMER_NAME, END_USER_CUSTOMER_ID and END_USER_ADDRESS_ID are the nearest documented fields, and address at the party level is surfaced through the PARTY alias rather than by a distinct assistant-manager attribute.

SELECT row_id,
       lead_number,
       status_code,
       customer_name,
       total_amount,
       currency_code,
       end_user_customer_name,
       end_user_address_id
  FROM as_opportunity_det_addr_v
 WHERE org_id = :p_org_id
   AND deleted_flag = 'N'
 ORDER BY creation_date DESC;
SELECT a.lead_number,
       a.vehicle_response,
       a.methodology_name,
       a.followup_date
  FROM as_opportunity_det_addr_v a
 WHERE a.status_code = :p_status
   AND a.win_probability >= 50;

Because the metadata record lists no referenced objects and shows the view as not implemented in this database, deployments should verify the presence of the view in each environment before relying on it in custom reports or interfaces.