Search Results aso_sup_sect_comp_map_n1

Overview

The table ASO.ASO_SUP_SECT_COMP_MAP is an Oracle E-Business Suite (EBS) reference table belonging to the ASO (Oracle Advanced Supply Chain Planning / Order Capture) schema. Its documented purpose is to store Section and Component mapping information, supporting the configuration model in which a business section may contain one or many components, and a section may itself contain a sub-section (a sub-section being another section instance). This mapping governs how structured content—sections, sub-sections, components, and responses—is assembled and presented to users in the ASO framework. The table resides in the APPS_TS_TX_DATA tablespace and is classified as VALID, and is registered in FND Design Data under ASO.ASO_SUP_SECT_COMP_MAP.

From a dimensional modeling perspective, the heuristic Data Vault classification for this object is standalone, meaning it does not behave strictly as a hub, link, or satellite in the mined FK structure. It should be treated as a standalone mapping table that relates sections to components, rather than as part of a formal Data Vault hub-and-spoke association.

Key Information Stored

Each row of ASO_SUP_SECT_COMP_MAP defines the relationship between a section and a component, along with presentation and response attributes. The most significant columns are:

• SECT_COMP_MAP_ID — the surrogate primary key (ASO_SUP_SECT_COMP_MAP_PK), uniquely identifying each mapping row. It is also the leading column of the unique index ASO_SUP_SECT_COMP_MAP_U1, making it a business-key candidate together with ZD_EDITION_NAME.
• SECTION_ID — identifies the parent section to which the mapping belongs (indexed in ASO_SUP_SECT_COMP_MAP_N1).
• COMPONENT_ID — identifies the component mapped to the section (also indexed by _N1).
• SUB_SECTION_ID and CHILD_COMPONENT_ID — support nested structures, allowing a section to reference a sub-section or a child component.
• PRESENTATION_STYLE and SECTION_COMPONENT_TYPE — control how the section/component is rendered and what category it belongs to.
• DISPLAY_SEQUENCE — determines the display ordering of components within a section.
• DEFAULT_RESPONSE_ID — references a default response associated with the mapped component.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing access-control partitioning.
• Standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY) and descriptive flexfield segments (ATTRIBUTE1–ATTRIBUTE20, CONTEXT, ZD_EDITION_NAME) provide audit and extensibility support.

Common Use Cases and Queries

Typical uses include retrieving the ordered component list for a section, resolving sub-section hierarchies, and reporting on presentation configuration.

• List components for a section, ordered for display:
  SELECT COMPONENT_ID, DISPLAY_SEQUENCE, PRESENTATION_STYLE FROM ASO_SUP_SECT_COMP_MAP WHERE SECTION_ID = :section_id ORDER BY DISPLAY_SEQUENCE;
• Resolve sub-section hierarchy:
  SELECT SECTION_ID, SUB_SECTION_ID, CHILD_COMPONENT_ID FROM ASO_SUP_SECT_COMP_MAP WHERE SUB_SECTION_ID IS NOT NULL;
• Retrieve default responses:
  SELECT SECT_COMP_MAP_ID, DEFAULT_RESPONSE_ID FROM ASO_SUP_SECT_COMP_MAP WHERE DEFAULT_RESPONSE_ID IS NOT NULL;
• Security-scoped reporting using SECURITY_GROUP_ID joined to FND_SECURITY_GROUPS.

Related Objects

The following objects are the most significant dependencies based on documented relationships:

• FND_SECURITY_GROUPS — referenced by ASO_SUP_SECT_COMP_MAP.SECURITY_GROUP_ID.
• ASO_SUP_INSTANCE_VALUE — references this table via SECT_COMP_MAP_ID.
• Sections and components referenced by SECTION_ID, COMPONENT_ID, SUB_SECTION_ID, and CHILD_COMPONENT_ID within the ASO configuration model.
• The unique index ASO_SUP_SECT_COMP_MAP_U1 and non-unique index ASO_SUP_SECT_COMP_MAP_N1, which support primary access and section/component lookups respectively.

Collectively these objects define how ASO sections and components are mapped, presented, and consumed by dependent instance values.