Search Results cz_imp_intl_text




Overview
Explore in AI Chat

Overview

CZ_IMP_INTL_TEXT is a table owned by the CZ schema within the Oracle Configurator module of Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM metadata explicitly marks this object as OBSOLETE, describing it as staging data intended to be imported into (or rejected by) the production table CZ_INTL_TEXTS. In practice, it functions as an interim landing area for internationalized text records prior to validation and promotion into the live Configurator internationalization store. Because the table is flagged obsolete, it should be treated as legacy infrastructure; new development should not depend on it, and existing integrations should be reviewed for migration to the current import mechanisms used by CZ_INTL_TEXTS.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. This suggests, as a modeling suggestion, that the table is not a true hub, link, or satellite participant in a normalized Data Vault sense; it is better understood as a transient staging artifact whose rows are typically short-lived and whose relationship to its parent is directional (an import row carries a reference to the target text identifier).

Key Information Stored

The documented physical schema for this table in 12.2.2 contains 16 columns. The most significant columns are:

  • INTL_TEXT_ID — The surrogate primary key and, critically, the documented foreign key referencing CZ_INTL_TEXTS. This column ties each staging row back to the corresponding production internationalized text record.
  • TEXT_STR — The actual text string payload to be imported; the primary business content of the row.
  • RUN_ID — Identifies the specific import or batch execution that produced the row, enabling grouping and reconciliation of a single load.
  • REC_STATUS — Processing status of the staging record, indicating whether it is pending, accepted, or rejected.
  • DISPOSITION — Records the outcome or handling decision applied to the row during import processing.
  • ORIG_SYS_REF — Reference back to the originating source system record, supporting traceability.
  • DELETED_FLAG — Logical delete indicator.
  • EFF_FROM / EFF_TO — Effective date range governing validity of the text record.
  • SECURITY_MASK / EFF_MASK — Masking attributes controlling visibility and date-based filtering.
  • CHECKOUT_USER — The user holding the record under checkout, relevant to concurrent editing in Configurator.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard EBS audit columns capturing who created and last modified each row and when.

The surrogate primary key is INTL_TEXT_ID. No separate unique business-key index is documented in the supplied metadata; the foreign-key reference to CZ_INTL_TEXTS is the principal documented relationship.

Common Use Cases and Queries

Typical usage centers on monitoring import outcomes, diagnosing rejected rows, and auditing batch runs before the table was retired. A representative reporting query counts records by processing status for a given run:

  • SELECT RUN_ID, REC_STATUS, COUNT(*) FROM CZ_IMP_INTL_TEXT GROUP BY RUN_ID, REC_STATUS;
  • Identifying rejects for remediation: SELECT * FROM CZ_IMP_INTL_TEXT WHERE DISPOSITION = 'REJECTED' AND RUN_ID = :run_id;
  • Tracing a staged row to its production counterpart: SELECT a.*, b.* FROM CZ_IMP_INTL_TEXT a JOIN CZ_INTL_TEXTS b ON a.INTL_TEXT_ID = b.INTL_TEXT_ID;
  • Auditing activity over a period using the standard audit columns: SELECT * FROM CZ_IMP_INTL_TEXT WHERE CREATION_DATE >= :from_date;

Because the object is obsolete, these patterns are primarily of historical and troubleshooting value.

Related Objects

The most significant dependency is the target table itself, joined on the documented foreign key:

  • CZ_INTL_TEXTS — The production internationalized text table; CZ_IMP_INTL_TEXT.INTL_TEXT_ID references it, and it is the promotion destination for staged rows.

Additional Configurator internationalization and import components in the CZ schema operate alongside this staging table, and any custom import or interface logic that historically wrote to this table should be assessed against the current CZ_INTL_TEXTS import path. Given the obsolete status, no new dependencies should be introduced.