Search Results get_location_data

Overview

The APPS.WSH_MAP_LOCATION_REGION_PKG package body belongs to the Oracle E-Business Suite Shipping (WSH) module and provides the core processing logic for mapping inventory locations to shipping regions. Its principal business role is to associate location records held in WSH_LOCATIONS with entries in WSH_REGIONS, thereby establishing the geographic relationships that drive freight rating, carrier service selection, transit time calculation, and delivery scheduling. The package is classified as an OTHER API in ETRM and is documented as being referenced by ten other packages, indicating it functions as a shared service utility rather than an isolated component.

The header comment ($Header: WSHMLORB.pls 120.16.12010000.3) confirms the file shipped in the 12.1.1 code line and remains the documented baseline for 12.2.2. A significant portion of the body is dedicated to bulk operations against WSH_REGION_LOCATIONS, introduced under Bug 4722963, which replaced row-by-row processing with collection-based insert, update, and delete logic for performance reasons.

Key Procedures and Functions

• MAP_LOCATIONS — The primary entry point. It determines the minimum and maximum location identifiers for the requested scope and spawns the child concurrent program one or more times based on the p_num_of_instances parameter, supporting parallel execution. It accepts inputs for region mapping, location type, date range, FTE installation, and facility creation.
• MAP_LOCATIONS_CHILD_PROGRAM — The worker program invoked by MAP_LOCATIONS for each partitioned range of location identifiers.
• MAPPING_REGIONS_MAIN — Drives the overall region mapping logic, coordinating rule evaluation and record persistence.
• INSERT_RECORD — Performs the physical insert of a location-to-region association into the mapping tables.
• MAP_LOCATION_TO_REGION — Resolves the appropriate region for a given location based on configured mapping criteria.
• RULE_LOCATION — Applies region assignment rules, including those maintained through the region and territory definitions.
• TRANSFER_LOCATION — Moves or reassigns a location between regions.
• LOCATION_USER_HOOK_API — A user exit hook allowing customers to extend or override standard mapping behavior.
• GET_TRANSIT_TIME — Returns the transit time associated with a mapped location and region pair, feeding downstream scheduling decisions.
• PREDEL_LOC_VALIDATION — Validates a location prior to deletion of its region mapping, guarding referential integrity.

Tables Accessed

The package reads and writes WSH_LOCATIONS and WSH_REGIONS as its core mapping entities. Territory and address data are sourced from FND_TERRITORIES_TL, HR_LOCATIONS_ALL, and HR_ALL_ORGANIZATION_UNITS. Shipping configuration is drawn from WSH_CALENDAR_ASSIGNMENTS, WSH_CARRIER_SERVICES, WSH_DELIVERY_DETAILS, WSH_DOC_SEQUENCE_CATEGORIES, and WSH_PICKING_RULES. Interorg and inventory context comes from MTL_INTERORG_SHIP_METHODS and MTL_PARAMETERS. Notably for the msc_atp search context, the package references MRP_ATP_SCHEDULE_TEMP_S, linking region mapping to available-to-promise scheduling activities. Workflow integration is handled through WF_EVENT_T and WF_PARAMETER_LIST_T.

Usage Notes

The package is typically invoked through the Shipping region mapping concurrent programs, where MAP_LOCATIONS serves as the driver and dispatches child requests across location ID ranges. It can also be called from Oracle Forms, PL/SQL batch routines, or custom extensions requiring programmatic location-to-region resolution. Customers implementing specialized mapping rules should use LOCATION_USER_HOOK_API rather than modifying the seeded body. Because it is referenced by ten other packages, changes to its behavior should be regression-tested across shipping, rating, and ATP scheduling flows.