Search Results get_property_name

Overview

APPS.RRS_SITE_UTILS is a PL/SQL utility package belonging to the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, specifically associated with location, site, and trade-area functionality. Its source header (RRSUTILS.pls 120.8, dated 2008/01/25) indicates it has been a stable component of the Applications schema for many releases. The package exposes a set of reusable functions and procedures that retrieve and format site-related descriptive data, resolve user-defined flexfield attribute values, manage temporary staging data used for map rendering, and maintain geometry (spatial) information for locations. It is classified under the ETRM API classification "OTHER," meaning it is not a public, supported business API in the same sense as an interface table or a formal open interface, but rather an internal helper package invoked by other application code. It is referenced by two other packages, confirming its role as a shared utility layer for site and location processing.

Key Procedures and Functions

The documented surface of the package comprises seventeen procedures and functions. The most prominent in the context of the search term "insert_temp_for_map" is INSERT_TEMP_FOR_MAP, a procedure that populates the RRS_SITE_TMP staging table with the site records that will be rendered on a map, accepting a session identifier, a context flag, and optional collections of site IDs, tag codes, and X/Y coordinates, and returning a generated theme identifier. Its counterpart, CLEAR_TEMP_FOR_MAP, removes the transient rows associated with a given session and optionally deletes the associated theme.

Several functions return descriptive text for a site or location: GET_LOCATION_ADDRESS, GET_SITE_DISPLAY_NAME, GET_LOCATION_NAME, GET_PROPERTY_NAME, and GET_ADDRESS each resolve identifiers into human-readable address or name strings. GET_USER_ATTR_VAL resolves a value from user-defined attribute groups by attribute group type, name, attribute name, object name, and primary key value. GET_UOM_COLUMN_PROMPT returns the display prompt associated with a unit-of-measure class.

Spatial handling is provided by UPDATE_GEOMETRY_FOR_LOCATIONS, which updates the latitude, longitude, and status of a location and returns a numeric status; GET_ORDINATE, which extracts a single ordinate from an MDSYS.SDO_GEOMETRY object; and GET_GEOMETRY_FOR_LOCATION and SET_GEOMETRY_SRC_FOR_LOCATION, which retrieve and set the geometry source for a location. Additional utilities include DEFAULT_SITE_NUMBERS, ADD_FAVORITE_OBJECTS, ISAGANDCLSASSOCDELETABLE, and GET_MULTIAG_COUNT, which support site numbering defaults, favorite-object maintenance, association deletability checks, and multi-aggregation counting respectively.

Tables Accessed

The package reads and writes a focused set of tables through APPS synonyms. Core site and location data is drawn from RRS_SITES_B, PN_LOCATIONS_ALL, HZ_LOCATIONS, and MTL_UNITS_OF_MEASURE, with MTL_UOM_CONVERSIONS used for unit-of-measure conversions. Staging and map-related activity is supported by RRS_SITE_TMP. Trade area definitions reside in RRS_TRADE_AREA_GROUPS_B, RRS_GROUP_TRADE_AREAS, and RRS_LOC_TRADE_AREA_GRPS. Property data is read from PN_PROPERTIES_ALL. Numbering defaults come from RRS_DEFAULT_SITE_NUMBER_S, while user personalization and favorites are stored in RRS_USER_FAVORITES and RRS_FAVORITE_S. Attribute-group resolution draws on EGO_FND_DSC_FLX_CTX_EXT and EGO_RESULTS_FMT_USAGES.

Usage Notes

RRS_SITE_UTILS is typically invoked from Oracle Forms and from other PL/SQL packages rather than directly by end users or concurrent programs. The map-related procedures INSERT_TEMP_FOR_MAP and CLEAR_TEMP_FOR_MAP are intended to bracket a map display session: the caller passes a session identifier, stages the relevant sites, and later clears the transient data. Because the package is classified as "OTHER" and is not a documented public API, customizations that call it should be treated as non-supported extensions and validated against the target release. Direct DML against RRS_SITE_TMP outside these procedures is not recommended, since the package manages the lifecycle of that staging data.