Search Results mdprvt_srid




Overview
Explore in AI Chat

Overview

The MDSYS.MDPRVT_SRID package body is an Oracle Spatial (Locator) internal utility that manages the registry of Spatial Reference Identifier (SRID) definitions used throughout the database. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, this package provides the private (MDPRVT) plumbing that supports the public spatial APIs exposed through MDSYS, such as SDO_CS and SDO_SRID. Its central responsibility is to resolve, validate, and cache metadata about coordinate systems, units of measure, geodetic versus projected reference kinds, and dimensional arity so that geometry operations behave consistently across applications.

The package is not an EBS business-layer component; it belongs to the database's spatial infrastructure that EBS inherits. It is deployed as a VALID object in the MDSYS schema and remains a dependency of a substantial portion of the spatial stack — ETRM records show it is referenced by 16 other packages and itself depends on MDSYS.ORDMD_SRID_LIBS and SYS.STANDARD. Because it is private and undocumented for external use, it should be treated as internal Oracle internals rather than a supported extension point.

Key Procedures and Functions

The documented API surface comprises seven procedures and functions, of which five are catalogued by name:

  • SDO_INVALIDATE_SRID_METADATA — Invalidates cached SRID metadata, forcing subsequent resolution calls to refresh from the authoritative spatial reference library. Typically invoked after SRID definitions are installed, updated, or patched.
  • GET_UNIT — Returns the unit-of-measure descriptor associated with a given spatial reference, enabling distance and area computations to apply the correct conversion factors.
  • IS_GEODETIC — Determines whether a specified SRID denotes a geodetic (latitude/longitude) coordinate system as opposed to a projected or local system, driving algorithm selection in downstream geometry operations.
  • GET_DIMS — Retrieves the number of dimensions (for example, two-dimensional or three-dimensional) declared for the referenced coordinate system.
  • GET_REF_KIND — Returns the classification of the reference system (geodetic, projected, local, and similar), allowing callers to branch on reference type.

The remaining two documented routines follow the same metadata-resolution pattern and are consumed internally by spatial code paths rather than by EBS application logic.

Tables Accessed

The ETRM metadata does not enumerate EBS-resident tables accessed through APPS synonyms, which is consistent with the package's role as a database-spatial utility. Its declared dependency is on MDSYS.ORDMD_SRID_LIBS, the Oracle-managed library of spatial reference definitions, from which SRID parameters, units, dimensional arity, and reference kinds are derived. Caching within the package reduces repeated lookups against that library during geometry processing. No application-level tables are documented as read or written.

Usage Notes

This package is invoked indirectly rather than directly. It is called by the broader MDSYS spatial packages — SDO_CS, SDO_SRID, SDO_GEOMETRY, and SDO_UTIL — whenever a geometry operation must resolve coordinate system metadata, such as transforming geometries, computing lengths in a specific unit, or validating SRIDs on insert. EBS components that store spatial data, including Oracle Field Service, asset and network geometry features, and any custom 11i or R12 tables using SDO_GEOMETRY columns, exercise this code path through those public APIs. Since MDPRVT_SRID is neither documented nor supported for direct invocation, customizations should use the public SDO_* interfaces instead. Administrators should also avoid granting direct execute privileges on this package and should revalidate it, along with its dependents, after any database patch that touches the MDSYS spatial stack.