Search Results wsh_regions_interface_s

Overview

The APPS.WSH_REGIONS_PKG package body is a core Warehouse Management (WSH) database object in Oracle E-Business Suite that manages the definition, maintenance, and propagation of shipping and receiving regions and their associated zone relationships. Regions and zones underpin the geographic hierarchy used throughout WSH to drive freight rating, routing, delivery calendars, and carrier service coverage. Because these geographic constructs are widely shared within Oracle Shipping Execution, the region model must be maintained in a controlled, auditable fashion, and WSH_REGIONS_PKG provides the procedural layer that enforces that control.

The package body is documented as VALID in the APPS schema with an API classification of OTHER. It depends on a broad set of WSH utilities — among them WSH_DEBUG_SV, WSH_DEBUG_INTERFACE, WSH_UTIL_CORE, and WSH_REGIONS_SEARCH_PKG — as well as FND_API, FND_MESSAGE, FND_REQUEST, and FND_GLOBAL for standard EBS error handling, messaging, concurrent request submission, and session context. Documented references to WSH_REGIONS_INTERFACE and WSH_REGIONS_INTERFACE_S confirm that the package participates in interface-table processing, which is consistent with the user search term "wsh_regions_interface_s".

Key Procedures and Functions

The package exposes 23 documented procedures and functions that can be grouped by purpose. Region maintenance is handled by ADD_REGION, INSERT_REGION, UPDATE_REGION, DELETE_REGION, and LOCK_REGION, which create, modify, remove, or explicitly lock region records. Interface processing is supported by LOCK_REGION_INTERFACE, which serializes operations against the region interface tables. Zone and zone-region relationships are managed through UPDATE_ZONE, LOCK_ZONE, UPDATE_ZONE_REGION, and LOCK_ZONE_REGION. Region loading and seeding are addressed by LOAD_REGION, DEFAULT_REGIONS, and LOAD_ALL_REGIONS. Query support is provided by GETZONEREGIONS, while GET_PARENT_REGION_INFO resolves hierarchical parent region information.

Translation and globalization are handled by ADD_LANGUAGE, which extends region definitions to additional FND_LANGUAGES entries. Validation of region data is performed by VALIDATE_REGION. The global-table routines INIT_GLOBAL_TABLE, INSERT_GLOBAL_TABLE, and UPDATE_GLOBAL_TABLE manage the WSH_REGIONS_GLOBAL and WSH_REGIONS_GLOBAL_DATA structures that are used to cache or stage region data for runtime access.

Tables Accessed

The package operates predominantly against the base region tables WSH_REGIONS, WSH_REGIONS_TL (the translated/language table), and their interface counterparts WSH_REGIONS_INTERFACE and WSH_REGIONS_TL_INTERFACE. The _S synonyms (WSH_REGIONS_S, WSH_REGIONS_INTERFACE_S) indicate sequence-number generation used during insert processing. Zone relationships are stored in WSH_ZONE_REGIONS and WSH_ZONE_REGIONS_S. Language validation and translation are supported by FND_LANGUAGES. Global caching uses WSH_REGIONS_GLOBAL and WSH_REGIONS_GLOBAL_DATA. Utility references such as DBMS_UTILITY, DUAL, and PLITBLM are used for context inspection and PL/SQL utility operations.

Usage Notes

WSH_REGIONS_PKG is typically invoked from Shipping Execution setup forms, from region and zone loading concurrent programs, and from interface-processing routines that stage data for validation before writing to the base region tables. The LOCK_* routines indicate that the package is intended for controlled, serialized maintenance rather than casual ad hoc modification. Because the package is documented as referenced by three other database objects and itself depends on FND_REQUEST, it is likely used to launch load or validation programs. Custom code should call the documented API routines rather than performing direct DML against WSH_REGIONS or WSH_ZONE_REGIONS, ensuring that validation, translation handling, and locking are consistently applied.