Search Results get_facility_parameters




Overview
Explore in AI Chat

Overview

MST_GEOCODING is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. It provides time-zone conversion and facility-level logistics parameter retrieval services used throughout the Oracle Transportation and warehouse/logistics modules. The package is defined with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the calling schema rather than the definer, a convention consistent with many shared APPS utility packages. Its source header (MSTGEOCS.pls 115.5, dated 2004) indicates the package has been stable and largely unchanged across releases, which is why the same signatures remain valid in EBS 12.1.1 and 12.2.2. The documented API classification is "OTHER," and the package is referenced by 17 other packages, confirming its role as a shared low-level service rather than an end-user-facing API. The two broad capabilities it exposes are (a) conversion between local and server time using a location identifier, and (b) retrieval of facility handling parameters such as load and unload rates and their associated units of measure.

Key Procedures and Functions

The package exposes five documented program units. No parameter lists are reproduced here beyond what the metadata records; descriptions reflect documented purpose only.

  • GET_LOCAL_TIME — Function that converts a supplied server time into the local time for a given location.
  • GET_SERVER_TIME — Function that performs the inverse conversion, translating a supplied local time at a location into server time.
  • GET_TIMEZONE_CODE — Function returning the time-zone code applicable to a given location as of a specified date, so that daylight-saving transitions are honored.
  • GET_SERVER_TIMEZONE_CODE — Function returning the time-zone code of the server for a given date.
  • GET_FACILITY_PARAMETERS — Procedure that returns facility handling parameters for the caller's facility context. It follows the standard EBS API convention, accepting an API version and an initialization flag, and returning pallet and non-pallet load and unload rates together with their handling units of measure. Status and error information are returned through the standard X_RETURN_STATUS, X_MSG_COUNT, and X_MSG_DATA out parameters, and the NOCOPY hint is applied to the out parameters for efficiency.

Tables Accessed

The package resolves data through two APPS synonyms. WSH_LOCATIONS supplies the location and time-zone attributes that drive the four time-conversion functions, providing the mapping between a location identifier and its geographic time zone. FND_APPLICATION is referenced for application-level context, typical of shared utility packages that must identify the owning application or resolve installation metadata. The metadata does not document additional base tables, suggesting facility parameter values are derived from configuration held in these or dependent objects rather than a dedicated parameter table visible at this level.

Usage Notes

MST_GEOCODING is a programmatic utility rather than a form-driven API. Its time-conversion functions are typically called from custom PL/SQL and from other packaged code whenever timestamps must be presented in local time or normalized to server time, for example in shipment, delivery, and appointment processing. Because GET_TIMEZONE_CODE and GET_SERVER_TIMEZONE_CODE accept a date argument, callers obtain correct results across daylight-saving boundaries. GET_FACILITY_PARAMETERS is invoked when processing logic needs the configured pallet or non-pallet load and unload rates and the associated handling units of measure; callers must inspect X_RETURN_STATUS and, on failure, X_MSG_COUNT and X_MSG_DATA, honoring the standard FND_API message-stack conventions. Given the package's AUTHID CURRENT_USER declaration, callers execute the underlying queries with their own privileges, so synonym grants on WSH_LOCATIONS and FND_APPLICATION must be in place. Its broad reuse by 17 dependent packages makes it a stable integration point in both 12.1.1 and 12.2.2.