Search Results referenced_usage_flag




Overview

APPS.CZ_RULETYPE_IMAGES_V is a configuration-layer view in the Oracle E-Business Suite product family commonly referred to as Oracle Configurator / ETRM (Enterprise Territory and Rules Management). It exposes image metadata associated with rule types, resolving the physical file location and descriptive label text needed by the Configurator user interface to render rule-type imagery. The view is owned by the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2, where it is typically consumed by Oracle Forms-based setup screens, OAF pages, and reporting or integration routines that need to locate image assets by rule type.

A distinguishing characteristic of this view is the synthetic column referenced_usage_flag. This column does not exist as a stored attribute on any base table; it is derived within the view's SQL using a DECODE expression over CZ_UI_PATHED_IMAGES_V.IMAGE_USAGE_CODE. Users searching for "referenced_usage_flag" are therefore looking at a computed indicator rather than a persisted database column, which is an important distinction when tracing data lineage or attempting to filter on that value in downstream queries.

Underlying Base Objects

The view is defined over two documented base objects, both of which are themselves views:

  • CZ_UI_PATHED_IMAGES_V — supplies image usage code, entity code, image file, and full image path. It is the driving source in the join, filtered by UI_DEF_ID = 0, image usage codes 20 and 21, and DELETED_FLAG = '0'.
  • CZ_DETAILEDRULETYPES_LKV — supplies the lookup label, data value, and description used for the entity associated with each image. It is joined with the outer-join operator (+) on NUMERIC_ID_VALUE = ENTITY_CODE, so images without a matching rule-type lookup row are still returned, with label columns null.

No base tables are referenced directly. All access is mediated through these two views, which in turn resolve to the underlying CZ_UI_PATHED_IMAGES and CZ_DETAILEDRULETYPES lookup structures.

Key Columns

  • IMAGE_USAGE_CODE — numeric discriminator indicating the purpose of the image; only codes 20 and 21 are eligible for this view.
  • ENTITY_CODE — identifier linking the image to a detailed rule type; joined to NUMERIC_ID_VALUE.
  • referenced_usage_flag — computed via DECODE(IMAGE_USAGE_CODE, 20, '0', 21, '1'). It maps usage code 20 to flag value '0' and code 21 to flag value '1', enabling consumers to distinguish the two supported usage roles without inspecting the raw numeric code.
  • IMAGE_FILE and FULL_IMAGE_PATH — the logical file name and the resolved absolute path used when rendering the image.
  • DATA_VALUE, VALUE_LABEL, ALT_TEXT — lookup-derived descriptive fields; VALUE_DESCRIPTION is aliased to ALT_TEXT for accessibility rendering.

Common Use Cases and Queries

Typical usage includes generating lists of rule-type images for a given usage role, validating that every configured rule type has an associated image, and supplying alt text to UI rendering layers.

SELECT referenced_usage_flag,
       entity_code,
       image_file,
       full_image_path,
       alt_text
FROM   apps.cz_ruletpe_images_v
WHERE  referenced_usage_flag = '1';

Because referenced_usage_flag is a DECODE alias, filtering on it is valid in the outer query but cannot be pushed into the base view. A join to CZ_DETAILEDRULETYPES_LKV is already present, so label and description values are available without additional joins. Note the outer join on the lookup: consumers should tolerate null DATA_VALUE and ALT_TEXT for entity codes with no corresponding rule-type lookup entry.

For audits of orphaned or missing imagery, a query comparing rule-type entities against this view and testing for null FULL_IMAGE_PATH is a standard practice.