Search Results cz_intl_texts_pk




Overview
Explore in AI Chat

Overview

The CZ.CZ_INTL_TEXTS table is a core repository for internationalized text strings within Oracle E-Business Suite 12.1.1 and 12.2.2. It is a foundational data object for the Oracle Configurator (CZ) module, which is part of the Oracle Supply Chain Management suite. The table's primary function is to store translatable text entries that can be referenced by other Configurator entities, enabling the presentation of user interfaces, model component names, descriptions, and messages in multiple languages. Its design supports a centralized, reusable approach to text management, which is critical for deploying configurable products in global markets. The table's status is marked as VALID but also OBSOLETE in the provided metadata, indicating it remains operational in these EBS versions but may have been superseded by a different architecture in later releases.

Key Information Stored

The table's structure is designed to manage text lifecycles and auditability. The most critical columns include:

  • INTL_TEXT_ID (NUMBER(15), PK): The unique, system-generated identifier for each text string. This is the primary key column for the CZ_INTL_TEXTS_PK index.
  • TEXT_STR (VARCHAR2(255)): The actual translatable text string, with a maximum length of 255 characters.
  • DELETED_FLAG (VARCHAR2(1)): A soft-delete indicator. A value of '1' marks the record for purging, allowing for non-destructive removal.
  • ORIG_SYS_REF (VARCHAR2(255)): Holds key information to identify the record's origin in a source database, crucial for data import and migration processes.
  • Standard Who Columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for audit tracking.
  • Reserved Columns: Several columns, including EFF_FROM, EFF_TO, SECURITY_MASK, EFF_MASK, and CHECKOUT_USER, are documented as "Not currently used," suggesting they were designed for future functionality like effective dating, security, and checkout mechanisms that were not implemented.

Common Use Cases and Queries

This table is primarily accessed for translation management, data cleansing, and audit reporting within the Configurator environment. A common scenario involves identifying active text strings for a translation extract or validating data post-import. The following query pattern retrieves all non-deleted text entries created within a specific date range, which is useful for auditing recent additions:

SELECT INTL_TEXT_ID, TEXT_STR, CREATION_DATE, CREATED_BY
FROM CZ.CZ_INTL_TEXTS
WHERE DELETED_FLAG != '1'
AND CREATION_DATE BETWEEN :p_start_date AND :p_end_date
ORDER BY CREATION_DATE DESC;

Another critical use case is reconciling imported data. The ORIG_SYS_REF column can be used to trace the source of records, as shown in this query to find potential duplicates or verify imports:
SELECT ORIG_SYS_REF, COUNT(*)
FROM CZ.CZ_INTL_TEXTS
WHERE ORIG_SYS_REF IS NOT NULL
GROUP BY ORIG_SYS_REF
HAVING COUNT(*) > 1;

Related Objects

Based on the provided dependency information, the CZ.CZ_INTL_TEXTS table has no documented foreign key relationships in the ETRM metadata extract. It is explicitly stated that "CZ.CZ_INTL_TEXTS does not reference any database object" and "CZ.CZ_INTL_TEXTS is not referenced by any database object." This suggests that within the scope of the documented schema, it may be accessed programmatically via the Configurator's application logic or APIs rather than through direct, database-enforced referential integrity constraints. The primary structural relationship is with its own unique index, CZ_INTL_TEXTS_PK, which enforces uniqueness on the INTL_TEXT_ID column.