Results for “notification_date”

50+ results




Overview
Explore in AI Chat

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

Overview

PQH_FYI_NOTIFY is a transactional detail table owned by the HR schema and delivered as part of the Oracle E-Business Suite Public Sector HR (PQH) product family. Its documented description, "FYI Notification Details," identifies it as the repository that records informational ("for your information") notifications generated in association with public sector HR transactions. Rather than representing a workflow approval or an actionable routing step, this table captures the recipients and characteristics of courtesy notifications that accompany transaction processing, allowing the application to report on who was informed, when, and for which category or instance of activity.

In Oracle EBS 12.1.1 and 12.2.2 the table is registered as VALID and exposes fourteen documented columns with a single unique index, PQH_FYI_NOTIFY_PK, defined on FYI_NOTIFIED_ID. The ETRM relationship metadata classifies the object heuristically as satellite-leaning. Under a Data Vault modeling suggestion, this indicates the table behaves primarily as a descriptive satellite, holding context and attributes keyed to a parent business entity or category rather than acting as a central hub or a pure many-to-many link. The single documented foreign key to PQH_TRANSACTION_CATEGORIES reinforces that satellite role by anchoring notification records to a transaction category dimension.

Key Information Stored

The surrogate primary key is FYI_NOTIFIED_ID, defined through the unique index PQH_FYI_NOTIFY_PK. This column is the system-generated identifier for each notification detail row and should be treated as a technical key rather than a user-recognizable business identifier; the documented metadata does not expose a separate natural unique key.

  • FYI_NOTIFIED_ID — surrogate primary key uniquely identifying each notification record.
  • TRANSACTION_CATEGORY_ID — foreign key to PQH_TRANSACTION_CATEGORIES, indicating the notification category context.
  • TRANSACTION_ID — reference to the originating transaction for which the notification was produced.
  • NOTIFICATION_EVENT_CD — code identifying the event that triggered the notification.
  • NOTIFIED_TYPE_CD — code describing the type or classification of the notified party.
  • NOTIFIED_NAME — the name of the individual or recipient entity that was notified.
  • NOTIFICATION_DATE — the date on which the notification was issued.
  • STATUS — current state of the notification record.
  • OBJECT_VERSION_NUMBER — optimistic locking column supporting concurrent update control.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns capturing when, by whom, and through which login the row was last modified.
  • CREATED_BY, CREATION_DATE — standard EBS audit columns capturing initial row creation.

The audit and object-version columns conform to the standard EBS WHO-column convention and are essential for any change-tracking or data-extraction reporting.

Common Use Cases and Queries

Typical usage centers on auditing and reporting which parties were informed about public sector HR transaction activity. A common query joins the notification table to its category parent to resolve category context:

  • Notification audit by category: SELECT n.FYI_NOTIFIED_ID, n.NOTIFIED_NAME, n.NOTIFICATION_DATE, n.STATUS FROM HR.PQH_FYI_NOTIFY n, HR.PQH_TRANSACTION_CATEGORIES c WHERE n.TRANSACTION_CATEGORY_ID = c.TRANSACTION_CATEGORY_ID;
  • Volume analysis by event: aggregate counts grouped by NOTIFICATION_EVENT_CD and NOTIFIED_TYPE_CD to profile notification traffic over time.
  • Recipient tracing: filter on NOTIFIED_NAME or NOTIFIED_TYPE_CD to determine which individuals or roles received FYI notifications for a given TRANSACTION_ID.
  • Change tracking: use LAST_UPDATE_DATE and OBJECT_VERSION_NUMBER to identify recently modified notification records for incremental extracts.

Because the table carries a single documented foreign key, reporting should generally be driven through PQH_TRANSACTION_CATEGORIES and TRANSACTION_ID rather than through independent lookups.

Related Objects

The following objects are most significant to PQH_FYI_NOTIFY, based on the documented relationship data:

  • PQH_TRANSACTION_CATEGORIES — referenced through PQH_FYI_NOTIFY.TRANSACTION_CATEGORY_ID; the principal parent dimension for notification categories.
  • PQH_FYI_NOTIFY_PK — the unique index enforcing the primary key on FYI_NOTIFIED_ID.
  • HR schema transaction tables — related via TRANSACTION_ID, providing the originating transaction context.
  • PQH public sector HR concurrent programs and notification APIs — the processes that insert notification detail rows during transaction handling.
  • Standard EBS audit reporting views — consumers of the WHO columns for change history.

Together these objects support tracing a notification from its category definition, through the originating transaction, to the named recipient and issue date.