Search Results wsh_zone_regions

Overview

The WSH_ZONE_REGIONS table is a core data object within the Oracle E-Business Suite Shipping Execution (WSH) module. It functions as the structural repository for defining the hierarchical relationship between zones and their constituent regions. In shipping logistics, a zone is a logical grouping of geographical areas, often used to simplify freight rating and delivery scheduling. This table stores the specific mapping that defines which regions belong to which zones, enabling the system to apply consistent shipping rules and calculations across broad geographic segments. Its role is fundamental to the configuration and execution of zone-based shipping strategies within the application.

Key Information Stored

The table's primary purpose is to maintain the zone-to-region hierarchy. While the full column list is not detailed in the provided metadata, the documented structure confirms the existence and criticality of the ZONE_REGION_ID column. This column serves as the unique identifier (Primary Key) for each record, which represents a single instance of a region being assigned to a zone. Other columns, typical for such a mapping table, would logically include foreign key references to the zone master (e.g., ZONE_ID) and the region master (e.g., REGION_ID), along with standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) for auditing. The table essentially answers the question: "Which regions make up this specific shipping zone?"

Common Use Cases and Queries

This table is central to any process involving zone-based freight calculations or delivery area validations. A common use case is during the rate shopping process, where the system determines a shipment's destination zone by checking which zone contains the destination region. It is also critical for generating reports on zone coverage and for administrative setups when modifying zone definitions. A fundamental query pattern involves joining WSH_ZONE_REGIONS to the zone and region master tables to list all components of a zone.

• Sample Query: To retrieve all regions for a specific zone named 'WEST_COAST_ZONE', one would typically execute a SQL statement joining WSH_ZONE_REGIONS to WSH_ZONES and a region table (e.g., WSH_REGIONS or HR_LOCATIONS, depending on implementation). The query would filter on the zone name and select the corresponding region identifiers or names from the joined tables.
• Reporting Use Case: Operational reports analyzing freight costs by zone rely on this table to correctly aggregate shipment data from specific regions into their parent zones for management review.

Related Objects

The primary relationship for the WSH_ZONE_REGIONS table is defined by its primary key constraint, WSH_ZONE_REGIONS_PK1, on the ZONE_REGION_ID column. This key is referenced by foreign key constraints in other shipping tables that need to link to a specific zone-region assignment. While the specific referencing tables are not listed in the excerpt, they would logically include detail tables in the shipping schema that store transactional or rating data tied to a zone-region combination. The table has a direct relationship with the master tables for zones (likely WSH_ZONES) and regions, which supply the foreign key values stored within WSH_ZONE_REGIONS to form the hierarchy. Any API or program unit within the Shipping Execution module that creates, updates, or validates zone definitions will interact with this table.