Search Results cz_db_settings_u1

Overview

CZ.CZ_DB_SETTINGS is a configuration repository table within the Oracle Configurator (CZ) schema, owned by the CZ user and registered in FND Design Data as CZ.CZ_DB_SETTINGS. It stores Oracle Configurator system settings, which are organized by section names and identified by individual setting names. A representative example is the setting "OracleSequenceIncr" within section "SCHEMA", which governs the increment applied to Configurator sequence objects. In Oracle EBS 12.1.1 and 12.2.2, this table functions as a seed-data configuration store rather than a transactional or master-data entity, and it resides in the APPS_TS_SEED tablespace, consistent with its role in holding setup and reference values.

From a data modeling perspective, the heuristic Data Vault classification for this object is standalone. Because the documented metadata shows no foreign key references from CZ_DB_SETTINGS to other database objects, and it is referenced only by the internal triggers/views in the CZ schema, it is best modeled as a self-contained reference or satellite-style table rather than a hub or link. The uniqueness pattern (SECTION_NAME, SETTING_ID, ZD_EDITION_NAME) further supports treating it as a versioned reference set keyed by section and setting identity.

Key Information Stored

The table contains six documented columns. The most significant are:

• SETTING_ID (VARCHAR2(40)) — the database setting identifier, e.g., "OracleSequenceIncr". Part of the business key.
• SECTION_NAME (VARCHAR2(30)) — the grouping (section) to which the setting belongs, such as "SCHEMA". Part of the business key.
• DATA_TYPE (NUMBER) — numeric code describing the value's datatype: 1 = integer, 2 = decimal, 3 = boolean, 4 = text (consistent with CZ_PROPERTIES conventions).
• VALUE (VARCHAR2(255)) — the active value for the setting; note values are stored as text and must be cast according to DATA_TYPE.
• DESC_TEXT (VARCHAR2(255)) — a human-readable description of the setting.
• ZD_EDITION_NAME (VARCHAR2(30)) — the edition name used by the EBS 12.2 Edition-Based Redefinition (EBR) model; in 12.1.1 this column is absent or not used.

The documented primary key is CZ_DB_SETTINGS_PK (SECTION_NAME, SETTING_ID). The unique index CZ_DB_SETTINGS_U1 (SECTION_NAME, SETTING_ID, ZD_EDITION_NAME) is the business-key candidate, adding the edition dimension to the logical identity. No surrogate numeric key is documented; identity is entirely business-derived.

Common Use Cases and Queries

Typical usage involves retrieving or validating Configurator runtime settings. A common pattern reads a specific setting by section and identifier:

• Look up a single setting: SELECT VALUE FROM CZ.CZ_DB_SETTINGS WHERE SECTION_NAME = :section AND SETTING_ID = :setting;
• List all settings in a section: SELECT SETTING_ID, DATA_TYPE, VALUE, DESC_TEXT FROM CZ.CZ_DB_SETTINGS WHERE SECTION_NAME = 'SCHEMA' ORDER BY SETTING_ID;
• Filter by datatype (e.g., boolean settings): SELECT * FROM CZ.CZ_DB_SETTINGS WHERE DATA_TYPE = 3;
• Edition-aware query in 12.2.x: constrain or join on ZD_EDITION_NAME to align with the active edition.

Reporting use cases include auditing Configurator configuration drift across environments, comparing setting values between development and production, and documenting baseline seed data. Because values are stored as text, reporting queries should apply CASE logic on DATA_TYPE to convert numeric and boolean settings appropriately. Ensure queries run with appropriate CZ/APPS privileges given the seed tablespace context.

Related Objects

The documented metadata states that CZ.CZ_DB_SETTINGS does not reference any database object and is referenced only by CZ_DB_SETTINGS# (the editioning/trigger artifact within the CZ schema). Because no FK relationships are documented, related objects are inferred from the Configurator domain rather than join metadata. The most significant associated objects include:

• CZ_DB_SETTINGS# — internal editioning/trigger companion object within CZ; the sole documented dependent.
• CZ_PROPERTIES — shares the datatype-code convention (1–4) referenced by DATA_TYPE, serving as the parallel configuration/property store.
• CZ_DB_SETTINGS_PK / CZ_DB_SETTINGS_U1 — the primary key constraint and unique index that enforce identity and business-key uniqueness.
• Oracle Configurator runtime components that read settings (sequence generation, schema configuration) — consumers of the VALUES stored here.

Because the object is standalone and referenced only within the CZ schema, integrators should consult Configurator setup documentation rather than relying on relational joins when extending or reporting on this table.