Results for “cz_archives”

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

Overview

The CZ_ARCHIVES table resides in the CZ schema and belongs to the Oracle Configurator (CZ) product family, a component of the Oracle E-Business Suite supply chain and order management stack. Its documented purpose is to serve as the Configurator Extension Archive Table, persisting archived configurations, extension artifacts, and related binary or URL-based payloads generated during the configuration lifecycle. In release 12.1.1 and 12.2.2 the table retains the same structural role, though schema validation and column definitions are best confirmed against the 12.2.2 ETRM physical listing.

Within a heuristic Data Vault classification, CZ_ARCHIVES models as a standalone structure — neither a hub nor a link nor a satellite in the strict sense, since no foreign-key relationships were mined from the FK structure. It is best treated as an independent reference or staging table, keyed by a single surrogate identifier, rather than as a participating entity in a normalized hub-and-link graph.

Key Information Stored

The table is documented with 14 columns in the 12.2.2 schema. The most significant are:

• ARCHIVE_ID — the surrogate primary key, enforced by the unique index CZ_ARCHIVES_PK. This is the sole business-key candidate documented.
• NAME and DESCRIPTION — human-readable identification of the archived artifact.
• ARCHIVE_TYPE — classifies the nature of the archived content (for example, extension, configuration, or document type).
• ARCHIVE_BLOB — the binary large object storing the actual archived payload. A system-managed LOB index (SYS_IL0000324853C00005$$) supports this column, indicating it is the fifth physical column.
• ARCHIVE_URL and DOCUMENTATION_URL — external or internal pointers to related archive and documentation resources, used when content is referenced rather than embedded.
• PERSISTENT_ARCHIVE_ID — correlates an archive record to a persistent archive reference, useful for tracking stable artifacts across regenerations.
• DELETED_FLAG — soft-delete indicator, permitting logical removal without physical purge.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS WHO columns supporting change tracking and concurrency.

Common Use Cases and Queries

Because the table is standalone and LOB-bearing, queries should avoid selecting ARCHIVE_BLOB unless the payload is genuinely required. A typical metadata query retrieves descriptive fields only:

• SELECT archive_id, name, archive_type, documentation_url FROM cz.cz_archives WHERE deleted_flag = 'N' ORDER BY creation_date DESC;
• Audit reporting: SELECT created_by, creation_date, last_updated_by, last_update_date FROM cz.cz_archives WHERE archive_id = :id;
• Reconciliation of archives lacking an external reference: SELECT archive_id, name FROM cz.cz_archives WHERE archive_url IS NULL AND persistent_archive_id IS NULL AND deleted_flag = 'N';
• Soft-delete maintenance and purge candidates based on deleted_flag and last_update_date.

Common scenarios include auditing configuration extension history, tracing documentation linked to a configuration, and administrative cleanup of obsolete archive records.

Related Objects

The ETRM metadata documents no foreign-key relationships for CZ_ARCHIVES, consistent with its standalone classification. Consequently, no dependent child tables are guaranteed by constraint. In practice, correlation with Configurator structures is achieved logically rather than declaratively:

• CZ_CONFIGURATIONS and CZ_CONFIG_HDRS — runtime configuration records that may be archived into CZ_ARCHIVES.
• CZ_EXTENSIONS and related extension definition tables — the artifacts whose archived forms are stored here, correlated through ARCHIVE_ID or PERSISTENT_ARCHIVE_ID at the application layer.
• FND_LOBS / FND_ATTACHED_DOCUMENTS — where LOB or document metadata may overlap with ARCHIVE_BLOB and DOCUMENTATION_URL handling.
• FND_USER — joined via CREATED_BY and LAST_UPDATED_BY to resolve user identities in audit reports.

Because no enforced FKs exist, joins to these objects must be established through application-maintained columns, and referential integrity should be validated explicitly in custom reporting.