Search Results aso_sup_response_b_u1

Overview

ASO.ASO_SUP_RESPONSE_B is the base table for the Response entity used by the Sales Supplement functionality within Oracle E-Business Suite. A Response belongs to a Component and typically represents a predefined answer or selection option presented to users during the supplement capture process. In Oracle EBS 12.1.1 and 12.2.2, this table resides in the APPS_TS_TX_DATA tablespace under the ASO (Sales Orders/Order Capture) schema and carries FND Design Data registration for ASO.ASO_SUP_RESPONSE_B. Because it holds descriptive attributes that change over time alongside a stable identifier, the heuristic Data Vault classification is standalone, suggesting that this object functions primarily as a reference or hub-like entity rather than as a transactional link.

Key Information Stored

The table is defined with 29 documented columns. The most significant are listed below.

• RESPONSE_ID (NUMBER) — surrogate primary key defined by constraint ASO_SUP_RESPONSE_B_PK, uniquely identifying each Response row.
• ZD_EDITION_NAME — participates with RESPONSE_ID in the unique index ASO_SUP_RESPONSE_B_U1, supporting editioned data in 12.2.x.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant security partitioning.
• CONTEXT (VARCHAR2 30) — descriptive flexfield context identifier.
• ATTRIBUTE1–ATTRIBUTE20 (VARCHAR2 240) — descriptive flexfield segments for customer-specific extensions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns tracking record lifecycle.

The surrogate key RESPONSE_ID is distinct from the business-key candidate represented by the composite unique index ASO_SUP_RESPONSE_B_U1 (RESPONSE_ID, ZD_EDITION_NAME).

Common Use Cases and Queries

Reporting on supplement responses typically joins this table to its component parent and to descriptive flexfield segments. A representative query retrieving responses within a security group follows:

• SELECT r.RESPONSE_ID, r.CREATION_DATE, r.ATTRIBUTE1 FROM ASO.ASO_SUP_RESPONSE_B r WHERE r.SECURITY_GROUP_ID = :p_security_group;
• Validating compliance with the unique index: SELECT RESPONSE_ID, ZD_EDITION_NAME FROM ASO.ASO_SUP_RESPONSE_B GROUP BY RESPONSE_ID, ZD_EDITION_NAME HAVING COUNT(*) > 1;
• Auditing changes via WHO columns: SELECT * FROM ASO.ASO_SUP_RESPONSE_B WHERE LAST_UPDATE_DATE >= :last_run;
• Extracting flexfield data: SELECT RESPONSE_ID, CONTEXT, ATTRIBUTE1, ATTRIBUTE2 FROM ASO.ASO_SUP_RESPONSE_B;

These patterns support order capture configuration reviews, security group segregation checks, and incremental ETL extractions.

Related Objects

The documented foreign key links ASO_SUP_RESPONSE_B.SECURITY_GROUP_ID to FND_SECURITY_GROUPS, anchoring row-level security. Supporting joins commonly involve:

• FND_SECURITY_GROUPS — via SECURITY_GROUP_ID.
• FND_USER — via CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — via LAST_UPDATE_LOGIN.
• ASO_SUP_RESPONSE_TL — the translation table for Response names and descriptions.
• ASO_SUP_COMPONENTS_B — the parent Component to which responses are attached.
• FND_DESCR_FLEX_COLUMN_USAGES — descriptive flexfield metadata for the ATTRIBUTE columns.

Because the metadata classifies the object as standalone, referential fan-out is limited, and the primary dependency remains the security group and WHO audit references.