Search Results ntf_error_act

Overview

APPS.AHL_ROUTE_APPROVAL_PVT is a private PL/SQL package within the Oracle E-Business Suite Application Object Library / Oracle Flow Manufacturing and Product Development (AHL) schema. It implements the internal logic that supports the Oracle Approval Management routing workflow for AHL (Product Development / Product Lifecycle Management) documents. The package provides the business logic invoked behind the scenes by Oracle Workflow and Oracle ASO approval mechanisms to generate FYI notification content, drive status transitions, and manage the activity details associated with approval routing. Because it is classified as a private (PVT) package, it is not intended as a public extension API and is normally invoked only by other Oracle-owned components. The package is declared with AUTHID CURRENT_USER, meaning that it executes with the privileges of the invoking user rather than the definer, and its original header dates to 2002 under the naming convention AHLVRWKS.pls.

Key Procedures and Functions

The documented ETRM metadata lists 10 procedures and functions exposed by this package. The core notification-related procedures include:

• SET_ACTIVITY_DETAILS — Accepts an item type, item key, activity ID, and function mode, and returns a result. This is the workflow interface routine that lets the approval process pass activity context into the routing logic.
• NTF_FORWARD_FYI — Generates the FYI notification document emitted when a routing item is forwarded to another approver.
• NTF_APPROVED_FYI — Generates the FYI notification document for the approved case.
• NTF_FINAL_APPROVAL_FYI — Generates the FYI document produced at final approval, used for display in messages in either text or HTML format. Documented history attributes it to Oracle ASO Approval (created by Rajanath Tadikonda, May 2002).
• NTF_REJECTED_FYI — Generates the FYI notification document for the rejected case, also used by Oracle ASO Approval.
• NTF_ERROR_ACT — This is the procedure most closely associated with the user search term "ntf_error_act." It handles the error activity notification path within the approval routing flow, producing the notification content surfaced when a routing activity encounters an error condition.
• NTF_APPROVAL — Produces the primary approval notification requesting action from the approver.
• NTF_APPROVAL_REMINDER — Produces the reminder notification re-sent to an approver who has not yet responded.
• UPDATE_STATUS — Advances the routing/approval status of the associated AHL route record.
• REVERT_STATUS — Rolls the routing/approval status back to a prior value, typically on rejection or cancellation.

All of the notification routines follow a shared design: they accept a document identifier (the item key) plus a display type of either 'text/plain' or 'text/html', and return the composed document buffer and its reported type.

Tables Accessed

The only table documented as referenced through APPS synonyms is AHL_ROUTES_B, the base table holding routing definitions. The package reads routing header information from this table to resolve the item key context and to determine the current routing state, and the UPDATE_STATUS and REVERT_STATUS procedures write back the approval status to the corresponding routing row. The notification procedures use the routing record to populate the FYI message content. No other base tables are documented as being touched directly by this package; supporting data such as notification definitions may be accessed indirectly through Oracle Workflow Y.

Usage Notes

APPS.AHL_ROUTE_APPROVAL_PVT is an internal implementation package and is referenced by zero other packages in the documented call graph. It is ordinarily invoked indirectly through Oracle Workflow notification activities configured for the AHL approval routing item type, and through the Oracle ASO approval integration noted in the procedure header comments. Custom code, Oracle Forms, or concurrent programs that need to force a routing status change or regenerate approval notifications should not call this private package directly. Instead, supported public APIs and Workflow activity definitions should be used, because the PVT classification signals that the signature and behavior are subject to change without notice between 12.1.1 and 12.2.2 releases.