Results for “dst_table”

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

Overview

CZ_XFR_TABLES is a Configurator (CZ) module control table in the Oracle E-Business Suite, owned by the CZ schema and marked VALID in both 12.1.1 and 12.2.2. Its documented purpose is to act as an import control table responsible for NOUPDATE flags. In practical terms, it defines the transfer (XFR) table mappings used by the Configurator's import and data-transfer routines, governing which source tables are moved into which destination tables and how each transfer behaves with respect to record protection and update suppression.

The table carries eight documented columns and is keyed by the composite primary key CZ_XFR_TABLES_PK on (XFR_GROUP, ORDER_SEQ). Under the heuristic Data Vault classification mined from its foreign key structure, this object is described as hub-leaning — that is, it behaves as a hub-like entity whose business key is the transfer-group and sequence pairing, with dependent attributes attached. This classification is offered as a modeling suggestion rather than a physical Data Vault implementation. Because the primary key also serves as the unique index and business-key candidate, CZ_XFR_TABLES is the parent of CZ_XFR_FIELDS, which references it via the shared XFR_GROUP and ORDER_SEQ columns.

Key Information Stored

Each row describes one transfer step within a transfer group, ordered by sequence. The most significant documented columns are:

• XFR_GROUP — Groups related transfer steps together; part of the primary key and the join key to CZ_XFR_FIELDS.
• ORDER_SEQ — The sequence in which the step executes within its group; the second component of the primary key.
• SRC_TABLE — The source table from which data is read during the transfer.
• DST_TABLE — The destination table into which data is loaded.
• DST_SUBSCHEMA — The destination subschema, allowing transfers to target alternate schema containers.
• FILTERSYNTAX — The filter predicate or selection syntax applied when extracting rows for the transfer.
• PK_USEEXPANSION — Controls whether primary-key expansion is applied for the transfer step.
• DISABLED — Flag indicating whether the transfer step is inactive and should be skipped.

The composite key (XFR_GROUP, ORDER_SEQ) is the only documented unique index and therefore the definitive business-key candidate; no separate surrogate column is documented. Filtering on the DISABLED flag and ordering by ORDER_SEQ replicates the runtime control logic that drives NOUPDATE behavior during imports.

Common Use Cases and Queries

Consultants and DBAs query this table to diagnose Configurator import behavior, audit which tables are transferred and in what order, and determine why certain columns are not updated during a load (the NOUPDATE flag mechanism). Typical reporting includes listing all enabled steps for a group and enumerating destination mappings.

• List active transfer steps for a group:

  SELECT ORDER_SEQ, SRC_TABLE, DST_TABLE, DST_SUBSCHEMA, FILTERSYNTAX
  FROM   CZ.CZ_XFR_TABLES
  WHERE  XFR_GROUP = :group AND NVL(DISABLED,'N') = 'N'
  ORDER BY ORDER_SEQ;

• Audit destination mappings: select distinct DST_TABLE, DST_SUBSCHEMA to review where imports land.
• Join to field-level detail to trace column mappings, using XFR_GROUP and ORDER_SEQ.
• Troubleshoot missing updates by checking PK_USEEXPANSION and the NOUPDATE-driven behavior of related field definitions.

Related Objects

The primary dependent object is CZ_XFR_FIELDS, which references this table through the composite columns CZ_XFR_FIELDS.XFR_GROUP and CZ_XFR_FIELDS.ORDER_SEQ, mapping to the parent key CZ_XFR_TABLES.XFR_GROUP and CZ_XFR_TABLES.ORDER_SEQ. Together these two tables form the transfer-definition pair: CZ_XFR_TABLES defines the table-level step, while CZ_XFR_FIELDS defines the column-level detail. Related Configurator import and model-transfer programs consume these definitions, and the destination tables named in DST_TABLE and DST_SUBSCHEMA are indirectly referenced at execution time. Administrators should treat CZ_XFR_TABLES as the hub governing transfer sequencing, with CZ_XFR_FIELDS as its dependent satellite of field mapping attributes.