Search Results aso_sup_response_b_pk

Overview

ASO_SUP_RESPONSE_B is the base table that stores Response records for the Sales Supplement functionality within the Order Capture (ASO) module of Oracle E-Business Suite. In the Sales Supplement model, a supplement groups a set of questions presented to a user during order entry, and each response captured against those questions is persisted at the detail level. ASO_SUP_RESPONSE_B provides that persistent detail storage, forming the header-level (base) record for a response. The "B" suffix follows Oracle Applications convention, indicating the base table that holds the primary entity attributes, typically paired with a "_TL" table when translatable columns are required. The object has a status of VALID in the documented 12.2.2 schema, which comprises 29 columns owned by the ASO schema.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. That classification is a modeling suggestion rather than a delivered architectural commitment; it reflects the absence of any modeled parent-child foreign key relationships. Practically, the table behaves as a hub-like anchor keyed on its surrogate identifier, with descriptive and audit columns carried alongside it.

Key Information Stored

The primary key of the table is defined by the constraint ASO_SUP_RESPONSE_B_PK, which covers the RESPONSE_ID column. RESPONSE_ID is the surrogate identifier for each response record and is the column through which child tables and referential relationships are joined. A separate unique index, ASO_SUP_RESPONSE_B_U1, is defined over the combination of RESPONSE_ID and ZD_EDITION_NAME, which serves as the documented business-key candidate and also reflects the editioning construct used in the 12.2.x schema.

Beyond the keys, the table carries the standard Oracle EBS who-columns used for auditing and concurrency: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The CONTEXT column holds the developer descriptive flexfield context value, while ATTRIBUTE1 through ATTRIBUTE20 provide the descriptive flexfield segment storage that allows implementers to extend the response entity without schema modification. The SECURITY_GROUP_ID column participates in the application's data security and multi-tenant access model. ZD_EDITION_NAME is present as part of the editioning infrastructure applied across the 12.2.x data model. Together these columns allow a response to be identified, audited, secured by group, and extended through flexfields.

Common Use Cases and Queries

The most frequent access pattern is retrieval of all responses associated with a given sales supplement context during order entry or order review, followed by joins to the child response detail tables that carry the actual answer values. A representative query pattern is:

• SELECT RESPONSE_ID, CREATION_DATE, LAST_UPDATE_DATE, SECURITY_GROUP_ID FROM ASO.ASO_SUP_RESPONSE_B WHERE RESPONSE_ID = :p_response_id;
• Filtering by flexfield context, for example WHERE CONTEXT = :context_code, to isolate responses belonging to a particular configured supplement.
• Audit and lineage reporting using CREATED_BY and LAST_UPDATED_BY against FND_USER, typically for troubleshooting who entered or modified a supplement response.
• Extract and reporting queries that pivot ATTRIBUTE1 through ATTRIBUTE20 into business-friendly columns where the flexfield segments have been mapped to meaningful data points.

Because the table is standalone with respect to modeled foreign keys, joins are driven by RESPONSE_ID into the associated "_TL" and detail tables rather than through database-enforced parent constraints.

Related Objects

The documented foreign key relationship references FND_SECURITY_GROUPS through SECURITY_GROUP_ID, linking each response to the security group that governs visibility of the record. Key related objects include:

• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID = SECURITY_GROUP_ID, controls data access partitioning.
• ASO_SUP_RESPONSE_TL — the translatable companion table, joined on RESPONSE_ID, holding language-specific response text.
• ASO_SUP_RESPONSE_VALUES / response detail tables — child records joined on RESPONSE_ID that store the individual answers.
• ASO_SUP_QUESTIONS_B and its _TL table — the definitions of the questions to which these responses correspond.
• ASO_SUP_SUPPLEMENTS_B — the supplement header that groups questions and responses for a given sales context.
• FND_USER — referenced through CREATED_BY and LAST_UPDATED_BY for auditing.
• FND_FLEX_VALUES / FND_DESCR_FLEX_COLUMN_USAGES — for interpreting CONTEXT and ATTRIBUTE1–20 flexfield content.

These objects collectively support the capture, retrieval, display, and audit of Sales Supplement responses across the order capture lifecycle in Oracle EBS 12.1.1 and 12.2.2.