Search Results aso_sup_comp_resp_map




Overview
Explore in AI Chat

Overview

ASO_SUP_COMP_RESP_MAP is a transactional mapping table owned by the ASO schema (Order Capture) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the relationship between configurable components and their predefined responses. In Oracle Order Capture and Configurator flows, a component represents a selectable element within a model, while a response represents a legal value or option a user can choose for that component. The table supports one-to-many cardinality, meaning a single component may be associated with one or many predefined responses, with DISPLAY_SEQUENCE controlling the presentation order of those responses in the user interface.

From a data modeling perspective, the mined FK structure classifies this object heuristically as standalone within a Data Vault construct. Because the table persists the association between two business entities (component and response) and carries descriptive attributes such as display sequence, it behaves in practice much like a link with satellite-like descriptive columns. The classification is offered as a modeling suggestion rather than a documented ETRM fact.

Key Information Stored

The table contains 32 documented columns. The most significant are:

  • COMPONENT_RESPONSE_ID — the surrogate primary key, enforced through ASO_SUP_COMP_RESP_MAP_PK. It uniquely identifies each component-to-response association record.
  • COMPONENT_ID — references the configurable component to which responses are attached.
  • RESPONSE_ID — references the predefined response value associated with the component.
  • DISPLAY_SEQUENCE — controls the ordering in which responses appear for a component.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, used for multi-tenant data segregation and access control.
  • ZD_EDITION_NAME — participates in the unique business-key index ASO_SUP_COMP_RESP_MAP_U1 (COMPONENT_RESPONSE_ID, ZD_EDITION_NAME), supporting edition-based or versioned data.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns capturing the last modification context.
  • CREATION_DATE, CREATED_BY — audit columns recording initial record creation.
  • CONTEXT and ATTRIBUTE1 through ATTRIBUTE20 — the standard EBS descriptive flexfield (DFF) storage columns, allowing customer-specific extensions without schema changes.

The unique index ASO_SUP_COMP_RESP_MAP_U1 on (COMPONENT_RESPONSE_ID, ZD_EDITION_NAME) represents the business-key candidate alongside the surrogate PK.

Common Use Cases and Queries

Typical usage involves retrieving all responses defined for a given component, validating that a response is legal for a component, or reporting on response configurations. A representative query to list ordered responses for a component is:

  • SELECT response_id, display_sequence FROM aso.aso_sup_comp_resp_map WHERE component_id = :component_id ORDER BY display_sequence;
  • Joining to FND_SECURITY_GROUPS via SECURITY_GROUP_ID to enforce row-level security in custom reports.
  • Auditing configuration changes using LAST_UPDATE_DATE and LAST_UPDATED_BY ranges.
  • Extracting DFF attributes (ATTRIBUTE1–ATTRIBUTE20) for customer-specific reporting on configurable options.

These patterns support order capture validation logic, configurator UI rendering, and data migration or comparison exercises during upgrades from 12.1.1 to 12.2.2.

Related Objects

  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for access control.
  • ASO component definition tables — referenced through COMPONENT_ID.
  • ASO response definition tables — referenced through RESPONSE_ID.
  • Order Capture / Configurator runtime views and APIs — consume this mapping to render available responses.
  • Standard EBS audit and DFF metadata objects — support the CONTEXT and ATTRIBUTE columns.