Search Results aso_sup_presentation_style

Overview

The view APPS.ASO_SUP_SECT_COMP_V is a reporting and integration construct within the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 Oracle Application Object Library and Order Capture / Sales foundation schema. It exposes the mapping between a Supplementary Section and the Components or sub-sections attached to that section, together with the descriptive names and lookup meanings required to render them in user interfaces, concurrent programs, and downstream integrations. The view is owned by APPS and is built from the base mapping table ASO_SUP_SECT_COMP_MAP joined against several supplementary "VL" views for section, component, and response descriptions, plus two instances of FND_LOOKUP_VALUES_VL to decode presentation style and section component type values. Because it encapsulates the lookup translation and outer-joins the default response, it is a convenient read-only source for customers who need to query section-component configuration without writing the joins themselves.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, this view is defined over the following objects:

• ASO_SUP_SECT_COMP_MAP (SYNONYM) — the driving table holding the section-to-component mapping, section_component_type, display_sequence, default_response_id, presentation_style, child_component_id, sub_section_id, and the descriptive flexfield attribute columns.
• ASO_SUP_SECTION_VL (VIEW) — provides the section name and section description.
• ASO_SUP_COMPONENT_VL (VIEW) — provides the component name and component description.
• ASO_SUP_RESPONSE_VL (VIEW) — provides the default response name; joined via an outer ((+)) join on default_response_id = response_id, so rows without a default response are still returned.
• FND_LOOKUP_VALUES_VL (VIEW) — used twice, aliased D and E, to resolve the meaning of the presentation_style (lookup type ASO_SUP_PRESENTATION_STYLE) and the section_component_type (lookup type ASO_SUP_SECTION_COMPONENT_TYPE).

The joins to the VL views are inner joins on component_id and section_id, while the lookup joins are inner joins on the lookup_code. Only the response join is outer, meaning every section-component mapping is returned regardless of whether a default response is assigned.

Key Columns

• SECT_COMP_MAP_ID, SECTION_ID, COMPONENT_ID — primary identifiers for the mapping row and its parent section and component.
• SECTION_NAME, SECTION_DESCRIPTION — descriptive text of the owning supplementary section.
• NAME, DESCRIPTION — conditionally populated via DECODE: the component name/description when section_component_type = 'COMPONENT', otherwise an empty string for other mapping types.
• SECTION_COMPONENT_TYPE, SECTION_COMPONENT_TYPE_MEANING — the mapping type code and its translated lookup meaning; this is the column directly associated with the search term aso_sup_section_component_type.
• PRESENTATION_STYLE, PRESENTATION_STYLE_MEANING — display style code and its translated meaning; the meaning is populated only for COMPONENT rows.
• DISPLAY_SEQUENCE — ordering of the component within the section.
• CHILD_COMPONENT_ID, SUB_SECTION_ID — references for hierarchical/child mapping structures.
• DEFAULT_RESPONSE_ID, DEFAULT_VALUE — the default response identifier and the resolved response name.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE20 — descriptive flexfield context and segment columns carried through from the base mapping table.

Common Use Cases and Queries

Typical uses include configuration reporting for supplementary sections, integration extracts feeding external sales or configuration systems, and validation of presentation styles prior to deployment. A common query retrieves all components for a given section, ordered by display sequence:

• SELECT section_name, name, section_component_type_meaning, presentation_style_meaning, display_sequence FROM apps.aso_sup_sect_comp_v WHERE section_id = :p_section_id ORDER BY display_sequence;
• SELECT section_component_type, section_component_type_meaning, COUNT(*) FROM apps.aso_sup_sect_comp_v GROUP BY section_component_type, section_component_type_meaning; — audits the distribution of component types, leveraging the search term lookup.
• SELECT v.* FROM apps.aso_sup_sect_comp_v v WHERE v.default_response_id IS NULL; — identifies mappings lacking a default response, exploiting the outer join in the definition.

Because the view relies on APPS-owned synonyms and VL views, callers should reference it as APPS.ASO_SUP_SECT_COMP_V and ensure the corresponding lookup types remain valid, as the lookup joins are inner joins and rows with missing lookup codes will be excluded from the result set.