Search Results aso_sup_component_b_pk

Overview

ASO_SUP_COMPONENT_B is a base table in the ASO (Order Capture) schema of Oracle E-Business Suite, documented as valid in both release 12.1.1 and 12.2.2. Its ETRM description is terse—"Table for Components"—but its position within the Order Capture module indicates that it stores the definitional rows for the configurable components that make up selling models and related configuration structures. Components are the discrete building blocks presented to users during configuration; this table holds the metadata that drives how each component is rendered, whether a response is required, and what type of response is expected.

The physical schema comprises 32 columns and is owned by ASO. The heuristic Data Vault classification mined from the foreign key structure is standalone, meaning the table has no child tables referencing it through foreign keys within the documented relationship set. In Data Vault modeling terms this suggests treating ASO_SUP_COMPONENT_B as a hub-like anchor rather than as a pure satellite, though the classification is a heuristic and should be validated against actual load patterns before committing to a warehouse design.

Key Information Stored

The primary key of the table is ASO_SUP_COMPONENT_B_PK, defined on COMPONENT_ID, which serves as the surrogate identifier for each component row. A unique index, ASO_SUP_COMPONENT_B_U1, is defined on the composite of COMPONENT_ID and ZD_EDITION_NAME; the presence of ZD_EDITION_NAME in that index indicates that edition-based or version-aware storage is supported, allowing multiple editions of the same component to coexist.

• COMPONENT_ID — surrogate primary key identifying the component.
• COMPONENT_TYPE — classifies the component, driving rendering and validation behavior.
• RESPONSE_TYPE — defines the expected response format or input mode for the component.
• MANDATORY_FLAG — indicates whether a response to the component is required.
• ZD_EDITION_NAME — edition discriminator participating in the unique business key.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant or group-level data isolation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit trail columns.
• CREATION_DATE, CREATED_BY — row creation audit columns.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE20 — the DFF (descriptive flexfield) infrastructure, allowing customer-specific extensions without schema change.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios involve listing components by type, auditing which components are mandatory, and joining to security groups to validate access partitioning. A representative query pattern:

• Enumerating components filtered by type: SELECT COMPONENT_ID, COMPONENT_TYPE, RESPONSE_TYPE, MANDATORY_FLAG FROM ASO.ASO_SUP_COMPONENT_B WHERE COMPONENT_TYPE = :p_type;
• Auditing mandatory components: WHERE MANDATORY_FLAG = 'Y' to identify configuration steps that cannot be skipped.
• Security group isolation: joining on SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID to restrict results to the caller's group.
• Flexfield extraction: projecting CONTEXT and the ATTRIBUTE columns to surface customer-specific component metadata.

Because the table is classified standalone, queries are typically driven from the component side outward rather than through inbound foreign keys.

Related Objects

The documented foreign key reference identifies FND_SECURITY_GROUPS as the principal parent through SECURITY_GROUP_ID. Beyond that, the table participates in the broader ASO Order Capture configuration model, and related objects generally include:

• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID.
• ASO_SUP_COMPONENT_B_PK — the primary key constraint on COMPONENT_ID.
• ASO_SUP_COMPONENT_B_U1 — unique index on (COMPONENT_ID, ZD_EDITION_NAME).

Any downstream integration or extension should respect the edition-aware unique key and the security group partitioning to avoid duplicate or unauthorized rows.