Search Results aso_sup_response_vl




Overview
Explore in AI Chat

Overview

ASO_SUP_RESPONSE_VL is an APPS-owned, VALID Oracle E-Business Suite view belonging to the ASO - Order Capture product family. It presents a language-translated, read-only projection of supplier (or party) response definitions used within Oracle's order capture and fulfillment configuration. In ETRM terminology the "_VL" suffix denotes a "view with language," meaning the view resolves translated descriptive columns against the session language while exposing the operational and audit columns from the base entity table. The view is available in both EBS 12.1.1 and 12.2.2, where it retains the same definition and column list.

Because responses are a configuration-style entity, the view is primarily consumed for reporting, integration extracts, and lookup validation rather than for transactional data entry. Application logic that writes responses operates against the base tables; the view provides a stable, flattened read surface that combines the denormalized base record with its language-specific name and description.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the APPS schema:

The view joins B.RESPONSE_ID = T.RESPONSE_ID and filters T.LANGUAGE = USERENV('LANG'), so each row returned corresponds to the response identified by RESPONSE_ID, enriched with the translated name and description for the current session language. The join is a one-to-many relationship in the underlying data model (one base row, many language rows in the TL table); the USERENV('LANG') predicate collapses it to a single row per RESPONSE_ID.

Key Columns

  • ROW_ID — the ROWID of the base table row (aliased from B.ROWID); useful as a surrogate identifier in update-through-view scenarios.
  • RESPONSE_ID — the primary key and foreign key to the base entity; the join key between the _B and _TL tables.
  • RESPONSE_NAME — the translated response name from ASO_SUP_RESPONSE_TL.
  • DESCRIPTION — the translated description from ASO_SUP_RESPONSE_TL.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns sourced from the base table.
  • CONTEXT, ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield (DFF) context and segment columns, sourced from the base table.

Common Use Cases and Queries

Typical scenarios include listing response definitions for configuration review, validating a RESPONSE_ID during integration, and joining responses to order capture or supplier data.

  • List all responses in the session language:
SELECT response_id, response_name, description
FROM   aso_sup_response_vl
ORDER  BY response_name;
  • Retrieve a single response by ID:
SELECT response_id, response_name, description
FROM   aso_sup_response_vl
WHERE  response_id = :p_response_id;
  • Include audit and DFF attributes for reporting:
SELECT response_id, response_name, attribute1, attribute2,
       created_by, creation_date
FROM   aso_sup_response_vl;

Because the view enforces USERENV('LANG'), multilingual reporting should ensure NLS_LANG is set appropriately; otherwise the join may return no row for languages lacking a translation record. When full multi-language extracts are required, query ASO_SUP_RESPONSE_B and ASO_SUP_RESPONSE_TL directly.