Results for “from_user”

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

Overview

WF_COMMENTS is a core Oracle Workflow table owned by the APPLSYS schema and registered under the FND – Application Object Library product. Its documented purpose is to store comments associated with workflow notifications. When a notification is routed through the Oracle Workflow engine — whether as an approval request, an FYI message, or a response-required action — the free-text and system-generated commentary attached to that notification is persisted in this table. As such, WF_COMMENTS functions as the audit and conversational history layer for the notification subsystem.

From a Data Vault modeling perspective, the provided metadata classifies this object heuristically as standalone. This classification is significant: WF_COMMENTS contains no foreign keys pointing to other tables except for SECURITY_GROUP_ID, which references FND_SECURITY_GROUPS. Because it is not joined through a documented parent-child FK chain to a workflow hub, an analyst may reasonably model WF_COMMENTS as a satellite table hanging off a notification or role-based hub, or treat it as an independent event log. The absence of a documented FK to WF_NOTIFICATIONS suggests the relationship is enforced at the application layer rather than by database constraint, which is common in the APPLSYS schema to reduce overhead during high-volume workflow processing.

Key Information Stored

The table contains 13 documented physical columns in the ETRM 12.2.2 schema. The most operationally important include:

• NOTIFICATION_ID — the identifier of the parent notification. Although not enforced as a database FK, this is the principal business-key candidate and the column most frequently used in joins.
• FROM_ROLE, FROM_USER — the role and user who generated or initiated the comment.
• TO_ROLE, TO_USER — the recipient role and user for whom the comment is intended, enabling routing-aware reporting.
• PROXY_ROLE — the proxy role acting on behalf of the recipient, where applicable.
• COMMENT_DATE — the timestamp of the comment, essential for chronological ordering.
• ACTION, ACTION_TYPE — the workflow action and its category associated with the comment.
• USER_COMMENT — the free-text body of the comment, the core payload.
• LANGUAGE — the language code, supporting multilingual deployments.
• SECURITY_GROUP_ID — the only documented FK, referencing FND_SECURITY_GROUPS.
• SEQUENCE — ordering indicator for multiple comments on the same notification.

No standalone surrogate primary key index is documented in the metadata excerpt; NOTIFICATION_ID combined with SEQUENCE and COMMENT_DATE typically forms the practical business key.

Common Use Cases and Queries

WF_COMMENTS is frequently queried for approval audit trails, notification comment history, and workflow troubleshooting. A typical pattern retrieves all comments for a given notification:

• SELECT NOTIFICATION_ID, FROM_USER, TO_USER, COMMENT_DATE, USER_COMMENT FROM WF_COMMENTS WHERE NOTIFICATION_ID = :id ORDER BY SEQUENCE;
• Reporting on comments by responding user across a date range: filter on COMMENT_DATE and TO_USER.
• Auditing proxy responses: filter WHERE PROXY_ROLE IS NOT NULL.
• Multilingual analysis: group by LANGUAGE to assess localization coverage.
• Security-group scoped extracts: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS.

Related Objects

• FND_SECURITY_GROUPS — joined via WF_COMMENTS.SECURITY_GROUP_ID; the only documented FK relationship.
• WF_NOTIFICATIONS — logical parent via NOTIFICATION_ID, holding the notification header and status.
• WF_NOTIFICATION_ATTRIBUTES — stores additional notification metadata associated with the same notification.
• WF_ROLES — resolves FROM_ROLE, TO_ROLE, and PROXY_ROLE identifiers.
• WF_USERS — resolves FROM_USER and TO_USER identifiers.
• WF_ACTIVITIES — contextualizes ACTION and ACTION_TYPE values.
• WF_ITEM_ACTIVITY_STATUSES — links notification activity to process instances.