Search Results id_tbl_type

Overview

APPS.WSH_LOCATIONS_PKG is a PL/SQL package in the Oracle E-Business Suite that maintains the WSH_LOCATIONS table, the Warehouse Management System's internal repository of shipping, receiving, and delivery locations. The package exists because Oracle Shipping requires a consolidated, denormalized view of location data that originates in multiple master tables — principally HZ_LOCATIONS for external customer and party sites and HR_LOCATIONS_ALL for internal organization locations. Rather than querying those heterogeneous sources at runtime, Shipping extracts the relevant records into WSH_LOCATIONS and keeps them synchronized.

The header comment of the package states its purpose directly: "To populate data in WSH_LOCATIONS with the data in HZ_LOCATIONS, HR_LOCATIONS." This positions the package as a data consolidation utility rather than a transactional API. It is a supporting component for shipping execution, carrier assignment, and location-based routing, and is referenced by sixteen other packages within the applications schema.

Key Procedures and Functions

Eight procedures and functions are documented. The central entry point is PROCESS_LOCATIONS, which drives population of WSH_LOCATIONS from HZ_LOCATIONS (filtered to deliver-to and ship-to usages) and HR_LOCATIONS. It accepts a location type discriminator (EXTERNAL, INTERNAL, or BOTH), a from/to location ID range, and a start/end date range used to restrict processing to records updated within the specified window; a null date range implies processing without that restriction. PROCESS_LOCATIONS orchestrates the remaining worker routines.

GET_SITE_NUMBER resolves the site number associated with a location, supporting identification and lookup of a party site or organization site. INSERT_LOCATIONS performs the initial insertion of location rows into WSH_LOCATIONS. UPDATE_LOCATIONS applies changes to existing rows, typically after the source HZ or HR record has been modified. INSERT_LOCATION_OWNERS establishes ownership relationships for locations, linking them to the appropriate owning entity so that Shipping can determine which operating unit or organization is entitled to use a given address. CREATE_GEOMETRY derives and stores spatial geometry values from the longitude and latitude columns, and CONVERT_INTERNAL_CUST_LOCATION handles transformation of internal customer-associated locations, reconciling the distinction between internally owned sites and customer-facing sites used in shipping.

These routines are not intended for direct external invocation; they are invoked in sequence by PROCESS_LOCATIONS or by other application packages.

Tables Accessed

WSH_LOCATIONS is the primary table written by the package. The location record type declared in the package specification mirrors the WSH_LOCATIONS columns exactly: WSH_LOCATION_ID, SOURCE_LOCATION_ID, LOCATION_SOURCE_CODE, LOCATION_CODE, UI_LOCATION_CODE, the four address lines, COUNTRY, STATE, PROVINCE, COUNTY, CITY, POSTAL_CODE, INACTIVE_DATE, LONGITUDE, LATITUDE, GEOMETRY, and TIMEZONE_CODE.

Source data is read from HZ_LOCATIONS, HZ_PARTY_SITES, HZ_PARTIES, HZ_PARTY_USG_ASSIGNMENTS, HZ_CUST_ACCT_SITES_ALL, and HZ_CUST_SITE_USES_ALL on the Oracle Receivables/Trading Community side, and from HR_LOCATIONS_ALL, HR_LOCATIONS_ALL_TL, and HR_ALL_ORGANIZATION_UNITS on the Human Resources side. FND_TIMEZONES_B supplies valid time zone reference values. AP_SUPPLIERS and PO_LOCATION_ASSOCIATIONS_ALL support supplier and purchasing location relationships, MTL_PARAMETERS supplies inventory organization context, and WSH_CARRIERS links location data to carrier definitions used in shipping.

Usage Notes

WSH_LOCATIONS_PKG is normally invoked indirectly. In a standard EBS configuration it is called from concurrent programs and from Oracle Shipping forms when location data must be refreshed after changes in the underlying HZ or HR tables. Because it is referenced by sixteen other packages, customizations should treat it as a shared dependency and avoid modifying its specification.

The search term "id_tbl_type" is not part of the documented package metadata. That identifier does not appear among the declared record types, procedures, or functions of WSH_LOCATIONS_PKG; it is more likely a column or type name from a different object such as WSH_LOCATION_ASSOC or a related shipping association package. Developers tracing "id_tbl_type" should consult the object that actually declares it rather than this package.

From a Release 12.1.1 and 12.2.2 perspective, the package behavior is consistent across both releases; the header revision (120.1.12000000.1) predates the 12.2 online patching model, and no 12.2-specific editioning changes are documented for this object. Any extension should be implemented as a wrapper that calls the standard procedures after validating the source HZ and HR data, and should account for the fact that PROCESS_LOCATIONS may run over large date ranges and therefore should be scheduled during low-activity periods.