Search Results csl_jtf_resource_extns_acc_pkg




Overview
Explore in AI Chat

Overview

CSL_JTF_RESOURCE_EXTNS_ACC_PKG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. It participates in the Oracle Territory Manager (JTM/CSL) replication and hook framework, which propagates changes to shared reference entities, such as resources and their extension attributes, across the EBS data model. The package is classified as OTHER within the ETRM metadata because it is not a standard public API in the conventional sense; instead, it acts as an internal handler that the territory and resource-management hooks invoke.

The package body (header identifier cslreacb.pls, version 115.5, last modified 2003) operates against the JTF_RS_RESOURCE_EXTNS table, exposing the four canonical DML event handlers that Oracle's replication framework requires: a replicate check, plus insert, update, and delete. It shares constants and logging utilities with JTM_HOOK_UTIL_PKG, including publication item metadata and debug-level control, ensuring that replication events are traced consistently with the rest of the JTM table-hook infrastructure. Three other packages reference it, confirming that it is embedded in a wider dependency chain rather than being called directly by end users.

Key Procedures and Functions

  • REPLICATE_RECORD — Determines whether a given resource extension record qualifies for replication. It queries JTF_RS_RESOURCE_EXTNS to locate the resource identifier, returns TRUE when the record is found and eligible, and returns FALSE when the record cannot be resolved. Debug-level messages are written through JTM_MESSAGE_LOG_PKG at FULL, MEDIUM, and ERROR thresholds, providing traceability during replication runs.
  • INSERT_RESOURCE_EXTNS — Handles the insert-side propagation of resource extension data, publishing the record to downstream territory consumers when a new extension row is created.
  • UPDATE_RESOURCE_EXTNS — Handles the update-side propagation, re-publishing extension changes so that territory definitions and related structures remain synchronized.
  • DELETE_RESOURCE_EXTNS — Handles the delete-side propagation, removing or invalidating the corresponding published representation of the extension row.

Tables Accessed

The documented table access is to JTF_RS_RESOURCE_EXTNS, read through the APPS synonym. REPLICATE_RECORD uses it primarily as an existence and identifier resolution source: it selects RESOURCE_ID for the supplied resource extension identifier. The insert, update, and delete handlers operate on the same table as the source of the change events that are subsequently replicated. The package also references the publication item JTF_RS_RESOURCE_EXTNS through JTM_HOOK_UTIL_PKG.t_publication_item_list and writes diagnostics to the JTM message log, both of which are framework support structures rather than business tables.

Usage Notes

This package is not intended for direct invocation by custom code. It is registered with the JTM hook and replication framework so that DML against JTF_RS_RESOURCE_EXTNS triggers the appropriate handler automatically. Typical invocation paths include territory and resource forms that maintain resource extension attributes, concurrent processes that rebuild or propagate territory data, and internal framework calls during multi-org or cross-instance replication. Because the handlers are driven by record-level events, they execute during normal maintenance activity rather than on demand.

Administrators investigating replication failures should enable debug logging through JTM_HOOK_UTIL_PKG so that Replicate_Record emits its entry, success, and error messages. The most common diagnostic signature is a "Could not find resource_extn_id" error, which indicates that the requested extension row is absent from JTF_RS_RESOURCE_EXTNS in the current instance. The package is compatible with both EBS 12.1.1 and 12.2.2, as its dependencies are longstanding JTM framework objects. When extending replication behavior, developers should override or wrap the framework hooks rather than modify this package body, and should preserve the publication item name so that downstream subscribers continue to receive events.