Search Results sect_comp_map_id




Overview

ASO_SUP_SECT_COMP_MAP is an Order Capture (ASO) module table that stores the mapping between sections and components used within Oracle EBS order capture and configuration workflows. Its documented purpose is "for Section and Component mapping purpose," indicating that it defines how configurable sections, sub-sections, and their constituent components are organized, presented, and sequenced when an order line is configured. The table resides in the ASO schema and is valid in both Oracle EBS 12.1.1 and 12.2.2.

From a modeling perspective, the supplied metadata classifies this object heuristically as a standalone entity based on its foreign-key structure. It carries a single documented outbound foreign key to FND_SECURITY_GROUPS via SECURITY_GROUP_ID, and it is referenced by ASO_SUP_INSTANCE_VALUE via SECT_COMP_MAP_ID. Because the table holds descriptive attributes, presentation metadata, and audit columns, it functions in practice as a configuration detail or satellite-style object anchored on its own primary key rather than a pure junction between two hubs.

Key Information Stored

The table contains 37 documented columns. The most significant are summarized below.

Distinguishing the surrogate key (SECT_COMP_MAP_ID alone in the PK) from the business-key candidate (SECT_COMP_MAP_ID with ZD_EDITION_NAME in the U1 unique index) is essential for correct joins and for any direct data manipulation.

Common Use Cases and Queries

Typical scenarios include investigating why a particular component appears, or fails to appear, in a configuration UI, and tracing which instances reference a given section-component mapping.

SELECT sect_comp_map_id, section_id, component_id,
       presentation_style, display_sequence, section_component_type
FROM   aso.aso_sup_sect_comp_map
WHERE  section_id = :section_id
ORDER  BY display_sequence;

To trace downstream instance usage:

SELECT m.sect_comp_map_id, i.*
FROM   aso.aso_sup_sect_comp_map m,
       aso.aso_sup_instance_value i
WHERE  m.sect_comp_map_id = i.sect_comp_map_id
AND    m.component_id = :component_id;

Reporting use cases include cataloging presentation configuration by section, auditing display sequences for UI consistency, and validating that no orphaned mapping records exist relative to their security group.

Related Objects

  • ASO_SUP_INSTANCE_VALUE — references this table via SECT_COMP_MAP_ID, linking runtime instance values to their mapping definition.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID, providing the security partitioning for each mapping record.
  • ASO_SUP_SECT_COMP_MAP_PK — the primary key constraint on SECT_COMP_MAP_ID.
  • ASO_SUP_SECT_COMP_MAP_U1 — the composite unique index on SECT_COMP_MAP_ID and ZD_EDITION_NAME.
  • ASO module section and component definition tables — the SECTION_ID and COMPONENT_ID values resolve against the ASO configuration definition objects that provide the referenced sections and components.