Search Results aso_sup_comp_resp_map_n1

Overview

ASO.ASO_SUP_COMP_RESP_MAP is a transactional configuration table in the Oracle E-Business Suite Order Capture / Oracle Advanced Pricing foundation schema (ASO). Its documented purpose is to map Components to predefined Responses, reflecting the business rule that a single component may be associated with one or many predefined responses. Records in this table therefore drive which responses are selectable or validated against a given component during order capture, configuration, and pricing flows.

The table is owned by the ASO schema, is marked VALID, and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Its indexes are stored separately in APPS_TS_TX_IDX. The table carries a full set of Standard Who audit columns and a 30-character CONTEXT column paired with twenty descriptive flexfield attribute segments, confirming that it is a flexfield-enabled transactional table subject to the standard EBS audit and DFF conventions.

From a Data Vault modeling perspective (heuristic Classification: standalone), this object behaves most naturally as a link-style association between components and responses, rather than as a pure hub or satellite. Because the metadata identifies no parent-child hierarchy beyond the component-response association, the standalone classification is a reasonable heuristic rather than a definitive statement. The primary key is ASO_SUP_COMP_RESP_MAP_PK, defined on COMPONENT_RESPONSE_ID.

Key Information Stored

The most significant columns documented for this table are:

• COMPONENT_RESPONSE_ID (NUMBER) — The surrogate primary key and the leading column of the unique index ASO_SUP_COMP_RESP_MAP_U1. It uniquely identifies each component-to-response association.
• COMPONENT_ID (NUMBER) — The identifier of the component being mapped; this is the business-key column indexed by the non-unique index ASO_SUP_COMP_RESP_MAP_N1, supporting lookups of all responses for a component.
• RESPONSE_ID (NUMBER) — The identifier of the predefined response attached to the component.
• DISPLAY_SEQUENCE (NUMBER) — Controls the ordering in which multiple responses for one component are presented.
• SECURITY_GROUP_ID (NUMBER) — References FND_SECURITY_GROUPS and enforces multi-org / security-group scoping.
• ZD_EDITION_NAME — Appears as the second column of the unique index ASO_SUP_COMP_RESP_MAP_U1, indicating edition-based support for the uniqueness rule.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard Who audit columns tracking who created and last modified each row, with foreign keys to FND_USER and FND_LOGINS.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE20 (VARCHAR2(240) each) — Descriptive flexfield segments available for customer-specific extension.

The unique business-key candidate is ASO_SUP_COMP_RESP_MAP_U1 (COMPONENT_RESPONSE_ID, ZD_EDITION_NAME), while ASO_SUP_COMP_RESP_MAP_N1 (COMPONENT_ID) provides the primary retrieval path.

Common Use Cases and Queries

Typical scenarios include retrieving all predefined responses for a given component, rendering responses in display order during order configuration, and auditing the response set attached to a component for a specific security group. A basic retrieval pattern is:

• SELECT COMPONENT_ID, RESPONSE_ID, DISPLAY_SEQUENCE FROM ASO.ASO_SUP_COMP_RESP_MAP WHERE COMPONENT_ID = :p_component_id ORDER BY DISPLAY_SEQUENCE;
• SELECT RESPONSE_ID, DISPLAY_SEQUENCE FROM ASO.ASO_SUP_COMP_RESP_MAP m WHERE m.COMPONENT_ID = :p_component_id AND m.SECURITY_GROUP_ID = :p_group_id;
• Validation query confirming uniqueness on the business key: SELECT COMPONENT_RESPONSE_ID FROM ASO.ASO_SUP_COMP_RESP_MAP WHERE COMPONENT_RESPONSE_ID = :p_id;

Reporting uses include configuration dependency reports showing which components are constrained to which responses, DFF-based extension reports over ATTRIBUTE1–ATTRIBUTE20, and change-audit reports driven by LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

• FND_SECURITY_GROUPS — Referenced by ASO_SUP_COMP_RESP_MAP.SECURITY_GROUP_ID, the documented foreign key relationship.
• FND_USER — Referenced indirectly by CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — Referenced by LAST_UPDATE_LOGIN.
• ASO.ASO_SUP_COMPONENTS — Parent of the COMPONENT_ID column used throughout component definition logic.
• ASO.ASO_SUP_RESPONSES — Source of the RESPONSE_ID values referenced here.
• Order Capture / Advanced Pricing configuration APIs — Consume this mapping when populating or validating selectable responses.

Because the table is documented as standalone with a single explicit foreign key, joins to component and response masters rely on the COMPONENT_ID and RESPONSE_ID columns rather than documented FK constraints, and should be verified against the specific 12.1.1 or 12.2.2 instance in use.