Results for “to_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The MDSYS.SDO package is a spatial cartridge package shipped as part of the Oracle Locator and Oracle Spatial option set, owned by the MDSYS schema. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 environment it provides the low-level geospatial encoding and dimensional-key primitives that higher-level Spatial and Location-Based Services functionality depends upon. Its principal business purpose is to convert human-readable coordinate, date, and numeric values into the compact binary dimensional keys (known historically as HHCODE values) that SDO indexes and spatial operators use internally, and to reverse that conversion.

The package does not implement application logic of its own; rather it exposes utility primitives that allow stored data to be keyed, compared, and searched efficiently. Because it is a database-level API rather than an EBS-owned API, it is classified in the ETRM as OTHER, and no EBS application tables are documented as being referenced or maintained through it. The package is referenced by zero other documented EBS packages, confirming its role as a foundational, standalone utility layer rather than a component of an interdependent application call graph.

Searches such as "soft sign 3.2 DMS" (an apparent attempt to express the 3.2 degree-format sign convention used when rendering decimal-degree-to-degree/minute/second conversions) commonly surface this package, since the encode/decode and latitude/longitude primitives are the objects that govern how DMS-style coordinate strings are produced and interpreted.

Key Procedures and Functions

The ETRM documents twelve entry points. No parameter lists are reproduced here; the descriptions below reflect the documented purpose of each named routine.

• COMPARE — Compares two HHCODE values (optionally a third) and returns a textual result indicating their relative ordering. Used to establish index ordering and range positioning.
• LATLONTOCODE — Converts a latitude/longitude pair expressed as NUMBER values into a single RAW HHCODE suitable for spatial indexing.
• DATETODIM — Converts a DATE value, with an optional component selector, into a RAW dimensional key, enabling temporal data to participate in the same encoded-key scheme as spatial data.
• BVALUETODIM — Encodes a bounded numeric value, given its lower bound, upper bound, and precision, into a RAW dimensional key.
• HVALUETODIM — Encodes one or more integer values of arbitrary bit length into a composite RAW dimensional key; this is the most general of the encoding routines and supports up to thirteen value/length pairs.
• ENCODE — Produces an encoded representation of an input value.
• DECODE — The inverse of ENCODE, recovering a value from its encoded form.
• TO_LAT — Extracts or converts a latitude value from its encoded representation.
• TO_LON — Extracts or converts a longitude value from its encoded representation.
• TO_DATE — Recovers a DATE value from a dimensional key produced by DATETODIM.
• TO_BVALUE — Recovers a bounded numeric value from a key produced by BVALUETODIM.
• TO_HVALUE — Recovers an integer value from a key produced by HVALUETODIM, completing the round-trip encode/decode family.

The routines are declared with pragma restrict_references (WNDS, RNDS, WNPS, RNPS), marking them as pure functions suitable for use in SQL statements and function-based indexes.

Tables Accessed

The ETRM metadata records no referenced tables for MDSYS.SDO, and no APPS synonyms are associated with the object. The package is stateless with respect to application data: it operates purely on its scalar inputs and returns computed RAW or VARCHAR2 outputs. All persistent spatial data resides in SDO geometry tables and their associated index metadata (for example the SDO_GEOMETRY columns and SDO_INDEX_METADATA structures maintained by the Spatial layer), not in tables directly read or written by this package.

Usage Notes

MDSYS.SDO is normally invoked indirectly. Oracle Spatial index maintenance, spatial operators, and Location-Based Services features call it internally when building or probing HHCODE-based indexes. In an EBS context, it may be reached through the Oracle Inventory and order-management location features, CRM territory and address geocoding, or any custom PL/SQL that stores SDO_GEOMETRY columns. Direct invocation from an EBS form or report is unusual and generally unnecessary.

Developers should treat this package as a database-supplied utility rather than an EBS customization point. Custom code requiring coordinate-to-code conversion should prefer the documented conversion functions above rather than reimplementing the encoding, and should be aware that the routines are deterministic, side-effect free, and therefore safe to call from SQL, views, and function-based indexes. Any call should be qualified with the MDSYS schema and the calling EBS user should be granted the appropriate Spatial privileges.