Results for “data_level_query”

12 results




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

Overview

APPS.EGO_RESULTS_FORMAT_V is a reporting and integration view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes the definition of saved search result formats used by the Oracle Product Information Management (PIM) / Product Data Hub customization framework. Each row represents a single named result format associated with a customization region, consolidating the format's name, description, row display limit, default-result indicator, site and user scoping, and import/data-level attributes into a single denormalized projection. The view is typically consumed by Oracle Application Framework (OAF) pages and by custom extensions that need to enumerate or validate the result formats configured for a given customization code and region.

The identifier "data_level_query" corresponds to an inline alias within the view text: a self-join of AK_CUSTOM_REGIONS restricted to PROPERTY_NAME = 'DATA_LEVEL', whose PROPERTY_VARCHAR2_VALUE is surfaced as the DATA_LEVEL column. Because DATA_LEVEL is resolved through an outer join (DATA_LEVEL_QUERY.PROPERTY_NAME (+) = 'DATA_LEVEL'), the column is nullable for formats that do not define a data level.

Underlying Base Objects

The view is defined over four documented base objects plus one package:

Key Columns

  • CUSTOMIZATION_APPLICATION_ID / CUSTOMIZATION_CODE — identity of the owning customization.
  • REGION_APPLICATION_ID / REGION_CODE — the region to which the result format belongs.
  • NAME / DESCRIPTION — user-visible label and long description of the format (language-dependent).
  • NUM_ROWS_DISPLAYED — maximum rows rendered per result set.
  • DEFAULT_RESULT_FLAG / DEFAULT_RESULT_FLAG_MEANING — flag indicating the default format, with its lookup meaning.
  • CLASSIFICATION1, CLASSIFICATION2, CLASSIFICATION3 — extension classifications from EGO_CUSTOMIZATION_EXT.
  • SITE_ID / WEB_USER_ID / CUSTOMIZATION_LEVEL_ID — scoping metadata for site-level, user-level, or level-specific customizations.
  • IMPORT_FLAG / DATA_LEVEL — import applicability and the data level governing result visibility; both are outer-joined and may be NULL.

Common Use Cases and Queries

Typical scenarios include auditing default result formats per region, verifying row limits before performance tuning, and driving custom OAF or BI Publisher reports over saved-search configurations. A representative query lists formats for a customization code:

  • SELECT name, description, num_rows_displayed, default_result_flag_meaning, data_level FROM apps.ego_results_format_v WHERE customization_code = :p_code AND region_code = :p_region ORDER BY default_result_flag DESC, name;
  • Identifying formats where DATA_LEVEL is populated to enforce row-level data restriction.
  • Joining to AK_CUSTOM_REGIONS or EGO_CUSTOMIZATION_EXT for additional property details not projected by the view.