Search Results aso_sup_comp_resp_map_v




Overview
Explore in AI Chat

Overview

ASO_SUP_COMP_RESP_MAP_V is a reporting and integration view in the APPS schema belonging to the ASO – Order Capture product family within Oracle E-Business Suite (documented for 12.1.1 and 12.2.2). It presents the relationship between configurable components and the responses attached to them in Oracle's Supplemental (or "Sup") configuration model. In EBS terms, a component represents an element or question in a configuration or order capture flow, while a response represents an allowable answer or selection. The view joins this mapping to the descriptive metadata of both the component and the response so that a single query returns the component name, its description, its instruction text, the response name and description, and control flags such as MANDATORY_FLAG and DISPLAY_SEQUENCE.

The name of the object is significant for the term searched: the view explicitly aliases ASOCV.DESCRIPTION as COMPONENT_DESCRIPTION. This means consumers searching for "component_description" are served by a friendly, denormalized column rather than having to resolve the underlying COMPONENT_ID against ASO_SUP_COMPONENT_V manually. The view therefore functions as a convenience layer for reports, concurrent programs, and external integrations that need to display configuration questions alongside their permitted responses.

Underlying Base Objects

The ETRM metadata records the view as defined over three referenced base objects:

The join predicates are ASOCRM.COMPONENT_ID = ASOCV.COMPONENT_ID and ASOCRM.RESPONSE_ID = ASORV.RESPONSE_ID. The view also selects ASOCRM.ROWID as ROW_ID. Because it is defined on other views and a synonym rather than directly on base tables, it is intended for read-only query access, not DML.

Key Columns

  • COMPONENT_RESPONSE_ID — Primary identifier of the component-to-response mapping row; the most reliable key for joining to downstream tables.
  • COMPONENT_DESCRIPTION — The descriptive text of the component, sourced from ASO_SUP_COMPONENT_V.DESCRIPTION. This is the column most commonly targeted when users search for component descriptions.
  • INSTRUCTION — Guidance text presented to the end user for the component.
  • COMPONENT_TYPE_MEANING / RESPONSE_TYPE_MEANING — Decoded meanings that are more readable in reports than the underlying coded values.
  • MANDATORY_FLAG — Indicates whether a response is required for the component.
  • RESPONSE_NAME / RESPONSE_DESCRIPTION — The answer value and its explanation, language-sensitive through the VL source.
  • DISPLAY_SEQUENCE — Controls the ordering in which responses appear for a component.

Common Use Cases and Queries

Typical usages include configuration documentation reports, validation of setup completeness, and interface extracts that must publish the permissible answers for each component.

To list all responses for a component, filtering by name:

SELECT component_name, component_description, response_name, response_description, mandatory_flag, display_sequence FROM apps.aso_sup_comp_resp_map_v WHERE component_name = :p_component ORDER BY display_sequence;

To find components lacking a description (a data-quality check driven by the searched term):

SELECT component_id, component_response_id FROM apps.aso_sup_comp_resp_map_v WHERE component_description IS NULL;

To enumerate every component and its response count:

SELECT component_name, component_description, COUNT(response_id) resp_count FROM apps.aso_sup_comp_resp_map_v GROUP BY component_name, component_description ORDER BY component_name;

Because the view is read-only and joins translated views, it should be queried with an appropriate language setting in multi-language implementations.