Search Results aso_sup_component_b_u1

Overview

ASO.ASO_SUP_COMPONENT_B is a foundational configuration table within the Oracle E-Business Suite ASO (Order Capture / Sales Foundation) schema. It stores the definition of the individual components that make up a supplemental structure used in Oracle's Sales and Order Capture flows. In practical terms, each row describes one question, prompt, or input field that the application presents when a user captures supplemental information against a sales document, quote, or order line. The table acts as the master definition list, while a companion date-tracked table (ASO_SUP_COMPONENT_TL / the _TL translation table for multilingual text) typically holds the descriptive labels.

From a data-modeling perspective, the ETRM metadata classifies this object heuristically as a standalone structure, which in Data Vault terms maps most naturally to a hub — a business-key-centric table whose rows are uniquely identified by a surrogate key with no mandatory parent reference. Because the only documented foreign key is to FND_SECURITY_GROUPS (via SECURITY_GROUP_ID), the table is self-contained and does not depend on other ASO transactional tables to exist. Rows are created through the ASO setup and administration user interfaces rather than through incidental transactional activity.

Key Information Stored

The table is documented with 32 physical columns in the 12.2.2 schema. The most significant are:

• COMPONENT_ID — the system-generated surrogate primary key (ASO_SUP_COMPONENT_B_PK). Every query that joins this table to dependent objects uses this column.
• COMPONENT_TYPE — identifies the technical type of the component (for example, a prompt, a lookup, or a value-set-driven field), governing how the component is rendered and validated.
• RESPONSE_TYPE — determines the kind of response the component expects, such as a text value, a code, or a date; this drives UI rendering and downstream validation.
• MANDATORY_FLAG — controls whether the user must supply a value for this component before the supplemental record can be saved.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, scoping the component to a security group and supporting multi-org / responsibility-based data access.
• ZD_EDITION_NAME — the edition column used by Oracle's editioning-enabled objects. It participates in the unique business key alongside COMPONENT_ID.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE20 — the standard descriptive flexfield (DFF) segments, available for customer-specific extensions without bespoke schema changes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — the standard WHO audit columns present on nearly all EBS tables, recording creation and last-modification metadata.

The unique index ASO_SUP_COMPONENT_B_U1 on (COMPONENT_ID, ZD_EDITION_NAME) is the business-key candidate for this object. The primary key, in contrast, is defined on COMPONENT_ID alone. The presence of ZD_EDITION_NAME in the unique index reflects the ZD (editioning) line of Oracle products, where the same logical entity may exist in multiple editions.

Common Use Cases and Queries

Typical usage falls into setup validation, reporting, and integration scenarios.

• Configuration auditing — listing all components and their mandatory/response settings to verify a supplemental structure against business requirements:

  SELECT COMPONENT_ID, COMPONENT_TYPE, RESPONSE_TYPE, MANDATORY_FLAG
  FROM   ASO.ASO_SUP_COMPONENT_B
  WHERE  NVL(MANDATORY_FLAG,'N') = 'Y';

• Security-group scoping — filtering components by security group to confirm visibility for a given responsibility:

  SELECT b.COMPONENT_ID, b.COMPONENT_TYPE
  FROM   ASO.ASO_SUP_COMPONENT_B b, FND_SECURITY_GROUPS g
  WHERE  b.SECURITY_GROUP_ID = g.SECURITY_GROUP_ID
  AND    g.SECURITY_GROUP_NAME = :p_group;

• DFF inspection — querying the ATTRIBUTE1–20 columns and CONTEXT to understand customer extensions, frequently needed during upgrades and regression testing.
• Interface / integration extraction — pulling the component master into external systems for quoting or CRM replication, usually by joining to the translation table for display labels.
• Change verification — reviewing COMPONENT rows where LAST_UPDATE_DATE falls within a window to confirm that a setup migration completed as expected.

Related Objects

• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; the only documented foreign key from this table.
• ASO_SUP_COMPONENT_TL / _T — the multilingual translation table that supplies the user-facing component labels; joins on COMPONENT_ID.
• ASO_SUP_STRUCTURES_B — the parent supplemental structure definition to which components are attached in the ASO supplemental model.
• ASO_SUP_STRUCTURE_COMPONENTS — the association table linking structures to components; joins on COMPONENT_ID.
• ASO_SUP_VALUES / ASO_QUOTE_SUP_VALUES — the captured response values that reference component definitions by COMPONENT_ID.
• FND_USER — joined on LAST_UPDATED_BY and CREATED_BY to resolve the names of the setup administrators.