Results for “enclosing_folder”

50+ results




Overview
Explore in AI Chat

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

Overview

CZ_USAGES_PICKER_V is a database view owned by the APPS schema within the Oracle E-Business Suite Configurator (CZ) product module. It is a presentation-layer view whose primary purpose is to supply the data set used by the Configurator "usage picker" — a selection list that lets users choose among model usages (USG objects) and other configurable object entries while navigating or editing configuration models. The name itself (USAGES_PICKER) reflects this: the view assembles human-readable labels, descriptions, object identifiers, and associated icons so that a picker component can render a list of selectable usages and entries.

The view is relevant to reporting and integration because it exposes a flat, denormalized result set that decouples callers from the normalized structure of the runtime Configurator tables. Rather than joining CZ_RP_ENTRIES, the model-usages view, the object-type lookup view, and the image-path view manually, downstream code — including Configurator UI logic, custom reports, and extensions — queries this view directly. The view is documented as VALID in the ETRM metadata for release 12.2.2, with an equivalent presence in 12.1.1.

Underlying Base Objects

The ETRM metadata records the following base objects referenced by the view:

The defining SQL is a UNION ALL. The first branch joins CZ_RP_ENTRIES to an inline model-usage subquery (aliased CZUSAGES), the object-type lookup, and the image view, constrained to OBJECT_TYPE = 'USG' and DELETED_FLAG = '0'. The second branch emits entries without an associated usage, substituting TO_NUMBER(NULL) for MODEL_USAGE_ID and NULL for the usage name and description. This design means the picker can display both usage entries and non-usage entries in one unified list.

Key Columns

  • OBJECT_ID, OBJECT_TYPE, ENCLOSING_FOLDER, NAME — identity and folder placement of the underlying repository entry.
  • DELETED_FLAG, SEEDED_FLAG — status flags; the view filters undeleted rows, but the column is still exposed.
  • MODEL_USAGE_ID — the model usage key; NULL for non-usage rows produced by the second UNION branch.
  • USAGE_NAME — the translatable usage name, the column most commonly targeted by searches such as usage_name. Populated from CZ_MODEL_USAGES_VL.NAME; NULL for non-usage rows.
  • USAGE_DESCRIPTION — the usage description; NULL for non-usage rows.
  • ALT_TEXT / OBJECT_TYPE_DESC — both map to CZ_RPOBJECTTYPES_LKV.VALUE_DESCRIPTION and provide display text for the object type.
  • IMAGE_FILE, FULL_IMAGE_PATH — icon filenames and resolved paths for picker rendering.

Common Use Cases and Queries

Typical uses include populating usage-selection LOVs, generating listings of model usages for configuration administration, and validating that every usage entry has a resolvable icon and object-type label.

List all usages by name:

  • SELECT object_id, model_usage_id, usage_name, usage_description FROM cz_usages_picker_v WHERE usage_name IS NOT NULL ORDER BY usage_name;

Search by name fragment:

  • SELECT model_usage_id, usage_name, object_type_desc FROM cz_usages_picker_v WHERE UPPER(usage_name) LIKE UPPER('%:search%');

Distinguish usage versus non-usage rows and inspect icons:

  • SELECT object_id, object_type, usage_name, image_file, full_image_path FROM cz_usages_picker_v WHERE object_type = 'USG';

Because the view relies on joins to lookup and image views, queries should be filtered where possible to avoid scanning unnecessary rows. Its stable column contract makes it a reliable integration point across both 12.1.1 and 12.2.2.