Results for “jtf_rs_resource”

35 results




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

Overview

JTF_RS_UPDATE_LOCATION_PUB is a public PL/SQL package owned by the APPS schema within the Oracle E-Business Suite. It belongs to the JTF product family, which provides the common resource management infrastructure used across CRM and field service applications. Its documented purpose is to update an existing resource record with location information — specifically a spatial geometry value — thereby keeping the resource's recorded position current within the E-Business Suite data model.

The package header identifies it as the "Resource Location Update API" with internal scope. It is classified as a PUB (public) API, indicating that it is intended for callers outside its own implementation layer, subject to standard EBS API calling conventions. The package header carries a version string dated 2005, reflecting the maturity of this interface across the 12.1.1 and 12.2.2 release lines, where it remains active according to its documented lifecycle status.

A key characteristic of this API is its use of the Oracle Spatial datatype MDSYS.SDO_GEOMETRY for the location parameter. This distinguishes it from simpler free-text location updates and ties the resource record to spatially enabled data, supporting geographic queries and mapping integrations.

Key Procedures and Functions

The package exposes a single documented procedure:

  • UPDATE_RESOURCE — Updates a resource record with the supplied location. The procedure accepts an API version identifier, an initialization flag for the message list, and a commit flag, following the standard EBS API parameter pattern. The target resource is identified by a resource identifier, and the new position is supplied as a spatial geometry value. An object version number, derived from the JTF_RS_RESOURCE_EXTNS table, is passed in and out to support optimistic locking; a mismatch causes the update to fail. The procedure returns the standard API output trio: return status, message count, and message data, allowing callers to detect success, failure, or unexpected errors and to retrieve the associated messages from the message list.

No other documented procedures or functions are exposed by this package. The procedure is documented as active and scoped for internal consumption, meaning it is not advertised as a general-purpose extension point but is nonetheless callable by dependent EBS components.

Tables Accessed

The package operates against a single documented table, referenced through an APPS synonym:

  • JTF_RS_RESOURCE_EXTNS — The resource extensions table, which stores the extended attributes of a resource beyond the base resource record. This package writes the location geometry into the record identified by the resource identifier, and reads and increments the OBJECT_VERSION_NUMBER column to enforce optimistic concurrency control. Because the object version number is passed as an IN OUT NOCOPY parameter, the caller receives the updated version value upon successful completion.

The involvement of a single table reflects the narrow, focused responsibility of the package: it does not orchestrate broader resource updates, but confines itself to the location attribute and its concurrency token.

Usage Notes

This API is typically invoked programmatically rather than interactively. Typical calling contexts include:

  • Resource maintenance forms or self-service pages where a user's or technician's location is captured or changed.
  • Concurrent programs and batch interfaces that synchronize resource locations from external systems such as mobile field service devices or dispatch engines.
  • Custom PL/SQL code that maintains resource geography, where the caller must supply a valid SDO_GEOMETRY value and the current object version number.

Callers should observe standard EBS API conventions: pass FND_API.G_FALSE for p_init_msg_list if the message list is already initialized, and for p_commit if transaction control is managed externally. The object version number must be fetched prior to the call and should be retained or refreshed afterward, since the procedure updates it in place. Handling of x_return_status, x_msg_count, and x_msg_data is mandatory for robust error reporting. The package is not documented as referenced by other packages, so dependencies flow inward to it rather than outward, and it should be treated as a stable but internal interface subject to the usual EBS patching lifecycle.