Search Results presentation_style

Overview

ASO_SUP_SECT_COMP_V is an APPS-owned, VALID database view within the ASO (Order Capture) product family of Oracle EBS 12.1.1 and 12.2.2. It exposes the mapping between supplementary sections and the components they contain, denormalizing descriptive names and lookup meanings so that the underlying configuration can be consumed directly by reporting, integration, and UI inquiry layers without additional joins.

The view is defined over ASO_SUP_SECT_COMP_MAP, the transactional mapping entity, and enriches each row with section, component, and response descriptions, plus decoded lookup meanings for the presentation style and section component type. Because EBS UI pages for section/component configuration frequently filter on presentation style, this view is the canonical read-only source when reproducing or auditing the screen configuration outside the form.

Underlying Base Objects

• ASO_SUP_SECT_COMP_MAP (SYNONYM): primary driving table holding SECTION_ID, COMPONENT_ID, SECTION_COMPONENT_TYPE, DISPLAY_SEQUENCE, PRESENTATION_STYLE, DEFAULT_RESPONSE_ID, and the DFF context/attribute columns.
• ASO_SUP_SECTION_VL (VIEW): supplies SECTION_NAME and DESCRIPTION (aliased SECTION_DESCRIPTION).
• ASO_SUP_COMPONENT_VL (VIEW): supplies COMPONENT_NAME and DESCRIPTION for rows where SECTION_COMPONENT_TYPE = 'COMPONENT'; otherwise these decode to an empty string.
• ASO_SUP_RESPONSE_VL (VIEW): outer-joined on DEFAULT_RESPONSE_ID, yielding RESPONSE_NAME as DEFAULT_VALUE.
• FND_LOOKUP_VALUES_VL (VIEW), aliased D: decodes PRESENTATION_STYLE against lookup type ASO_SUP_PRESENTATION_STYLE into PRESENTATION_STYLE_MEANING.
• FND_LOOKUP_VALUES_VL (VIEW), aliased E: decodes SECTION_COMPONENT_TYPE against lookup type ASO_SUP_SECTION_COMPONENT_TYPE into SECTION_COMPONENT_TYPE_MEANING.

Key Columns

• SECT_COMP_MAP_ID: surrogate primary key of the mapping row; ROW_ID is the rowid.
• SECTION_ID / COMPONENT_ID: foreign keys to the section and component definitions.
• SECTION_COMPONENT_TYPE: discriminator ('COMPONENT' or other values) controlling whether component name/description are populated.
• PRESENTATION_STYLE / PRESENTATION_STYLE_MEANING: lookup code and its decoded meaning (lookup type ASO_SUP_PRESENTATION_STYLE) — the column users most commonly query, e.g. to identify components rendered as a specific control style.
• DISPLAY_SEQUENCE: numeric ordering within the section.
• CHILD_COMPONENT_ID, SUB_SECTION_ID, DEFAULT_RESPONSE_ID: self-referencing and sub-section linkages; DEFAULT_VALUE derives from ASO_SUP_RESPONSE_VL.
• WHO columns and ATTRIBUTE1–15/CONTEXT: standard audit fields and descriptive flexfield segments.

Common Use Cases and Queries

Typical scenarios include auditing which presentation style a component uses, reproducing the section/component tree, and extracting configuration for migration.

• Filter by a specific presentation style:

SELECT section_name, name, presentation_style_meaning, display_sequence
FROM   aso_sup_sect_comp_v
WHERE  presentation_style = :p_style
ORDER  BY section_id, display_sequence;

• List components within a section:

SELECT name, description, section_component_type_meaning, default_value
FROM   aso_sup_sect_comp_v
WHERE  section_id = :p_section_id
AND    section_component_type = 'COMPONENT'
ORDER  BY display_sequence;

• Report presentation style usage counts across sections for configuration review.

Because FND lookup joins are inner joins on PRESENTATION_STYLE and SECTION_COMPONENT_TYPE, rows whose lookup codes are missing or end-dated may be excluded; include lookup-maintenance checks when result counts appear unexpectedly low.