Search Results predicated_join




Overview
Explore in AI Chat

Overview

MDSYS.SDO_SAM is the Oracle Spatial "Spatial Analysis and Mining" (SAM) package shipped with the Oracle Locate/Spatial option of the Oracle Database. In the Oracle E-Business Suite 12.1.1 and 12.2.2 technology stack, it resides in the MDSYS schema and is exposed to the EBS application schema through a PUBLIC synonym and a corresponding APPS synonym, which is how ETRM documents it as reachable from the EBS data dictionary. The package is classified as OTHER within the ETRM API inventory, meaning it is not an EBS-owned business API but a database-supplied utility that EBS modules may call when geospatial analysis is required.

Its business function is to deliver analytical operations over SDO_GEOMETRY data: clustering of spatial features, aggregation of numeric measures into tiled or binned regions, geometric simplification of layers, and determination of the spatial relationship between co-located feature sets. These capabilities support EBS deployments in which customer, supplier, asset, or delivery geometry is stored in Spatial-enabled columns and must be summarized for reporting, territory planning, or logistics analysis. The package status is recorded as VALID.

Key Procedures and Functions

ETRM documents fourteen callable units on MDSYS.SDO_SAM. The most significant are summarized below; parameter lists are intentionally omitted because the ETRM metadata does not expose them.

  • PREDICATED_JOIN — performs a spatial join between two feature collections using a spatial predicate, returning paired rows rather than a simple Cartesian comparison.
  • SIMPLIFY_GEOMETRY — reduces the vertex count of an individual geometry while preserving its overall shape, typically for display performance.
  • SIMPLIFY_LAYER — applies geometry simplification across an entire layer or feature set in a single operation.
  • INTERSECTION_RATIO — computes the proportional overlap between two geometries, used to quantify how much of one feature lies within another.
  • TILED_BINS — generates a regular tiling (bin grid) covering a specified spatial extent.
  • BIN_GEOMETRY — assigns an individual geometry to its corresponding tile or bin.
  • BIN_LAYER — bins an entire layer, producing the spatial assignment for every feature in the set.
  • SPATIAL_CLUSTERS — identifies groupings of spatially proximate features, the core spatial-mining operation of the package.
  • AGGREGATES_FOR_LAYER — computes aggregate measures across all features of a layer, optionally per spatial bin.
  • AGGREGATES_FOR_GEOMETRY — computes aggregate measures restricted to a single geometry window.
  • TILED_AGGREGATES — combines tiling and aggregation, returning summarized measures for each tile.
  • COLOCATED_REFERENCE_FEATURES — identifies reference features that are co-located with a given feature set, supporting association analysis.

Tables Accessed

The ETRM dependency record shows the package referencing only infrastructure objects rather than application tables: DUAL, ODCICONST, and PLITBLM, reached through APPS synonyms. DUAL is used for single-row expression evaluation, ODCICONST is the Oracle Data Cartridge constants package, and PLITBLM is the PL/SQL integer table type used for array-style parameters. All actual spatial data is supplied by the caller through SDO_GEOMETRY, SDO_DIM_ARRAY, SDO_REGIONSET, SDO_REGIONSET, SDO_ROWIDSET, and SDO_REGAGGRSET type instances. The package therefore reads no EBS transactional tables directly; it operates entirely on geometry and collection values passed in by the invoker.

Usage Notes

SDO_SAM is a database-tier API and is not surfaced through an EBS form or standard concurrent program. It is invoked from custom PL/SQL — for example, a custom concurrent program, a database package owned by an EBS module, or an ad hoc analytical script — when spatial summarization is required over EBS data. Because ETRM records zero packages referencing it within the application, any EBS usage is custom rather than part of delivered functionality. The dependency listing also shows SDO_SAM referencing itself, reflecting internal recursive calls within the package body.

Deployment prerequisites are the Oracle Spatial option and a valid MDSYS installation; the synonyms must be visible from the invoking schema. Operationally, SDO_SAM is best suited to batch or analytical workloads, since clustering and layer-level aggregation can be resource-intensive on large feature sets. Callers should ensure spatial indexes and metadata exist for the geometry columns involved, and should validate results against the SPATIAL_CLUSTERS and aggregate functions before using them to drive territory or logistics decisions.