Search Results convert_dms_or_dm_to_dd




Overview
Explore in AI Chat

Overview

CSI_GIS_INSTANCE_LOC_UTL_PKG is a utility package in the APPS schema that supports Oracle E-Business Suite's Geographic Information System (GIS) integration for item instance locations. Its principal business function is to validate and transform geographic coordinate data associated with item instance geolocations, and to verify instance numbers passed to the GIS processing layer. The package is classified as an OTHER-type API, indicating that it is an internal technical utility rather than a published business API; it exists to serve the higher-level public package CSI_GIS_INSTANCE_LOC_PUB, which drives the GIS instance location workflow. In EBS 12.1.1 and 12.2.2, the object is documented as VALID, meaning it compiles successfully and its dependents resolve correctly. The package depends on SYS.STANDARD and is referenced by CSI_GIS_INSTANCE_LOC_PUB, by itself, and by the MTL_EAM_ASSET_NUMBERS_ALL_V view. This dependency profile confirms that the utility sits beneath both the GIS public API and certain asset-number viewing constructs.

Key Procedures and Functions

The ETRM metadata documents eight procedures and functions within this package. Their purposes are as follows:

  • VALIDATE_INSTANCE_NUMBER — Confirms that a supplied item instance number is valid for use in GIS instance location processing, guarding downstream logic against missing or malformed instance identifiers.
  • VALIDATE_LATITUDE_LONGITUDE — Checks that latitude and longitude values supplied by a caller fall within acceptable geographic ranges before they are persisted.
  • CONVERT_DMS_OR_DM_TO_DD — Converts coordinate values expressed in degrees-minutes-seconds (DMS) or degrees-minutes (DM) notation into decimal degrees (DD).
  • CALCULATE_DD — Performs the core decimal degree computation, deriving a DD coordinate from the constituent degree, minute, second, and direction elements.
  • GET_DEGREES_FROM_DD — Extracts the whole-degree component from a decimal degree value, typically as part of reversing a DD value back into DMS form.
  • GET_MINUTES_FROM_DD — Extracts the minutes component from a decimal degree value.
  • GET_SECONDS_FROM_DD — Extracts the seconds component from a decimal degree value.
  • GET_DIRECTION_FROM_DD — Determines the compass direction (for example, north/south or east/west) associated with a decimal degree value.

Together these routines cover the validation and bidirectional conversion of coordinate representations used in GIS-enabled instance location records.

Tables Accessed

The package accesses its documented tables through APPS synonyms:

  • CSI_II_GEOLOCATIONS — The primary geolocation table for item instances. The package reads and, where applicable, validates or derives coordinate values that belong to rows in this table.
  • CSI_ITEM_INSTANCES — The item instance master. It is referenced to confirm that the instance for which a geolocation is being processed exists and is valid.
  • DUAL — Used for scalar computations, particularly for the coordinate conversion functions and directional logic that do not require persistent storage access.

No additional tables are documented as direct references within the package body.

Usage Notes

CSI_GIS_INSTANCE_LOC_UTL_PKG is an internal utility and is not intended for direct invocation by end users or by general custom code. It is normally called indirectly through CSI_GIS_INSTANCE_LOC_PUB, which is its sole documented package-level consumer. In practice it is invoked when an item instance geolocation is created or updated, either from a GIS-enabled form, from concurrent processing that imports or reconciles location data, or from integration code that submits coordinates in DMS or DM format. Because the package enforces latitude/longitude range validation and instance-number checks, callers should expect exceptions or null returns when invalid data is supplied. Customers and partners extending GIS instance location behavior should call the public package rather than this utility, since the utility's signatures and internal logic are Oracle-owned and may change between releases. The reference from MTL_EAM_ASSET_NUMBERS_ALL_V indicates that some asset-number view logic also relies on this package's validation or conversion routines, so changes to it should be assessed against that view during upgrades between 12.1.1 and 12.2.2.