Search Results wsh_regions_interface




Overview
Explore in AI Chat

Overview

WSH_REGIONS_INTERFACE is a Shipping Execution (WSH) staging table in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It serves as an inbound interface for region reference data, storing region records prior to validation and upload into the permanent region tables used by shipping and transportation configuration. The table resides in the WSH schema and is documented as VALID and Oracle proprietary/confidential. It is one of several WSH interface tables that isolate external or bulk-loaded data from the base reference tables, allowing batch cleansing, validation, and error handling before promotion.

Heuristically mined from its foreign-key structure, the object is classified in Data Vault terms as standalone, meaning it is not modeled as a dependent hub, link, or satellite. This classification should be treated as a modeling suggestion: the table behaves as a self-contained staging entity whose regional hierarchy is expressed via a self-referencing PARENT_REGION_ID rather than external foreign-key relationships.

Key Information Stored

The table contains 21 documented columns. The most significant are:

Common Use Cases and Queries

Typical usage involves bulk-loading region data from external sources and then selecting unprocessed rows for validation and upload. A common pattern is:

  • Identifying pending records: SELECT region_id, region_type, country_code FROM wsh_regions_interface WHERE processed_flag = 'N';
  • Resolving hierarchies: joining the table to itself on parent_region_id = region_id to reconstruct the regional tree.
  • Reporting transportation coverage by counting records grouped by the port/airport/road/rail flags, or aggregating by country and state codes.
  • Validating geography by checking latitude/longitude and timezone completeness before promotion.

The PROCESSED_FLAG column is central to interface control; rows are written, validated, and then flagged once the corresponding base-table record is created.

Related Objects

Because the metadata classifies the table as standalone, explicit FK relationships to other objects are not documented. Its functional dependencies are instead inferred from the shipping reference model:

  • Base region reference tables in the WSH schema that receive the promoted rows.
  • WSH_REGIONS_INTERFACE_U1 and WSH_REGIONS_INTERFACE_PK1 — unique and primary key indexes on REGION_ID.
  • Shipping and transportation configuration components that consume the geographic hierarchy, transportation-node flags, and timezone data.
  • Concurrent programs and APIs that read PROCESSED_FLAG to drive the upload cycle.

The self-join on PARENT_REGION_ID remains the primary internal relationship for hierarchical analysis.