Results for “source_message_code”

2 results




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

Overview

The XNP_TIMER_PUBLISHERS table resides in the XNP schema, which supports the Oracle E-Business Suite Number Portability module. It stores timer definitions associated with messages processed by the number portability infrastructure. In the context of XNP, timers govern the scheduled publication and expiration of messages, ensuring that message-driven workflows execute within expected service-level windows.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as a link. This classification reflects the presence of foreign keys referencing XNP_MSG_TYPES_B through two distinct columns — TIMER_MESSAGE_CODE and SOURCE_MESSAGE_CODE — indicating the table associates pairs of message types in a timer-driven relationship. The link interpretation is a modeling suggestion only; the physical implementation is a standard EBS transactional table with audit and multi-tenancy columns.

Key Information Stored

The table comprises ten documented columns. The most significant are:

Two unique indexes serve as business-key candidates: XNP_TIMER_PUBLISHERS_U1 (TIMER_PUBLISHER_ID, ZD_EDITION_NAME) and XNP_TIMER_PUBLISHERS_U2 (SOURCE_MESSAGE_CODE, TIMER_MESSAGE_CODE, ZD_EDITION_NAME). The latter enforces uniqueness of a source/timer message pair per edition, confirming the link semantics of the table.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios center on determining which source messages publish which timer messages, and on auditing timer configuration by edition.

  • Retrieve timer definitions for a specific message type:
    SELECT tp.timer_publisher_id, tp.timer_message_code, tp.source_message_code
    FROM   xnp.xnp_timer_publishers tp
    WHERE  tp.timer_message_code = :message_code;
  • Join to message types for descriptive reporting:
    SELECT mt_b.message_name, tp.source_message_code, tp.timer_message_code
    FROM   xnp.xnp_timer_publishers tp,
           xnp.xnp_msg_types_b mt_b
    WHERE  tp.source_message_code = mt_b.message_code;
  • Audit recent configuration changes using the standard audit columns:
    SELECT timer_publisher_id, last_updated_by, last_update_date
    FROM   xnp.xnp_timer_publishers
    WHERE  last_update_date > SYSDATE - 30;

Because ZD_EDITION_NAME participates in both unique indexes, queries in a 12.2.x environment should filter by the appropriate edition when comparing configurations across patch cycles.

Related Objects

The table participates in the following documented relationships:

  • XNP_MSG_TYPES_B — Referenced twice: XNP_TIMER_PUBLISHERS.TIMER_MESSAGE_CODE and XNP_TIMER_PUBLISHERS.SOURCE_MESSAGE_CODE both resolve to this message type base table.
  • FND_SECURITY_GROUPS — Referenced by XNP_TIMER_PUBLISHERS.SECURITY_GROUP_ID, governing row-level security.
  • XNP_TIMER_PUBLISHERS_PK — The primary key constraint on TIMER_PUBLISHER_ID.
  • XNP_TIMER_PUBLISHERS_U1 and XNP_TIMER_PUBLISHERS_U2 — Unique indexes supporting lookup by publisher identifier and by source/timer message pairing respectively.

These relationships position XNP_TIMER_PUBLISHERS as a configuration link between message types, with security scope inherited from the standard EBS security group infrastructure.