Search Results internal_det_chain
Overview
MDSYS.SDO_CS is the Oracle Spatial Coordinate Systems package, a PL/SQL API that provides coordinate system transformation and management services for geometric and geographic data stored in the Oracle database. In the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, this package resides in the MDSYS schema—the schema that owns Oracle Spatial and Graph—and is exposed to the EBS application through a PUBLIC synonym named SDO_CS. The package is classified under the generic "OTHER" API category within ETRM, but its role is foundational: it allows EBS modules that store spatial or location-aware data to convert geometries between coordinate reference systems (CRSs), manage SRID chains, handle EPSG-based reference systems, and validate well-known text (WKT) definitions of coordinate systems.
The package carries a VALID status and, per the documented ETRM metadata, exposes 122 procedures and functions. It is referenced by 19 other database objects, indicating that it functions as a central transformation engine within the Oracle Spatial stack rather than an isolated utility.
Key Procedures and Functions
The documented API surface is broad and can be grouped by purpose:
- Geometry transformation: TRANSFORM_ORIG and TRANSFORM_ORIG_WITH_ARCS transform individual geometric objects between coordinate systems; TRANSFORM_LAYER and TRANSFORM_LAYER_WITH_ARCS perform the same operation across an entire spatial layer. VIEWPORT_TRANSFORM converts geometries for display within a defined viewport.
- Validation and parsing: VALIDATE_WKT and INTL_VALIDATE_WKT validate WKT coordinate system definitions; INTERNAL_READ_PROJ_FROM_WKT reads projective parameters from WKT input; INTERNAL_DET_SRID_WKT derives an SRID from a WKT definition.
- Chain determination: DETERMINE_DEFAULT_CHAIN, DETERMINE_CHAIN, INTERNAL_DET_CHAIN_VARCHAR, and INTERNAL_DET_CHAIN resolve the transformation path (chain) between two coordinate systems.
- SRID mapping: MAP_ORACLE_SRID_TO_EPSG and MAP_EPSG_SRID_TO_ORACLE convert between Oracle-assigned SRIDs and EPSG codes.
- Operation management: CREATE_PREF_CONCATENATED_OP, CREATE_CONCATENATED_OP, DELETE_OP, and ADD_PREFERENCE_FOR_OP manage concatenated coordinate operations and user preferences for those operations.
No parameter lists are documented for these routines in the ETRM extract, and they are intentionally omitted here.
Tables Accessed
SDO_CS reads and writes a defined set of Spatial metadata objects through APPS synonyms, including XMLTYPE, DBMS_LOB, DBMS_OUTPUT, DUAL, PLITBLM, XDBURITYPE, and XMLAGG. Internally, the package references MDSYS objects such as EPSG_PARAMS, SDO_DIM_ARRAY, SDO_GEOMETRY, SDO_SRID_CHAIN, SDO_SRID_LIST, SDO_TRANSIENT_RULE_SET, TFM_PLAN, and XMLTYPE. These objects supply the EPSG parameter dictionary, dimension arrays, SRID chain and list definitions, transient transformation rule sets, and transformation plans used when resolving and applying coordinate conversions.
Usage Notes
In EBS 12.1.1 and 12.2.2, SDO_CS is not typically invoked directly by end users. It is called indirectly by higher-level Spatial packages and triggers, including SDO_3GL, SDO_GEOM, SDO_UTIL, SDO_PQRY, SDO_GEOR, SDO_TIN_PKG, SDO_PC_PKG, and SDO_CSW_PROCESS (for CSW/WFS services), as well as by SRID and coordinate-operation triggers such as CS_SRS_TRIGGER, SDO_CRS_INSERT_TRIGGER, and SDO_PREFERRED_OPS_* triggers that enforce referential consistency when coordinate system definitions change. Custom EBS extensions that store SDO_GEOMETRY columns, or that integrate with Oracle Spatial for asset/network location data, may invoke SDO_CS functions directly to reproject data or validate SRID definitions. Because the package is owned by MDSYS and accessed through the PUBLIC synonym, EXECUTE privileges must be granted appropriately to any EBS application schema that calls it.