Search Results import_instance_geo_location




Overview
Explore in AI Chat

Overview

CSIGISINSTANCELOCPUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM documentation as a PUB (public) API. It belongs to the Oracle Enterprise Asset Management (eAM) and Installed Base product family, more specifically the CSI (Customer Support Installed Base) module, which manages the lifecycle, configuration, and location of customer assets and item instances. The package provides a programmatic interface for creating, updating, and importing geographic location information associated with item instances held in the Installed Base.

Its central business purpose is to bridge the Installed Base data model with geographic information system (GIS) or geolocation functionality. Organizations use it to maintain latitude, longitude, and related geolocation attributes for instances so that those records can be plotted, tracked, or analyzed spatially. In on-premise Oracle EBS 12.1.1 and 12.2.2 environments, the package is validated and advertises two documented entry points, both of which are intended to be called by other application code rather than relied upon directly as end-user features.

Key Procedures and Functions

The ETRM metadata identifies two documented procedures within this package:

  • CREATEUPDATE_INST_GEOLOC_INFO — This procedure performs the core create-or-update operation for an instance's geolocation record. It is designed so that a single call either inserts a new geolocation entry or modifies an existing one for a given item instance, following the common EBS API pattern for idempotent maintenance routines.
  • IMPORT_INSTANCE_GEO_LOCATION — This procedure serves the bulk or batch import path. It reads staged geolocation data and applies it to the Installed Base instance records, typically after the data has been validated and placed into the appropriate interface table.

The metadata does not document the formal parameter lists for these procedures, and no parameter signatures are reproduced here. Callers should inspect the package specification in the EBS instance before invoking them.

Tables Accessed

The documented tables referenced through APPS synonyms are:

  • CSI_II_GEOLOC_INTERFACE — The interface (staging) table that holds inbound geolocation records prior to processing. It is the source on which IMPORT_INSTANCE_GEO_LOCATION depends.
  • CSI_ITEM_INSTANCES — The primary Installed Base item instance table. The package reads and updates this table to associate geolocation information with the correct instance record, and it is the target of the create-or-update logic.
  • PLITBLM — A standard Oracle Application Object Library multiline message table used to return error, warning, and informational messages to the calling program. Its presence confirms that the package follows the standard EBS API error-handling convention of stacking messages for later retrieval.

Usage Notes

CSI_GIS_INSTANCE_LOC_PUB is a server-side public API. It is referenced by the package itself and by the wrapper package CSI_GIS_INSTANCE_LOC_PUB_W, which typically exposes the API to form-based or concurrent processing. The dependency on FND_API and SYS.STANDARD indicates that it relies on the Oracle Application Object Library API standards for return status and message handling. Typical invocation patterns include Oracle Forms or OAF pages that capture geolocation data for an instance, concurrent programs that run the import routine against CSI_II_GEOLOC_INTERFACE, and custom extensions or integrations that call the procedures directly to synchronize external GIS systems with Installed Base. Because it is a PUB classification, it is a supported integration point, though callers should always validate input, commit or roll back transactions explicitly, and inspect the returned FND_API status and PLITBLM messages after each call.