Search Results wsh_map_location_region_pkg




Overview
Explore in AI Chat

Overview

APPS.WSH_MAP_LOCATION_REGION_PKG is a Oracle E-Business Suite PL/SQL package that supports the mapping between physical locations and geographic regions within the Oracle Shipping (WSH) application. Its primary business purpose is to associate location records — such as addresses, organizations, and ship-to or ship-from sites — with the region definitions used by Oracle Transportation and logistics processing. This association is fundamental to carrier service selection, transit time calculation, delivery scheduling, and picking rule evaluation, all of which depend on knowing the geographic region into which a shipment is destined or from which it originates.

The package is classified as VALID in the APPS schema and is registered in ETRM with an API classification of OTHER, indicating that it is an internal utility package rather than a formally published public API. It is referenced by ten other packages and concurrent program components, including WSH_REGIONS_SEARCH_PKG, WSH_UTIL_CORE, WSH_UTIL_VALIDATE, WSH_EXTERNAL_INTERFACE_SV, WSH_PARTY_MERGE, FTE_LANE_SEARCH, HR_LOCATION_BK1 through HR_LOCATION_BK3, and the package itself, confirming its role as a shared service layer for location-to-region resolution across WSH and HR integration points.

Key Procedures and Functions

ETRM documents ten procedures and functions within this package. Their documented roles are as follows:

  • MAP_LOCATIONS — Primary driver routine for mapping location records to their corresponding regions.
  • MAP_LOCATIONS_CHILD_PROGRAM — Child concurrent program entry point that processes location mapping in batches, enabling the main mapping routine to be executed as a scheduled background job.
  • MAPPING_REGIONS_MAIN — Main orchestration routine for the region mapping process.
  • INSERT_RECORD — Inserts an individual mapping record, persisting the association between a location and its region.
  • MAP_LOCATION_TO_REGION — Resolves and assigns the region for a specific location.
  • RULE_LOCATION — Applies location-related rules, supporting the broader picking and routing rule framework.
  • TRANSFER_LOCATION — Handles relocation or transfer of a location mapping.
  • LOCATION_USER_HOOK_API — User exit hook allowing customers to extend or override default location mapping behavior.
  • GET_TRANSIT_TIME — Returns transit time information derived from the mapped location and region data.
  • PREDEL_LOC_VALIDATION — Validates location data prior to deletion, protecting referential integrity of the mapping tables.

Tables Accessed

The package reads and writes several core EBS tables through APPS synonyms. WSH_LOCATIONS and WSH_REGIONS form the foundation of the mapping, holding location and region definitions respectively. WSH_CARRIER_SERVICES, WSH_CALENDAR_ASSIGNMENTS, WSH_PICKING_RULES, and WSH_DOC_SEQUENCE_CATEGORIES support service, calendar, rule, and document sequencing dependencies. HR_LOCATIONS_ALL and HR_ALL_ORGANIZATION_UNITS integrate human resources location and organization data. FND_TERRITORIES_TL supplies territory descriptions, while MTL_PARAMETERS, MTL_INTERORG_SHIP_METHODS, and MRP_ATP_SCHEDULE_TEMP_S link shipping logic to inventory and ATP scheduling. WF_EVENT_T and WF_PARAMETER_LIST_T provide Workflow event and parameter handling, and WSH_DELIVERY_DETAILS connects mappings to delivery lines.

Usage Notes

WSH_MAP_LOCATION_REGION_PKG is typically invoked indirectly. Concurrent programs schedule location mapping through MAP_LOCATIONS_CHILD_PROGRAM, while forms tied to location and region maintenance trigger validation and mapping logic. The GET_TRANSIT_TIME function is consumed by shipping and transportation flows requiring transit estimation, and PREDEL_LOC_VALIDATION is called before location deletion. Because of its API classification as OTHER, customizations should avoid direct calls to internal procedures and instead leverage the documented entry points or the LOCATION_USER_HOOK_API user exit, which is the sanctioned extension mechanism. The package is available in both Oracle EBS 12.1.1 and 12.2.2, with the 12.2.2 ETRM metadata confirming the same procedure inventory and dependency footprint.