Search Results component_type_meaning




Overview
Explore in AI Chat

Overview

ASO_SUP_COMPONENT_V is an APPS-owned, VALID database view within the ASO - Order Capture product family of Oracle E-Business Suite (documented across 12.1.1 and 12.2.2). The suffix "_V" denotes a "value" or "translated" view; the object is built over the _VL (value-plus-language) underlying view and adds joins to FND_LOOKUP_VALUES_VL to resolve coded values into their human-readable meanings. It exposes the configurable "components" that make up the supplemental questionnaire framework used during order capture — that is, the questions, instructions, and response-driven elements presented to users when they configure or qualify a sales order, quote, or model. The view's principal role is reporting and integration: it provides a denormalized, meaning-enriched row set suitable for BI Publisher reports, OBIEE/OTBI-style extracts, custom concurrent programs, and interface queries, without requiring callers to separately join to the lookup tables. Because it preserves WHO columns and the 15 descriptive flexfield (DFF) attribute columns, it also serves as a convenient source for auditing and attribute-based filtering.

Underlying Base Objects

The documented base objects are ASO_SUP_COMPONENT_VL (VIEW) and FND_LOOKUP_VALUES_VL (VIEW), which is referenced twice (aliased D and E). ASO_SUP_COMPONENT_VL is the language-enabled view of the ASO_SUP_COMPONENT base entity; it holds the translation-sensitive columns (COMPONENT_NAME, DESCRIPTION, INSTRUCTION) and all physical columns such as COMPONENT_ID, COMPONENT_TYPE, RESPONSE_TYPE, and MANDATORY_FLAG, along with the DFF attributes. The two FND_LOOKUP_VALUES_VL instances decode the internal codes: alias D joins on LOOKUP_TYPE = 'ASO_SUP_COMPONENT_TYPE' matching COMPONENT_TYPE (producing COMPONENT_TYPE_MEANING), and alias E joins on LOOKUP_TYPE = 'ASO_SUP_RESPONSE_TYPE' matching RESPONSE_TYPE (producing RESPONSE_TYPE_MEANING). The DECODE in the view text ensures RESPONSE_TYPE_MEANING is populated only when COMPONENT_TYPE = 'QUESTION'; otherwise it returns a null/empty string, since response semantics apply only to question-type components. The view is therefore one level removed from the physical table (table → VL view → V view) and two levels removed from the raw lookup codes.

Key Columns

  • ROW_ID / COMPONENT_ID — Primary key of the underlying row and the component's unique identifier.
  • COMPONENT_TYPE / COMPONENT_TYPE_MEANING — The internal type code (e.g., QUESTION, INSTRUCTION) and its lookup meaning.
  • COMPONENT_NAME / DESCRIPTION / INSTRUCTION — User-facing text presented on the supplemental questionnaire.
  • RESPONSE_TYPE / RESPONSE_TYPE_MEANING — The expected answer format for a question (meaning populated only for QUESTION-type components).
  • MANDATORY_FLAG — Indicates whether the user must supply a response.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit (WHO) columns.
  • CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns enabling customer-specific data and filtering.

Common Use Cases and Queries

Typical uses include listing all active components for a questionnaire definition, reporting only mandatory questions, and extracting questionnaire structure to an integration file. Because the view already resolves both lookups, queries remain simple.

SELECT component_id,
       component_name,
       component_type_meaning,
       response_type_meaning,
       mandatory_flag
  FROM aso_sup_component_v
 WHERE component_type = 'QUESTION'
   AND mandatory_flag = 'Y'
 ORDER BY component_name;

To audit driven-by-flexfield or recently changed components:

SELECT component_id,
       component_name,
       response_type_meaning,
       last_updated_by,
       last_update_date
  FROM aso_sup_component_v
 WHERE last_update_date >= SYSDATE - 30
 ORDER BY last_update_date DESC;

Note that CALLER_ID or ORG_ID security is not enforced by the view itself; responsibility for applying any required security context remains with the querying program. The view is read-only and should not be used for DML — inserts and updates must target the underlying ASO_SUP_COMPONENT entity through supported APIs.