Search Results aso_sup_response_type

Overview

APPS.ASO_SUP_COMPONENT_V is a reporting and integration view in the Oracle E-Business Suite Order-to-Cash (ASO) schema. It exposes the supplemental component definitions that drive the configurator-style "supplemental" qualification and question flows used by Oracle Sales and Oracle Order Management. Each row represents a single supplemental component — either a question or another component type — along with the descriptive metadata required to render, interpret, and validate the component within a runtime UI or an inbound/outbound interface.

The view's central role is to resolve coded values into human-readable meanings. It joins the base supplemental component entity to two independent lookups (ASO_SUP_COMPONENT_TYPE and ASO_SUP_RESPONSE_TYPE) so that consumers receive both the stored code and its translated meaning in a single row. Because it is a view, it presents a read-only, denormalized projection suitable for concurrent programs, BI Publisher reports, OAF/VBCS integration payloads, and ad hoc SQL — without exposing the base table's internal storage mechanics to the caller.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two referenced objects:

• ASO_SUP_COMPONENT_VL (VIEW) — the multi-language base view that supplies the physical columns of the supplemental component: identifiers, component type, component name, description, response type, instruction text, the mandatory flag, WHO audit columns, the DFF context, and attributes 1 through 20.
• FND_LOOKUP_VALUES_VL (VIEW) — the Applications Foundation lookup values view, referenced twice (aliased D and E) to translate the component type and response type lookup codes into their meanings.

The join to FND_LOOKUP_VALUES_VL is an equi-join on lookup code, constrained to the lookup type ASO_SUP_COMPONENT_TYPE for alias D and ASO_SUP_RESPONSE_TYPE for alias E. Both lookups are effectively inner joins; a component whose type or response code has no active lookup match will not be returned. This is a key behavioral consideration when the view is used as a data source.

Key Columns

• ROW_ID / COMPONENT_ID — surrogate and primary identifiers for the component.
• COMPONENT_TYPE — the stored lookup code for the component's kind (for example, QUESTION).
• COMPONENT_TYPE_MEANING — the translated meaning of the component type, resolved from ASO_SUP_COMPONENT_TYPE.
• COMPONENT_NAME / DESCRIPTION / INSTRUCTION — display and prompt text presented to the user.
• RESPONSE_TYPE — the lookup code describing the expected response (for example, how the answer is captured).
• RESPONSE_TYPE_MEANING — populated only when COMPONENT_TYPE = 'QUESTION'; the DECODE returns an empty string for all other component types, making this column effectively conditional.
• MANDATORY_FLAG — indicates whether the component requires a response before the flow can proceed.
• Created/Last Updated WHO columns — audit trail for the component definition.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE20 — the descriptive flexfield segment columns carried through from the base view.

Common Use Cases and Queries

Typical uses include enumerating supplemental questions for a configuration or qualification flow, validating which components are mandatory, and building integration extracts that need translated type and response meanings rather than raw codes.

Sample SQL returning all question components and their response meanings:

SELECT component_id, component_name, component_type_meaning,
       response_type, response_type_meaning, mandatory_flag
 FROM apps.aso_sup_component_v
 WHERE component_type = 'QUESTION'
 ORDER BY component_name;

Because the type meaning is already resolved in the view, callers avoid re-joining FND_LOOKUP_VALUES_VL for reporting. When auditing component definitions, the WHO and DFF columns provide the governance data needed without additional joins. Filtering on mandatory_flag supports UI validation logic, while a full projection of the attribute columns supports downstream extracts that carry the flexfield segments intact.