Search Results mst_geocoding




Overview
Explore in AI Chat

Overview

The APPS.MST_GEOCODING package body is a stored PL/SQL utility within the Oracle E-Business Suite APPS schema that provides geocoding, time-zone resolution, and location-derived time computation services. Its primary business function is to translate a geographic location, facility, or server context into the correct time-zone code and corresponding local or server time, allowing Oracle EBS modules—most notably Oracle Transportation Management and logistics-related processing—to schedule activities, stamp transactions, and apply time-sensitive business rules against the correct regional clock. The package is classified as OTHER in the ETRM repository and is a VALID object in both Oracle EBS 12.1.1 and 12.2.2 environments.

Geocoding in this context is deliberately narrow: rather than performing street-address normalization, the package reconciles Oracle application configuration (profile options and application registrations) with the warehouse and shipping location model to derive a reliable time-zone reference. This avoids hard-coding regional offsets and keeps scheduling logic aligned with Oracle's own time-zone master data.

Key Procedures and Functions

The package body exposes five documented subprograms:

  • GET_LOCAL_TIME — Returns the current time expressed in the local time zone applicable to the caller's location or facility context. It is the principal entry point for applications needing a location-aware timestamp.
  • GET_SERVER_TIME — Returns the current time as observed on the database or application server, providing a normalized baseline when the local zone is unknown or irrelevant.
  • GET_TIMEZONE_CODE — Resolves and returns the time-zone code for a given location or facility. This is the core geocoding lookup that maps a physical or organizational location to an Oracle-recognized time-zone identifier.
  • GET_SERVER_TIMEZONE_CODE — Returns the time-zone code associated with the server, enabling comparison between server and local zones.
  • GET_FACILITY_PARAMETERS — Retrieves configuration parameters tied to a facility, supplying the attributes that the other functions use to determine location and time-zone behavior.

No parameter signatures are documented; consumers should inspect the package specification in the target environment before calling these routines from custom code.

Tables Accessed

The package reads from two APPS-synonymed tables:

  • FND_APPLICATION — the Oracle Application Object Library registration table. It is queried to identify application context and related configuration used during time-zone resolution.
  • WSH_LOCATIONS — the shipping and warehouse location repository. It supplies the geographic and facility attributes from which the time-zone code and facility parameters are derived.

Additional dependencies reported by the ETRM metadata include FND_PROFILE, FND_TIMEZONES_VL, and HZ_TIMEZONE_PUB, indicating that profile option values and the Trading Community time-zone master are consulted as part of the resolution chain. The package does not appear to write to these objects; it functions as a read-only utility.

Usage Notes

MST_GEOCODING is typically invoked from PL/SQL rather than directly by end users. It is referenced by seventeen other database packages, which makes it a shared foundation routine for scheduling, shipping, and transportation processing across Oracle EBS. Customizations should call the documented functions instead of replicating time-zone logic, so that profile-driven and location-driven behavior remains consistent with Oracle's own code. Because the package resolves time zones from live configuration, environments with incomplete location or profile setup may return default or server-based values; administrators should validate WSH_LOCATIONS and time-zone profile settings before relying on the results in concurrent programs or interfaces. The package body is not referenced by any database object, so it is exclusively a provider, never a consumer, of dependent logic.