Search Results order_seq




Overview
Explore in AI Chat

Overview

CZ_XFR_FIELDS is a Configurator (CZ) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores import rule specifications at the field level. It defines how individual source and destination fields participate in a Configurator transfer (XFR) definition, working in tandem with the table-level rules held in CZ_XFR_TABLES. Each row describes the mapping, ordering, and behavioral constraints applied when a field is imported through a Configurator transfer process, which is typically used in the context of model and option class migration between environments or organizations.

Under the heuristic Data Vault classification mined from its foreign key structure, CZ_XFR_FIELDS is satellite-leaning. In practice this means the table behaves as a descriptive, attribute-bearing entity whose context is defined by an upstream parent (CZ_XFR_TABLES), rather than a standalone hub or an associative link. Modeling it as a satellite attached to the transfer-group business key is a reasonable design suggestion for analytical or warehouse replication.

Key Information Stored

The table contains 8 documented columns. The surrogate primary key is CZ_XFR_FIELDS_PK, composed of FIELD_ORDER, XFR_GROUP, and ORDER_SEQ. This composite uniquely identifies each field-level rule and is also present as a unique index, making it the strongest documented business-key candidate.

  • XFR_GROUP — the transfer group identifier that ties this field rule to the parent CZ_XFR_TABLES record; the leading FK join to the table-level definition.
  • FIELD_ORDER — the ordinal position of the field within the transfer definition; part of the composite PK and the join key used by CZ_XFR_FIELD_REQUIRES.
  • ORDER_SEQ — sequencing value that distinguishes repeated or ordered entries within the same XFR_GROUP and FIELD_ORDER; the third PK column.
  • SRC_FIELD — the source field name or identifier from which values are read during the import/tranfer.
  • DST_FIELD — the destination field name or identifier to which the value is written.
  • REQUIRED — flag indicating whether the field must be populated for the transfer rule to succeed.
  • DEFAULT — the default value applied to the destination field when no source value is supplied (stored as DEFAULT within DEFAULTSYNTAX).
  • NOUPDATE — flag controlling whether an existing destination value may be overwritten by the transfer.

Common Use Cases and Queries

Typical uses include inspecting the field mapping rules for a specific transfer group, auditing which fields are mandatory, and identifying default or no-update fields that govern migration behavior. A common retrieval pattern is:

  • SELECT XFR_GROUP, FIELD_ORDER, ORDER_SEQ, SRC_FIELD, DST_FIELD, REQUIRED, DEFAULTSYNTAX, NOUPDATE FROM CZ.CZ_XFR_FIELDS WHERE XFR_GROUP = :p_group ORDER BY FIELD_ORDER, ORDER_SEQ;
  • Reporting required fields per transfer: WHERE REQUIRED = 'Y';
  • Identifying mappings that must not be overwritten: WHERE NOUPDATE = 'Y';
  • Joining to CZ_XFR_TABLES on XFR_GROUP to resolve the parent table context.

Related Objects

  • CZ_XFR_TABLES — parent table referenced by CZ_XFR_FIELDS.XFR_GROUP; provides the table-level import rule specification.
  • CZ_XFR_FIELD_REQUIRES — child table referencing CZ_XFR_FIELDS via FIELD_ORDER, XFR_GROUP, and ORDER_SEQ; records field dependency/requirement constraints.
  • CZ_XFR_FIELDS_PK — primary key index on (FIELD_ORDER, XFR_GROUP, ORDER_SEQ).