Results for “ego_results_format_v”

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

Overview

EGO_RESULTS_FORMAT_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, part of the EGO (Advanced Product Catalog) product family. Its documented purpose is to present "all of the results formats" configured within the Advanced Product Catalog's user interface customization framework. Results formats govern how search and query results are rendered to end users in the catalog, including which columns appear, how many rows are displayed, and whether results may be imported or exported. The view is marked VALID in ETRM for both 12.1.1 and 12.2.2.

Because the underlying metadata is stored in the generic Application Kit (AK) customization model, where each property of a customization is persisted as a separate row keyed by a property name, EGO_RESULTS_FORMAT_V acts as a de-normalizing layer. It pivots the relevant properties ("RESULT_NAME", "RESULT_DESCRIPTION", "NUM_ROWS_DISPLAY", "DEFAULT_RESULT_FLAG", "SITE_ID", "WEB_USER_ID", "IMPORT_FLAG", "DATA_LEVEL") into named columns, joining localized names and descriptions and resolving lookup values. This makes the view suitable for reporting and integration, where a flat, query-friendly representation of results formats is required rather than a raw AK property model.

Underlying Base Objects

The view is defined over the following documented base objects:

• AK_CUSTOM_REGIONS (synonym) — the primary source, joined multiple times (aliased NAME_QUERY, DESC_QUERY, ROWS_QUERY, DEFAULT_QUERY, SITE_ID_QUERY, USER_ID_QUERY, LEVEL_ID_QUERY, IMPORT_QUERY, DATA_LEVEL_QUERY), once per property being pivoted.
• AK_CUSTOM_REGIONS_TL (synonym) — the translated variant, used for the RESULT_NAME and RESULT_DESCRIPTION properties, filtered by USERENV('LANG') to return the session language.
• EGO_CUSTOMIZATION_EXT (synonym) — supplies the CLASSIFICATION1, CLASSIFICATION2 and CLASSIFICATION3 segments associated with the customization.
• FND_LOOKUP_VALUES (synonym) — aliased L1, provides the DEFAULT_RESULT_FLAG_MEANING decoded meaning.
• FND_GLOBAL (package) — referenced via USERENV/FND_GLOBAL.SHORT_NAME for language resolution.

The IMPORT_FLAG and DATA_LEVEL joins use the outer-join notation (+), indicating these properties are optional; a results format may legitimately have no import flag or data level defined.

Key Columns

• NAME — the RESULT_NAME property; the display name of the results format.
• DESCRIPTION — the RESULT_DESCRIPTION property, localized.
• NUM_ROWS_DISPLAYED — the NUM_ROWS_DISPLAY property; controls how many result rows are shown.
• DEFAULT_RESULT_FLAG / DEFAULT_RESULT_FLAG_MEANING — the default-format indicator and its decoded lookup meaning.
• IMPORT_FLAG — the property the user searched for; indicates whether the results format supports import of result data.
• DATA_LEVEL — the data level associated with the format.
• SITE_ID, WEB_USER_ID, CUSTOMIZATION_LEVEL_ID — identify the ownership level of the customization (site, user, or level).
• CUSTOMIZATION_APPLICATION_ID, CUSTOMIZATION_CODE, REGION_APPLICATION_ID, REGION_CODE — composite keys identifying the customization and the region it applies to.
• CLASSIFICATION1/2/3 — extended classification segments from EGO_CUSTOMIZATION_EXT.

Common Use Cases and Queries

Typical scenarios include auditing which results formats permit import, identifying the default format for a region, and reporting on configured row limits.

To locate formats flagged for import:

• SELECT name, description, import_flag, default_result_flag FROM apps.ego_results_format_v WHERE import_flag = 'Y';

To find the default results format per customization:

• SELECT customization_code, region_code, name, default_result_flag_meaning FROM apps.ego_results_format_v WHERE default_result_flag = 'Y';

To review row-display settings and data levels across formats:

• SELECT name, num_rows_displayed, data_level, site_id, web_user_id FROM apps.ego_results_format_v ORDER BY name;

Because the view already resolves translated names and lookup meanings, these queries require no additional joins to AK or FND lookup tables, making EGO_RESULTS_FORMAT_V the preferred access point for reporting and integration against Advanced Product Catalog results formats.