Results for “rec_status”

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

Overview

The CZ_XFR_RUN_RESULTS table resides in the CZ (Configurator) schema within Oracle E-Business Suite, and is documented as valid in both release 12.1.1 and 12.2.2. Its documented purpose is to provide a summary of records imported during a configuration transfer or import run. In practice, this table acts as a per-run, per-table audit and reconciliation ledger: each row captures how many records a specific import operation moved for a given source table and the resulting disposition or status of those records. This makes it a diagnostic and control object rather than a transactional master or detail table.

ETRM metadata classifies this object heuristically as standalone, with no foreign-key relationships mined from its structure. Under a Data Vault modeling lens, this classification suggests the table behaves as an independent reporting or outcome table rather than functioning as a hub, link, or satellite within a conformed Data Vault model. Architects designing a warehouse layer should therefore treat CZ_XFR_RUN_RESULTS as a self-contained fact-like entity keyed on the run and source table combination, and model any associated run header or source table descriptions as separate dimensions.

Key Information Stored

The table contains five documented columns. The primary key constraint, CZ_XFR_RUN_RESULTS_PK, is defined over four of these columns and also serves as the sole unique (business-key candidate) index: IMP_TABLE, REC_STATUS, RUN_ID, and DISPOSITION. Columns of significance include:

• RUN_ID — Identifier of the configuration transfer or import run this result row belongs to. Groups all per-table outcomes produced by a single execution.
• IMP_TABLE — Name of the import (source or target) table to which the row's counts and status refer.
• DISPOSITION — The result classification assigned to the records, such as accepted, rejected, or otherwise categorized, distinguishing outcome buckets within a run.
• REC_STATUS — Status of the records for that table and disposition, forming part of the composite uniqueness of each row.
• RECORDS — Numeric count of records falling into the combination of run, table, disposition, and status.

Because the primary key spans IMP_TABLE, REC_STATUS, RUN_ID, and DISPOSITION, there is no single surrogate column key; the surrogate identity is the composite of those four attributes, and RECORDS acts purely as a measure. CONFIGURATOR-specific implementations should not assume additional columns beyond those documented.

Common Use Cases and Queries

Typical scenarios include reconciling an import run, auditing rejection volumes, and producing transfer success reporting. A common pattern aggregates counts per run:

• SELECT RUN_ID, IMP_TABLE, DISPOSITION, REC_STATUS, SUM(RECORDS) FROM CZ.CZ_XFR_RUN_RESULTS WHERE RUN_ID = :run_id GROUP BY RUN_ID, IMP_TABLE, DISPOSITION, REC_STATUS;
• Identifying tables with non-zero rejections: SELECT RUN_ID, IMP_TABLE, RECORDS FROM CZ.CZ_XFR_RUN_RESULTS WHERE DISPOSITION = 'REJECTED' ORDER BY RECORDS DESC;
• Trending import throughput across runs by joining RUN_ID to the parent run header.

These queries support post-migration validation, error triage, and operational reporting where confirmation that all records were imported is required.

Related Objects

Although the ETRM metadata records this object as standalone with no mined foreign keys, dependent reporting and transfer programs reference it through its documented columns. The principal associated objects include the parent run header table keyed by RUN_ID, the CZ transfer staging tables whose names appear in IMP_TABLE, the CZ_XFR_RUN_RESULTS_PK index enforcing uniqueness, and Configurator transfer concurrent programs that populate results during execution. Join columns remain RUN_ID and IMP_TABLE; no additional FK columns are documented. Oracle Proprietary, Confidential Information.