Search Results sdo_overlapbdyintersect




Overview
Explore in AI Chat

Overview

MDSYS.SDO_TPFNS is an Oracle Spatial and Graph utility package that resides in the MDSYS schema, the schema that owns the core Oracle Locator and Oracle Spatial feature set. The name derives from its role as a repository of topology and filter helper functions consumed by the spatial operator layer. In the context of Oracle E-Business Suite 12.1.1 and 12.2.2, the package is not an EBS application object; it is part of the shipped Oracle Database spatial option that the EBS technology stack installs and validates alongside the APPS schema. EBS modules that store or query geometry — for example Oracle Field Service, Oracle Inventory warehouse and bin geometry, Oracle Property Manager lease spaces, and Oracle Fusion-style mapping extensions delivered through the 12.x technology stack — indirectly exercise this package whenever spatial predicates are evaluated against an SDO_GEOMETRY column.

The ETRM record confirms the object is VALID in the MDSYS schema and classifies its API surface as OTHER, indicating that it is an internal support package rather than a documented, customer-callable API.

Key Procedures and Functions

The ETRM metadata documents zero publicly listed procedures or functions. This is consistent with the object's classification as an internal helper package: its callable units are exposed for use by other MDSYS packages rather than for direct invocation by EBS developers. The dependency list is the primary evidence of its purpose. SDO_TPFNS references SDO_GEOMETRY, SDO_TOPO_GEOMETRY, SDO_TOPO_OBJECT_ARRAY, SDO_INDEX_METHOD_10I, and the Oracle Data Cartridge interface ODCIINDEXCTX, which together indicate that the package implements topology-aware predicate and filter logic used during spatial index evaluation.

Tables Accessed

No APPS-synonym tables are documented as being referenced by this package. The package operates on Oracle Spatial metadata and topology structures maintained in the MDSYS schema rather than on EBS application tables. Where EBS data is involved, access occurs indirectly: an EBS table containing an SDO_GEOMETRY column is passed to the spatial operator layer, which in turn calls SDO_TPFNS routines. The referenced SDO_TOPO_OBJECT_ARRAY and SDO_TOPO_GEOMETRY types show that topology object arrays are read and manipulated in memory rather than through application-owned tables.

Usage Notes

SDO_TPFNS is never invoked directly from an EBS form, concurrent program, or custom PL/SQL unit. It is reached only through the spatial operator functions that depend on it. The ETRM dependency list shows that twelve spatial operators reference SDO_TPFNS, including SDO_ANYINTERACT, SDO_CONTAINS, SDO_COVEREDBY, SDO_COVERS, SDO_EQUAL, SDO_FILTER, SDO_INSIDE, SDO_ON, SDO_OVERLAPBDYDISJOINT, SDO_OVERLAPBDYINTERSECT, SDO_OVERLAPS, and SDO_TOUCH. A recursive reference to SDO_TPFNS itself also appears, indicating internal reuse across the package body.

Consequently, any EBS SQL statement or view that applies one of these operators to a geometry column — for example a WHERE SDO_FILTER(...) or WHERE SDO_RELATE(...) clause in a mapping or asset-location query — triggers execution of the relevant SDO_TPFNS helper code at runtime. Diagnosing performance or correctness issues with spatial queries in EBS therefore requires familiarity with this package even though it is never named explicitly in application code. Because the package ships with the database option and not with the EBS application, patch and upgrade activity affecting it originates from Oracle Database releases and spatial patches, not from EBS patching. Customers should not modify or recompile the package body, as doing so can invalidate dependent spatial operators and compromise index behaviour.