Search Results validate_region

Overview

WSH_REGIONS_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the maintenance and loading of region, zone and geographic reference data used by Oracle Shipping Execution (WSH) and related logistics and transportation modules. Regions in this context represent geographic entities — countries, states, cities, ports, airports, road and rail terminals, and postal code ranges — that are used for routing, freight rating, delivery, and location determination. The package encapsulates the business logic required to insert, update, delete, validate and lock region and zone records, and to load the seeded or default region data into the base tables. It is classified as a general-purpose (OTHER) API rather than a fully supported public API, which means it is primarily intended for internal EBS use, data loading, and controlled extension, and its signatures may change between releases.

Key Procedures and Functions

The documented interface contains 23 procedures and functions. The core maintenance routines are ADD_REGION, INSERT_REGION, UPDATE_REGION and DELETE_REGION, which perform the respective DML operations against region records and their translations. LOCK_REGION and LOCK_REGION_INTERFACE provide concurrency control, ensuring that a region row and its interface staging row are protected during multi-step updates. VALIDATE_REGION performs business validation on region attributes before persistence.

Zone-related routines include UPDATE_ZONE, LOCK_ZONE, UPDATE_ZONE_REGION and LOCK_ZONE_REGION, which manage the relationship between delivery zones and the regions that belong to them. GETZONEREGIONS and GET_PARENT_REGION_INFO are query functions that return zone membership and parent-child region hierarchy information respectively.

Data load and seeding is handled by LOAD_REGION, LOAD_ALL_REGIONS and DEFAULT_REGIONS, which populate region data from seeded or supplied sources. Language support is provided by ADD_LANGUAGE. The global table routines INIT_GLOBAL_TABLE, INSERT_GLOBAL_TABLE and UPDATE_GLOBAL_TABLE manage a PL/SQL global temporary structure used to hold region data in memory during a session, typically ahead of bulk processing.

Tables Accessed

The package reads and writes WSH_REGIONS, the base region table, and its translation table WSH_REGIONS_TL, which stores language-dependent descriptions such as continent, country, state, city, county and alternate name. Interface staging is handled through WSH_REGIONS_INTERFACE and WSH_REGIONS_TL_INTERFACE, with WSH_REGIONS_INTERFACE_S providing the sequence. Zone membership is maintained in WSH_ZONE_REGIONS and WSH_ZONE_REGIONS_S. Global and session-level collected data is held in WSH_REGIONS_GLOBAL and WSH_REGIONS_GLOBAL_DATA. FND_LANGUAGES is referenced to validate and resolve language codes, and DUAL and DBMS_UTILITY are used for utility operations. PLITBLM supports PL/SQL table (associative array) manipulation. The numerous associative array types declared in the package header — for region ID, country code, state code, city code, port and terminal flags, longitude, latitude, timezone and translated descriptions — mirror the column structure of these tables and are used to pass bulk region data between procedures efficiently.

Usage Notes

WSH_REGIONS_PKG is typically invoked from Oracle Shipping Execution setup forms, from concurrent programs that seed or refresh region and zone data, and from internal EBS code that resolves geographic routing information. Administrators use it indirectly when maintaining regions and zones through the application UI. Because it is not a formally published public API, custom code should exercise caution: direct calls to INSERT_REGION or the load routines (triggered by the user's search for "insert_region") are best reserved for controlled data migration or extension scenarios, and callers should validate against the current release's version of the package. The package is referenced by three other EBS packages, confirming its role as a shared dependency within the WSH region and zone data model. Any customization should account for the translation table (WSH_REGIONS_TL) and interface tables being updated in tandem to preserve multi-language integrity.