Results for “action_time”

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

Overview

WF_BES_SUBSCRIBER_PINGS is a transactional table owned by the APPLSYS schema within the FND – Application Object Library product of Oracle E-Business Suite. It operates as part of the Business Event System (BES), the infrastructure layer that governs event subscription, queue management, and message propagation across EBS modules and integrated systems. As the name indicates, the table records subscriber ping activity: it contains one row for each ping issued against each queue subscriber. Pings in the BES context are lightweight liveness or heartbeat signals used to verify that a subscriber endpoint is reachable and responsive before or during event delivery.

From a dimensional modeling perspective, the ETRM metadata classifies WF_BES_SUBSCRIBER_PINGS as a standalone object with a heuristic Data Vault classification of a hub. This designation is a modeling suggestion only: the table behaves much like a hub in that it captures discrete occurrences (ping events) uniquely identified by a compound business key, rather than describing the mutable attributes of an entity or resolving a many-to-many relationship between other hubs. Because the metadata documents no foreign keys other than SECURITY_GROUP_ID, the table is self-contained and does not participate as a link or satellite in the mined relationship graph.

Key Information Stored

The table comprises seven documented columns. The most significant of these define the identity, timing, and disposition of each ping:

• PING_NUMBER — The sequence or numeric identifier assigned to each ping. It forms the first component of the unique business key.
• QUEUE_NAME — The name of the BES queue against which the ping was performed. It is the second component of the unique key and identifies which queue the subscriber is bound to.
• SUBSCRIBER_NAME — The name of the queue subscriber that received the ping. Together with PING_NUMBER and QUEUE_NAME, it completes the unique index WF_BES_SUBSCRIBER_PINGS_U1, which serves as the business-key candidate.
• PING_TIME — The timestamp at which the ping was issued or recorded, enabling latency and liveness analysis over time.
• STATUS — The outcome or state of the ping, allowing administrators to distinguish successful pings from failures or pending conditions.
• ACTION_TIME — The timestamp of the action taken in response to the ping, supporting duration calculations between PING_TIME and ACTION_TIME.
• SECURITY_GROUP_ID — The security group under which the ping was executed. This is the only documented foreign key, referencing FND_SECURITY_GROUPS, and it enforces the multi-tenant data segregation model used throughout the APPLSYS schema.

The unique index WF_BES_SUBSCRIBER_PINGS_U1 (PING_NUMBER, QUEUE_NAME, SUBSCRIBER_NAME) is the documented business-key candidate. The metadata does not document an explicit surrogate primary key column beyond this composite uniqueness, though PING_NUMBER functions as a partial surrogate within a given queue and subscriber context.

Common Use Cases and Queries

Typical operational and diagnostic scenarios include verifying subscriber responsiveness, measuring ping-to-action latency, and auditing ping volume and failure rates by queue or subscriber. The following SQL patterns illustrate these uses.

Listing recent failed pings for a specific queue:

• SELECT ping_number, subscriber_name, ping_time, status FROM applsys.wf_bes_subscriber_pings WHERE queue_name = :queue AND status != 'SUCCESS' ORDER BY ping_time DESC;

Measuring response latency between ping and action:

• SELECT queue_name, subscriber_name, AVG(action_time - ping_time) avg_latency FROM applsys.wf_bes_subscriber_pings GROUP BY queue_name, subscriber_name;

Auditing ping activity within a security group and time window:

• SELECT status, COUNT(*) FROM applsys.wf_bes_subscriber_pings WHERE security_group_id = :sg AND ping_time >= :start_date GROUP BY status;

These queries support monitoring dashboards, subscriber health reports, and capacity planning for BES queue infrastructure.

Related Objects

The following objects are most significant in relation to WF_BES_SUBSCRIBER_PINGS:

• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID in the sole documented foreign key; joins on SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID. It governs the tenant boundary for ping records.
• WF_BES_SUBSCRIBERS (or the equivalent subscriber definition table) — Provides the subscriber metadata corresponding to SUBSCRIBER_NAME, allowing pings to be enriched with subscription details.
• WF_QUEUES — Supplies queue attributes matching QUEUE_NAME, linking ping activity to the physical or logical queue configuration.
• WF_BES_SUBSCRIBER_PING_HISTORY (if present in the deployment) — A companion table capturing historical ping denormalization or archival data.
• Business Event System PL/SQL APIs — Packages such as WF_EVENT and WF_BES that create, dispatch, and manage pings recorded in this table.

Because the metadata documents only one foreign key, these related objects should be treated as operational join candidates based on column-name alignment rather than constraint-enforced relationships. This table is central to BES health monitoring and should be included in any subscriber reliability analysis.