Search Results track_ha_attachments

Overview

CSM_HA_EVENT_PKG is an Oracle E-Business Suite package owned by the APPS schema that implements the high-availability (HA) event tracking and payload capture framework used by Oracle's Field Service and telephony/contact-center integrations. Its principal business function is to record, sequence, and serialize database changes (DML) that occur against key service objects so those changes can be reliably propagated to external or downstream HA consumers, even when the originating transaction is long-running, distributed, or spans multiple application tiers.

The package operates with AUTHID CURRENT_USER, so name resolution and privilege checks are performed against the invoking schema rather than APPS. It maintains session-scoped global state — session sequence, start/end timestamps, payload sequence boundaries, and the current payload identifier — which are declared at package level. This state allows the framework to bracket a unit of work with begin/end calls and to correlate captured changes to a specific HA session. In Oracle EBS 12.1.1 and 12.2.2, the package is part of the service/CSM module stack and supports the change-data-capture needs behind High Availability and synchronization features.

Key Procedures and Functions

• BEGIN_HA_TRACKING — Opens an HA tracking session and initializes package-level state (session sequence and start time). Returns status and error message outputs.
• END_HA_TRACKING — Closes the HA tracking session, finalizes the end time and payload sequence boundaries, and returns status/error information.
• SAVE_SEQUENCE — Persists the payload sequence information for a given session and action, optionally accepting payload start and end markers.
• GET_XML_PAYLOAD — Builds an XML representation of a record (and its context) for a specified table using primary key name/type/character lists, returning the payload and context as CLOB values plus status outputs.
• TRACK_HA_RECORD — The core capture routine: given a table, primary key metadata, DML type, optional mobile-data flag, and optional parent payload ID, it records the change for HA propagation.
• TRACK_HA_ATTACHMENTS — Captures attachment-related changes as part of the HA tracking flow.
• GET_PK_COLUMN_NAME — Returns the primary key column name for a supplied object/table name.
• GET_HA_PROFILE_VALUE — A function returning a configuration value from the HA system profile option. This is the entry the user searched for (get_ha_profile_value); it governs whether HA tracking behavior is enabled and how it behaves, typically read at the start of a tracking session or before capture.
• GET_PREDICATE_CLAUSE — Constructs a SQL predicate clause from supplied columns and values, used internally to filter records for capture.
• GET_LISTFROM_STRING — Returns a CSM_VARCHAR_LIST constructed from a delimited string, supporting list-based parameter passing.

Tables Accessed

The package reads and writes a cluster of CSM/ASG and CSF tables via APPS synonyms. Capture and payload persistence center on CSM_HA_PAYLOAD_DATA (and its sequence CSM_HA_PAYLOAD_DATA_S), CSM_HA_ACTIVE_CONC_DATA, and CSM_HA_ACTIVE_WF_COMPONENTS, which hold active payload and workflow component state. Mapping tables CSM_HA_AUX_MAPPINGS and CSM_HA_RESP_MAPPINGS resolve auxiliary and responsibility-level configuration. CSM_DEFERRED_NFN_INFO and CSM_AUTO_SYNC_NFN support deferred notification and automatic synchronization. Resource/skill and availability data come from ASG_USER, ASG_USERS_INQINFO, ASG_DEFERRED_TRANINFO, ASG_PUB_ITEM, ASG_SYSTEM_DIRTY_QUEUE, CSF_ACCESS_HOURS_B, and CSF_REQUIRED_SKILLS_B.

Usage Notes

CSM_HA_EVENT_PKG is typically invoked by three other packages and by Field Service/CSM forms and concurrent programs rather than being called directly by end users. The standard pattern is BEGIN_HA_TRACKING, one or more TRACK_HA_RECORD and TRACK_HA_ATTACHMENTS calls as business changes occur, then END_HA_TRACKING, with SAVE_SEQUENCE persisting sequence data. GET_HA_PROFILE_VALUE is commonly called first to confirm HA tracking is enabled before any capture work is performed. Custom code extending HA behavior should follow the same begin/end bracketing and honor the AUTHID CURRENT_USER semantics to avoid hard-coding APPS. Because payloads rely on sequence tables and deferred queues, callers should treat the package as transactional with the surrounding DML.