Search Results track_ha_record

Overview

APPS.CSM_HA_EVENT_PKG is a PL/SQL package body in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments that supports the High Availability (HA) and diagnostic tracking infrastructure for Oracle Field Service / TeleService (CSM) modules. The package forms part of the broader CSM_HA_* object family, which manages session state, payload capture, sequence mapping, and audit information related to concurrent program execution and workflow activity within a high-availability or clustered deployment configuration.

The package depends extensively on Oracle Workflow (WF_*) tables, Application Object Library (FND_*) views and tables, and JTM concurrent request data, indicating that its primary business function is to observe and record the flow of work items, simultaneous concurrent processing, and the associated data payloads that move across the HA boundaries of the CSM environment. It also references ASG_* (Apps Service/Depot management) objects, suggesting its scope spans field service resource, task, and inquiry tracking.

Key Procedures and Functions

The ETRM metadata documents ten callable units within the package body:

• BEGIN_HA_TRACKING — Initializes an HA tracking session, establishing the context under which subsequent tracking and payload operations are recorded.
• END_HA_TRACKING — Closes the active HA tracking session and persists or finalizes the accumulated tracking data.
• SAVE_SEQUENCE — Persists sequence-related mapping information, likely into CSM_HA_SEQ_MAPPINGS or CSM_HA_SESSION_SEQ_VALUES, to preserve record ordering across HA nodes.
• GET_XML_PAYLOAD — Retrieves an XML-formatted payload, presumably reconstructed from CSM_HA_PAYLOAD_DATA and its sibling table CSM_HA_PAYLOAD_DATA_S (the table the user searched for).
• TRACK_HA_RECORD — Records an individual business record into the HA tracking store, capturing the primary key and related attributes.
• TRACK_HA_ATTACHMENTS — Captures attachment metadata associated with a tracked record, leveraging FND_DOCUMENTS and related attachment structures.
• GET_PK_COLUMN_NAME — Determines the primary key column for a given entity, supporting generic record tracking.
• GET_HA_PROFILE_VALUE — Reads a system profile option value (via FND_PROFILE) that governs HA tracking behaviour.
• GET_PREDICATE_CLAUSE — Builds a dynamic SQL predicate clause used when querying tracked records.
• GET_LISTFROM_STRING — Parses a delimited string into a list structure, likely returning a CSM_VARCHAR_LIST or similar collection.

Tables Accessed

The package reads and writes several categories of tables through APPS synonyms. The core HA persistence tables are CSM_HA_PAYLOAD_DATA, CSM_HA_PAYLOAD_DATA_S, CSM_HA_SESSION_INFO, CSM_HA_SESSION_INFO_S, CSM_HA_SEQ_MAPPINGS, CSM_HA_SESSION_SEQ_VALUES, CSM_HA_AUX_MAPPINGS, CSM_HA_RESP_MAPPINGS, CSM_HA_ACTIVE_CONC_DATA, and CSM_HA_ACTIVE_WF_COMPONENTS. These hold payload XML, session metadata, sequence mappings, auxiliary and responsibility mappings, and active concurrent/workflow component state.

Supporting tables include ASG_BASE, ASG_DEFERRED_TRANINFO, ASG_PUB_ITEM, ASG_SYSTEM_DIRTY_QUEUE, ASG_USER, and ASG_USERS_INQINFO for service resource and inquiry tracking; CSF_ACCESS_HOURS_B and CSF_REQUIRED_SKILLS_B for field service scheduling data; CS_INCIDENT_LINKS and CS_INCIDENT_LINKS_EXT for incident relationships; CUG_INCIDNT_ATTR_VALS_B for incident attribute values; and the FND and WF families for user, responsibility, request group, document, notification, and workflow activity metadata.

Usage Notes

CSM_HA_EVENT_PKG is not referenced by any dependent package per the ETRM metadata, although three other packages are documented as referencing it. It is therefore typically invoked directly by Oracle Forms, concurrent programs, or custom extensions rather than being buried deep in a call stack. The GET_XML_PAYLOAD and SAVE_SEQUENCE routines are commonly called during HA synchronization operations, while TRACK_HA_RECORD and TRACK_HA_ATTACHMENTS are used when business transactions must be logged for later replay or audit. GET_HA_PROFILE_VALUE gates behaviour on profile settings, so administrators should verify the relevant CSM HA profile options before enabling tracking in a production environment.