Results for “ntf_rejected_fyi”

50+ results




Overview
Explore in AI Chat

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

Overview

APPS.AHL_UC_WF_APPR_PVT is a private PL/SQL package in Oracle E-Business Suite that supports the Oracle Workflow approval infrastructure for the AHL (Product Development / Unit Configuration) module. Its name reflects its role: AHL denotes the Product Development application family, UC denotes Unit Configuration, WF denotes Workflow, APPR denotes Approval, and the PVT suffix classifies the package as private, meaning it is intended for internal use by the application rather than as a public API for customer extensions.

The package is declared with AUTHID CURRENT_USER and carries the header identifier AHLVUWFS.pls version 115.0, originally created on 2003/08/07. It encapsulates the activity and notification logic required to drive Unit Configuration approval workflows, including the generation of notification document bodies, approval and rejection notifications, reminders, error handling, and status transitions. It is closely associated with Oracle ASO (Order Capture) approval flows, as indicated in the procedure comments describing usage by Oracle ASO Approval.

Key Procedures and Functions

The package exposes ten documented procedures. Each serves a discrete role within the approval workflow lifecycle:

  • SET_ACTIVITY_DETAILS — Sets all item attribute details for the workflow activity, populating the runtime attributes required for subsequent notification and approval processing.
  • NTF_FORWARD_FYI — Generates the FYI (For Your Information) notification document for display in messages, producing either text or HTML output based on the requested display type.
  • NTF_APPROVED_FYI — Generates the FYI document notifying recipients that the item has been approved.
  • NTF_FINAL_APPROVAL_FYI — Generates the FYI document issued upon final approval, marking completion of the approval chain.
  • NTF_REJECTED_FYI — Generates the FYI document informing recipients that the item has been rejected.
  • NTF_APPROVAL — Produces the primary approval notification requesting action from the designated approver.
  • NTF_APPROVAL_REMINDER — Generates a reminder notification for approvers who have not yet responded to a pending approval.
  • NTF_ERROR_ACT — Handles notification of error conditions encountered during activity execution.
  • UPDATE_STATUS — Advances or sets the approval status of the underlying record as the workflow progresses.
  • REVERT_STATUS — Rolls back the approval status, typically used when a workflow is cancelled or an approval is withdrawn.

Tables Accessed

The package references AHL_UNIT_CONFIG_HEADERS through APPS synonyms. This table stores the header-level records for Unit Configuration definitions, which are the subject of the approval workflow. The package reads from this table to determine the item context for notifications and writes to it via UPDATE_STATUS and REVERT_STATUS to reflect the current approval state. Because the package is declared AUTHID CURRENT_USER, all table access resolves under the privileges of the invoking user, and reliance on APPS synonyms ensures consistent resolution within the EBS schema model.

Usage Notes

AHL_UC_WF_APPR_PVT is not intended for direct invocation by end users or customer code. It is invoked as part of Oracle Workflow activity function definitions configured against the Unit Configuration approval item type. The workflow engine calls SET_ACTIVITY_DETAILS at activity entry to populate attributes, then invokes the various NTF_* notification procedures to build message bodies rendered in the Workflow Notification System, and calls UPDATE_STATUS or REVERT_STATUS to persist approval outcomes.

Because the package is classified as private (PVT) and is referenced by zero other packages according to the documented metadata, it should be treated as internal implementation. Any customization should be performed through supported workflow configuration rather than by modifying this package, since its procedures and signatures are subject to change between releases. The FYI document procedures support both text/plain and text/html output, allowing notification content to render appropriately in both plain-text and HTML-capable notification clients.