Search Results g_wf_name_token

Overview

OKC_TASK_ALERT_ESCL_PVT is a private PL/SQL package in the Oracle E-Business Suite Contracts (OKC) module. It provides the internal engine that drives the task notification and escalation lifecycle for Oracle Contracts deliverables and task-based workflow. The package is classified as PVT, meaning it is not a public API; it is designed to be called by a corresponding public wrapper (OKC_TASK_ALERT_ESCL, or the workflow/concurrent-program layer) rather than directly by customer code.

The package's responsibility is to evaluate contract tasks against their planned and due dates, generate alerts to task owners before a due date is breached, and raise progressively higher escalation levels when a task remains incomplete. It also triggers the action assembler when a scheduled planned date is reached. This supports the SLA-style monitoring of contract deliverables, ensuring that contractual obligations tied to tasks are not silently missed.

The header declares the package name constant G_PKG_NAME as 'OKC_TASK_ALERT_ESCALATE', the application name from OKC_API.G_APP_NAME, standard error-handling tokens (G_UNEXPECTED_ERROR, G_SQLERRM_TOKEN, G_SQLCODE_TOKEN), and the private-level suffix G_LEVEL ('_PVT'). It also defines workflow-related tokens and an API version of 1.0.

Key Procedures and Functions

The documented interface contains four procedures:

• TASK_ALERT — Sends notifications to all task owners before the due date. This is the pre-emptive reminder stage, invoked ahead of a task's planned/due date so owners can act before the deadline is missed.
• TASK_ESCALATION1 — Performs the level-1 escalation of a task. Invoked when a task remains incomplete past its due threshold, notifying the first-level escalation recipient.
• TASK_ESCALATION2 — Performs the level-2 escalation of a task, the procedure referenced by the search term task_escalation2. It represents the next tier of the escalation ladder, executed when a task continues to be unresolved after level-1 escalation.
• OKC_PDATE_REACH_PVT — Triggers the action assembler when the scheduled planned date is reached, driving downstream contract actions tied to the planned date.

Each procedure exposes standard concurrent-program style OUT parameters (errbuf, retcode) plus the API parameters p_api_version, p_init_msg_list, p_wf_name, and p_wf_process. The workflow name/process parameters allow the caller to associate the alert or escalation with a specific Oracle Workflow process, and the package validates this through G_WORKFLOW_ACTIVE, G_WF_NAME_TOKEN, and G_WF_P_NAME_TOKEN, raising G_PROCESS_NOTFOUND if the process cannot be located.

Tables Accessed

• JTF_TASKS_B, JTF_TASKS_TL — the core task and task translation tables holding the deliverables and their descriptions that are being monitored.
• JTF_TASK_STATUSES_TL, JTF_TASK_TYPES_TL — provide status and type translation values used to determine whether a task is open, complete, or overdue.
• FND_USER — resolves task owners and escalation recipients for notification addressing.
• OKC_RESOLVED_TIMEVALUES — supplies resolved time/date values used for due-date and planned-date calculations.
• OKC_RULES_B — holds the rule definitions that govern alerting/escalation behaviour.
• OKC_WF_NOTIFY_S1 — the workflow notification sequence supporting the alert/escalation messages.
• DUAL — used for simple single-row evaluations.

Usage Notes

Because OKC_TASK_ALERT_ESCL_PVT is a private package, it is not intended for direct invocation from custom code. It is typically scheduled as a concurrent program or called from the Contracts workflow background engine, which runs periodically to scan tasks, issue pre-due alerts via TASK_ALERT, and advance escalation levels via TASK_ESCALATION1 and TASK_ESCALATION2. The task_escalation2 procedure is therefore reached through workflow configuration rather than an end-user screen. ETRM metadata records the package as referenced by zero other packages, confirming its role as a workflow-invoked leaf routine. Customisations should target the public API wrapper rather than this private package to remain upgrade-safe.