Results for “zone_id”

50+ results




Overview
Explore in AI Chat

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

Overview

FTE_INTERFACE_ZONES is the inbound staging interface table used by Oracle Transportation Execution (FTE), formerly known as Oracle Transportation Management's execution-side zone processing within the E-Business Suite framework. It belongs to the FTE schema and holds zone definition records that are loaded and validated before being promoted into the operational zone model. In Oracle EBS 12.1.1 and 12.2.2, FTE performs warehouse and transportation execution activities such as picking, put-away, cross-docking, and task dispatch; zone boundaries defined by postal code ranges are a foundational input to those activities. This table functions as a transient buffer: external systems, warehouse management feeds, or conversion programs write zone records here, and concurrent programs validate and migrate valid rows to their destination tables, typically the warehouse zone base tables.

The ETRM metadata classifies FTE_INTERFACE_ZONES heuristically as standalone under the Data Vault modeling scheme. As a modeling suggestion, this implies the table is not itself a hub, link, or satellite within a normalized Data Vault design, but rather a functional staging object that participates in the integration flow feeding the WMS zone structures. It carries a single outbound foreign key to WMS_ZONES_B via ZONE_ID, indicating that its ultimate business purpose is to establish or update zone master records.

Key Information Stored

The documented physical schema comprises nine columns. The most significant are:

  • ZONE_ID — Foreign key to WMS_ZONES_B.ZONE_ID; the surrogate identifier linking a staged row to an existing zone master record. This is the primary integration key.
  • ZONE_NAME — The business name of the zone, a candidate business key used to match or create zone definitions.
  • POSTAL_CODE_FROM and POSTAL_CODE_TO — The lower and upper bounds of the postal code range defining the zone's geographic span.
  • POSTAL_CODE_STRING — A delimited or concatenated representation of postal codes, supporting bulk or pattern-based zone assignment.
  • LOAD_ID — Identifies the interface batch or load run, enabling grouping and reprocessing of records from a given upload.
  • HASH_VALUE — A computed checksum used to detect changed records and avoid redundant processing.
  • OWNER_ID — Owning organization or party reference that scopes the zone record.
  • ROW_NUMBER — Sequence or line number within the interface load, useful for ordering and error reporting.

No unique index is documented in the provided metadata; ZONE_ID serves as the principal relationship identifier rather than a declared surrogate primary key.

Common Use Cases and Queries

Typical scenarios include validating an inbound zone load, detecting duplicates or hash changes before promotion, and reconciling staged rows against existing zone masters. Representative SQL patterns:

  • Preview a load: SELECT zone_id, zone_name, postal_code_from, postal_code_to FROM fte.fte_interface_zones WHERE load_id = :p_load_id ORDER BY row_number;
  • Find staged rows with no matching master zone: SELECT i.* FROM fte.fte_interface_zones i WHERE NOT EXISTS (SELECT 1 FROM wms_zones_b b WHERE b.zone_id = i.zone_id);
  • Detect unchanged records: compare HASH_VALUE against the current master value to skip re-processing.
  • Reporting: summarize zone coverage by postal range for network analysis prior to commit.

Related Objects

  • WMS_ZONES_B — Base zone master; referenced by FTE_INTERFACE_ZONES.ZONE_ID. The primary promotion target.
  • WMS_ZONES_TL — Zone translation table, supplying zone names for validation and reporting.
  • FTE interface processing and validation concurrent programs, which consume LOAD_ID batches from this table.
  • Other FTE interface tables (parallel staging tables) that share the LOAD_ID and HASH_VALUE conventions for consistent batch control.
  • Inventory and warehouse execution tables that rely on zone assignments derived from promoted zone records.

Together these objects complete the path from staged zone data to operational transportation and warehouse execution logic.