Results for “csf_gps_pub”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.CSF_GPS_PUB is the public API package for the Oracle E-Business Suite GPS (Global Positioning System) integration, part of the Field Service / TeleService technology stack. It provides a stable, documented interface through which other application modules and custom extensions can determine whether GPS tracking is enabled for the current installation, resolve user-facing GPS labels, retrieve the last known location of a device or resource, and bulk-load or purge GPS location feed data. The package is defined with AUTHID CURRENT_USER, meaning that it executes with the privileges of the calling session rather than the owner, and it is classified as a PUB interface, indicating that Oracle supports its use by external callers.

The package sits between GPS hardware or vendor telemetry feeds and the EBS tables that store device, vendor, and location information. Vendor hardware typically transmits latitude, longitude, speed, direction, parked time, and address readings; CSF_GPS_PUB normalises these readings and persists them. In the context of searches such as "non gps sidekick", the package is relevant because it is the layer that determines whether GPS processing is active and which records require a GPS-dependent treatment versus a manual or non-GPS fallback. IS_GPS_ENABLED and GET_GPS_LABEL in particular allow calling code to branch cleanly between GPS-driven and non-GPS behaviour without querying profile options directly.

Key Procedures and Functions

• IS_GPS_ENABLED — Function returning a VARCHAR2 indicator of whether GPS functionality is enabled for the environment. Used as the primary gate before invoking any GPS-dependent logic.
• GET_GPS_LABEL — Function returning the descriptive label associated with a GPS device, resource, resource type, or date. Intended for display purposes in forms and reports.
• GET_LOCATION (procedure) — Returns the current location for a device or resource as a set of OUT parameters: feed time, status code and its meaning, latitude, longitude, speed, direction, parked time, address, creation date, and device tag.
• GET_LOCATION (function) — Overloaded variant returning the location as an MDSYS.SDO_POINT_TYPE, suitable for Spatial queries and mapping integrations.
• SAVE_LOCATION_FEEDS — Standard EBS API-convention procedure that bulk-inserts a set of location feed rows from array parameters (device, feed time, status, latitude, longitude, speed, direction, parked time, and address). It accepts an API version, message list and commit flags, and returns standard return status, message data, and message count values.
• PURGE_LOCATION_FEEDS — Concurrent-program-style procedure (errbuf/retcode signature) that removes historic location feed rows, optionally scoped by vendor or device.
• ADD_LANGUAGE — Maintains translated GPS metadata, populating or refreshing language-specific descriptions.

Tables Accessed

The package reads and writes CSF_GPS_DEVICES and CSF_GPS_DEVICE_ASSIGNMENTS to resolve which device is attached to which resource, and CSF_GPS_LOCATION_FEEDS (with its sequence CSF_GPS_LOCATION_FEEDS_S) as the primary store for incoming telemetry. Vendor configuration is read from CSF_GPS_VENDORS_B and CSF_GPS_VENDORS_TL, with CSF_GPS_VENDOR_STATUS_MAPS translating status codes into business meanings. FND_LANGUAGES and FND_PROFILE_OPTION_VALUES support language handling and the enablement check, while JTF_TERR_RSC_ALL supplies resource and territory information used to validate resource references.

Usage Notes

CSF_GPS_PUB is typically invoked from Service / Field Service forms, from concurrent programs that ingest vendor feed files, and from custom PL/SQL that needs device location data. SAVE_LOCATION_FEEDS and PURGE_LOCATION_FEEDS are the standard entry points for integration and housekeeping jobs, while IS_GPS_ENABLED and GET_GPS_LABEL should be called before attempting any GPS-specific processing so that environments without GPS provisioning degrade gracefully. Because the package is referenced by three other packages, changes to its behaviour can propagate broadly; callers should use only the documented signatures and rely on the standard return-status and message-count conventions when handling errors.