Results for “attribute_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

EGO_RESULTS_FORMAT_COLUMNS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the EGO product family, Advanced Product Catalog, which underpins the configurator, item catalog, and search infrastructure used across supply chain and order management. The view provides a consolidated, query-friendly representation of the results columns that make up a results format — the reusable layout definitions that determine which catalog attributes are returned to the user and how they are rendered in a results table.

Results formats in Advanced Product Catalog are stored as customization metadata rather than as dedicated tables. The physical attribute properties — display sequence, order sequence, order direction, column heading, and the show-total indicator — are held as attribute/value rows in the generic AK_CUSTOM_REGION_ITEMS table. EGO_RESULTS_FORMAT_COLUMNS_V pivots those property rows into a single flattened row per column, keyed by the region, attribute, and customization identifiers. This makes the view suitable for reporting, extract, and integration scenarios where the caller needs a denormalized list of format columns without writing repeated self-joins against the underlying property store.

Underlying Base Objects

The only documented base object referenced by the view is the synonym AK_CUSTOM_REGION_ITEMS, owned by APPS in the ETRM 12.2.2 metadata. The view text constructs five inline subqueries, each selecting from AK_CUSTOM_REGION_ITEMS filtered on a specific PROPERTY_NAME value:

• DISPLAY_QUERY — PROPERTY_NAME = 'DISPLAY_SEQUENCE', exposing PROPERTY_NUMBER_VALUE as DISPLAY_SEQUENCE.
• ORDER_QUERY — PROPERTY_NAME = 'ORDER_SEQUENCE', exposing PROPERTY_NUMBER_VALUE as ORDER_SEQUENCE.
• DIRECTION_QUERY — PROPERTY_NAME = 'ORDER_DIRECTION', exposing PROPERTY_VARCHAR2_VALUE as ORDER_DIRECTION.
• NAME_QUERY — resolves the display COLUMN_NAME for the attribute.
• TOTAL_QUERY — resolves SHOW_TOTAL, the flag controlling whether the column is aggregated in the results summary row.

These subqueries are joined on the common key set CUSTOMIZATION_APPLICATION_ID, CUSTOMIZATION_CODE, REGION_APPLICATION_ID, REGION_CODE, ATTRIBUTE_APPLICATION_ID, and ATTRIBUTE_CODE. Because the view is a simple join over base property rows, it inherits the security and indexing characteristics of AK_CUSTOM_REGION_ITEMS and requires no materialization of its own.

Key Columns

• CUSTOMIZATION_APPLICATION_ID, CUSTOMIZATION_CODE — identify the customization (results format) to which the column belongs.
• REGION_APPLICATION_ID, REGION_CODE — identify the region within the format; REGION_CODE is the value most commonly used to filter or group columns belonging to a particular results region.
• ATTRIBUTE_APPLICATION_ID, ATTRIBUTE_CODE — identify the catalog attribute displayed by the column.
• COLUMN_NAME — the resolved display name of the column.
• DISPLAY_SEQUENCE — numeric ordering of the column within the results layout.
• ORDER_SEQUENCE — numeric ordering used when the column participates in sorting.
• ORDER_DIRECTION — sort direction (for example ascending or descending).
• SHOW_TOTAL — indicates whether totals are displayed for the column.

Common Use Cases and Queries

Typical uses include validating a results format definition, auditing which attributes appear in a given region, and generating metadata extracts for migration or documentation. A query filtered on REGION_CODE returns the ordered column layout for that region:

• SELECT column_name, display_sequence, order_sequence, order_direction, show_total FROM ego_results_format_columns_v WHERE customization_code = :p_customization AND region_code = :p_region ORDER BY display_sequence;
• SELECT attribute_code, column_name FROM ego_results_format_columns_v WHERE region_code = :p_region AND show_total = 'Y';
• SELECT region_code, COUNT(*) FROM ego_results_format_columns_v WHERE customization_code = :p_customization GROUP BY region_code;

Because the view is read-only and defined over Advanced Product Catalog setup data, it should be used for reporting and validation only; changes to results formats must be made through the supported EGO configuration interfaces.