Search Results aso_sup_component_vl




Overview
Explore in AI Chat

Overview

ASO_SUP_COMPONENT_VL is a multi-language (VL) view owned by the APPS schema within the ASO - Order Capture product family of Oracle E-Business Suite. It presents translated supplementary component (SUP_COMPONENT) definitions used by Oracle's order capture and configuration functionality. In EBS terminology, a "supplementary component" represents an additional question, attribute, or data element collected from a user or external system during order capture, typically associated with configurable products or models. The VL designation indicates that the view joins a base table (language-independent data) to a translation table (language-dependent text) and filters the translation rows by the session's current language.

Because only validated, translated data is presented for the active language, the view serves as the standard reporting and integration interface for supplementary component metadata. External systems, concurrent programs, and custom forms typically query this view rather than the underlying tables directly, since it resolves the language join automatically through USERENV('LANG') and exposes user-visible names and instructions alongside the technical attributes.

Underlying Base Objects

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

The view text joins the two on COMPONENT_ID and restricts the translation rows with T.LANGUAGE = USERENV('LANG'). The base row provides ROW_ID (the B.ROWID), making the view updatable on the base table where the translation join permits. Because it is a VL view, each query returns exactly one translation row per component for the session language, eliminating the need for consumers to manage the TL join manually.

Key Columns

  • COMPONENT_ID — unique identifier for the supplementary component; the join key between the B and TL tables.
  • COMPONENT_TYPE — classifies the component (for example, the type of supplementary question or data element).
  • COMPONENT_NAME / DESCRIPTION / INSTRUCTION — language-dependent text sourced from ASO_SUP_COMPONENT_TL, presented in the session's language.
  • RESPONSE_TYPE — defines the expected user response format (for example, text, list, date, number).
  • MANDATORY_FLAG — indicates whether a response is required before the order line or configuration can proceed.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
  • CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield (DFF) segments, enabling customer-specific extensions without schema modification.
  • ROW_ID — the ROWID of the base table row, used by Oracle Forms and certain APIs to address the underlying record.

Common Use Cases and Queries

Typical uses include validating supplementary component setups, generating configuration documentation, and integrating order capture metadata with external order management or CPQ systems. The MANDATORY_FLAG and RESPONSE_TYPE columns are frequently inspected when auditing configuration rules, while the DFF attributes support customer-specific reporting.

Example: list all mandatory components for the current language.

SELECT component_id,
       component_name,
       component_type,
       response_type,
       mandatory_flag
FROM   aso_sup_component_vl
WHERE  mandatory_flag = 'Y'
ORDER  BY component_name;

Example: retrieve instructions and DFF context for a specific component.

SELECT component_id,
       component_name,
       description,
       instruction,
       context,
       attribute1,
       attribute2
FROM   aso_sup_component_vl
WHERE  component_id = :p_component_id;

Because the view filters on USERENV('LANG'), queries executed from a session with a different language setting return translated text for that language, making the view suitable for multilingual reporting and integration without additional join logic.