Search Results csi_gis_instance_loc_pub_w




Overview
Explore in AI Chat

Overview

The APPS.CSI_GIS_INSTANCE_LOC_PUB_W package is a public wrapper package within the Oracle E-Business Suite Customer Intelligence (CSI) module, specifically supporting the GIS (Geographic Information System) integration layer for instance location data. The "W" suffix conventionally denotes a wrapper that shields external callers from the underlying implementation package, which in this case is APPS.CSI_GIS_INSTANCE_LOC_PUB. Its principal business purpose is to create and update geolocation information associated with customer product instances, enabling EBS installations to associate physical or logical assets with geographic coordinates for mapping, service coverage analysis, and field service dispatch.

The package is classified as OTHER in the ETRM API classification scheme, indicating that it is not a fully documented public API in the same manner as Installed Base or Order Management APIs, but rather an internal integration utility. The package status is VALID in both Oracle EBS 12.1.1 and 12.2.2, and it resides in the APPS schema with the standard dependent objects STANDARD and SYS.

Key Procedures and Functions

The ETRM metadata documents three procedures within this package. Parameter lists are not published and must not be assumed.

  • CREATEUPDATE_INST_GEOLOC_INFO — The primary business-facing routine. It creates a new geolocation record for a customer product instance or updates an existing one, reconciling the instance identifier with its associated geographic attributes.
  • ROSETTA_TABLE_COPY_IN_P1 — A utility procedure used to marshal inbound tabular data (typically PL/SQL nested tables) into the RosettaNet messaging structure. It supports the inbound leg of the GIS integration pipeline.
  • ROSETTA_TABLE_COPY_OUT_P1 — The outbound counterpart, converting internal cursor or table structures into a RosettaNet-compatible payload prior to transmission.

The RosettaNet naming convention confirms the package participates in B2B or inter-application exchange of instance location data, likely in the context of the CSI GIS integration with external mapping, logistics, or partner systems.

Tables Accessed

The documented table reference is PLITBLM, accessed through an APPS synonym. PLITBLM is the PL/SQL Character Table of VARCHAR2(100) — a standard Oracle Applications generic nested-table type rather than an application data table. Its presence here indicates the copy-in and copy-out procedures operate on transient in-memory collections of 100-character strings rather than directly on persistent CSI base tables. Any persistent writes to instance geolocation records would be performed by the underlying CSI_GIS_INSTANCE_LOC_PUB package, which this wrapper encapsulates. Consumers should therefore treat the wrapper as an orchestration layer rather than a table-owning entity.

Usage Notes

Because the package is a wrapper, it is normally invoked by other PL/SQL components rather than directly by end users or concurrent programs. Typical invocation patterns include:

  • Service-oriented integrations that accept geolocation updates from external GIS providers.
  • Custom concurrent programs that batch-load customer product instance coordinates from staging tables.
  • Internal EBS module logic (for example, Field Service or Asset Tracking) requiring instance geolocation creation or maintenance.

The dependency listing shows the package depends on CSI_GIS_INSTANCE_LOC_PUB and is referenced only by itself, with zero external referencing packages documented. This self-reference suggests internal recursion or overloaded entry points. Customizations should call CSI_GIS_INSTANCE_LOC_PUB directly where possible, reserving the wrapper for interface-layer completeness. As with any EBS 12.1.1/12.2.2 integration package, all calls must be wrapped in a savepoint-aware error handler, since geolocation writes participate in the standard EBS transaction and concurrency model.