Results for “ego_item_revisions”

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

Overview

ENG_WORKFLOW_NTF_UTIL is a utility package body owned by APPS within the Oracle E-Business Suite engineering workflow framework. Its primary responsibility is to construct and deliver Workflow notifications generated by the Oracle Engineering (ENG) module, most notably for Engineering Change Order (ECO) processing. The package translates workflow notification identifiers into human-readable message content by resolving seeded workflow message names and retrieving the corresponding subject, text body, and HTML body attribute values from the Workflow message repository.

In practice, the package acts as the presentation bridge between the Oracle Workflow engine and the Engineering Change Management notification content. When an engineering change or a revision moves through its approval routing, the workflow engine raises events such as assignment, priority change, status change, reassignment, FYI notices, and approval status changes. ENG_WORKFLOW_NTF_UTIL maps each of these internal workflow message codes to the seeded message templates that carry the actual text presented to the recipient. This object is classified as a UTIL (utility) API, meaning it is not intended to be called directly by end-user code but instead supports higher-level engineering workflow processing.

Key Procedures and Functions

The ETRM metadata documents six callable units in this package:

• GETMESSAGETEXTBODY — Returns the plain-text body content associated with a given workflow notification message. It resolves the workflow message name to its corresponding text-body message attribute and retrieves the rendered value.
• GETMESSAGEHTMLBODY — Returns the HTML body content for a notification, allowing the workflow notification to render with HTML formatting in the notification worklist and e-mail delivery channels.
• GETRUNFUNCURL — Builds the Workflow run-function URL used to direct a notification recipient to the appropriate Engineering responsibility and form when responding to a notification.
• GETCHANGERUNFUNCURL — Constructs the run-function URL specific to an engineering change, supplying the navigation context required to open the change record directly from the notification.
• GETCHANGESUMMARYRUNFUNCURL — Produces the run-function URL for the engineering change summary view, used when a notification should land the user on a consolidated change summary rather than a single change.
• GETNTFRECIPIENT — Determines the intended recipient or recipients of a notification, supporting the routing logic that Workflow uses to address the message.

Tables Accessed

The package reads from several engineering and workflow tables through APPS synonyms:

• WF_NOTIFICATIONS — Queried to obtain the message name associated with a notification identifier, forming the entry point for message resolution.
• WF_MESSAGE_ATTRIBUTES — Holds the per-message subject, text-body, and HTML-body attribute values that this package retrieves.
• ENG_ENGINEERING_CHANGES — Provides engineering change data used when building change-specific run-function URLs and notification content.
• ENG_CHANGE_ORDER_TYPES and ENG_CHANGE_TYPE_APPLICATIONS — Supply change type configuration and the association between change types and applications, used to determine routing and recipient context.

Usage Notes

ENG_WORKFLOW_NTF_UTIL is invoked indirectly through the Oracle Engineering workflow processes rather than from a user-facing form or concurrent program directly. Notification activities defined in the Engineering Change Order workflow call these utilities to populate message subject and body at runtime, and to attach the correct run-function navigation links. The package header identifies the source revision as ENGUNTFB.pls, version 120.2, dated 2006, reflecting the long-standing stability of this utility within the EBS code line; it remains present in both 12.1.1 and 12.2.2 releases. Because it is a UTIL-class API, customizations and extensions should avoid modifying it directly; instead, integrators should rely on the seeded workflow message templates and, where necessary, call these utilities only for read-only purposes. One other package references this object, confirming it operates as a shared dependency of the engineering workflow notification stack.