Search Results sdo_topo




Overview
Explore in AI Chat

Overview

The MDSYS.SDO_TOPO package is the core PL/SQL application programming interface for Oracle Spatial's topology data model, exposed in Oracle E-Business Suite environments through the MDSYS schema and surfaced to the APPS schema via synonyms. Within Oracle EBS 12.1.1 and 12.2.2, this package provides the programmatic foundation for managing topological relationships among spatial features — nodes, edges, and faces — rather than managing geometries in isolation. It is classified as an OTHER API in the ETRM documentation, reflecting that it is an Oracle Spatial foundation utility rather than a business-process concurrent program or a form-bound API. The package is VALID in the documented environment and exposes 30 documented procedures and functions that cover topology creation, metadata initialization, geometry layer management, spatial relationship evaluation, and export/import lifecycle handling. Its principal role in an EBS context is to support location-based functionality such as network routing, service territory definition, field service dispatching, asset tracking, and any custom spatial analysis that requires shared-edge consistency between adjacent features. Because topology definitions must be maintained consistently across environments, the package's lifecycle procedures are directly relevant to EBS cloning, patching, and migration activities.

Key Procedures and Functions

The documented procedures and functions group into several functional areas:

Tables Accessed

Per the documented metadata, the package references the DUAL and PLITBLM tables via APPS synonyms. DUAL is used for single-row expression evaluation in PL/SQL and SQL statements. PLITBLM is the standard PL/SQL table lookup mechanism used by the compiled package body. Beyond these, SDO_TOPO operates against the internal Oracle Spatial topology metadata tables (user-owned topology and topology metadata tables created by INITIALIZE_METADATA), and its dependencies reference the SDO_GEOMETRY, SDO_TOPO_GEOMETRY, SDO_TGL_OBJECT_ARRAY, SDO_TOPO_OBJECT_ARRAY, and SDO_NUMBER_ARRAY types. These objects are described here in terms of documented dependencies only; no undocumented table structures are assumed.

Usage Notes

SDO_TOPO is typically invoked from custom PL/SQL code, database triggers, or EBS concurrent programs that require topological correctness rather than custom forms. It may be called directly by Spatial-related functionality, as indicated by its documented dependency relationships with SDO_NET, SDO_TOPO_GEOMETRY, and SDO_TPFNS, and it is referenced by three other packages. In EBS environments, use cases include building and maintaining service or distribution networks, computing adjacency and containment relationships for territory assignment, and aligning field asset geometries. The EXECUTE privilege is granted publicly, though DDL-style operations such as CREATE_TOPOLOGY should be performed under controlled change management. During cloning or data migration, PREPARE_FOR_EXPORT and INITIALIZE_AFTER_IMPORT must be sequenced correctly to preserve topology integrity. As with all MDSYS Spatial APIs, SDO_TOPO should be used only after the Spatial option is enabled in the database, and topologies should be tested in a non-production environment before deployment.