Search Results l_message

Overview

APPS.CSF_ALERTS_PUB is the public package body that implements the wireless alert engine for Oracle E-Business Suite Field Service and Task Manager. Its principal entry point, checkForAlerts, is a Workflow subscription callback that evaluates task assignments against business conditions and dispatches alert notifications to field personnel. ETRM classifies the package as a PUB API, indicating that its procedures are intended for invocation from Workflow event subscriptions, forms, and custom code rather than internal-only use.

The header comment enumerates the filtration logic applied before an alert is generated: an assignment must carry an attached task with schedule start and end dates; the scheduled start date must be greater than SYSDATE; the task must be of type 'Dispatch' with the schedulable flag set to 'Y' for Field Service tasks; task priority is checked against a profile value; and the assignment status must match the 'CSF: Default Assigned task status' profile setting at the application level.

Key Procedures and Functions

The package exposes 22 documented procedures and functions, spanning alert generation, evaluation, and message composition:

• CHECKFORALERTS — Main entry point. Accepts a subscription GUID and a WF_EVENT_T record, performs the filtration described above, and routes processing based on event type.
• CHECKALERTSENABLED — Determines whether alerts are active for the current context before further processing occurs.
• CHECKEVENT and CHECK_AGAIN — Evaluate event characteristics and re-evaluation conditions.
• CHECK_AUTO_REJECT — Handles automatic rejection scenarios within the assignment lifecycle.
• ACCEPT_ASSGN and CANCEL_ASSGN — Manage assignment acceptance and cancellation actions triggered by alert responses.
• SENDNOTIFICATION and GETSENDDATE — Compose and time the delivery of notifications, using a computed send date derived from shift start and the configured minutes-before offset.
• GETREMINDERMESSAGE, GETDELETEMESSAGE, GETRESCHEDULEMESSAGE, GETASSIGNEDMESSAGE — Retrieve the message text appropriate to each alert category.
• CATEGORY_TYPE and GETITEMKEY — Derive the alert category and the Workflow item key.
• GETUSERID and GETUSERNAME — Resolve the recipient identity for the notification.
• GETCONTACTDETAIL and GETTASKDETAILS — Fetch contact information and task attributes used to populate message content.
• GETCLIENTTIME — Returns client-local time, supporting time-zone-aware scheduling of alerts.

Tables Accessed

The package operates against Task Manager, Service, and Trading Community tables joined through APPS synonyms:

• JTF_TASK_ASSIGNMENTS, JTF_TASKS_B, JTF_TASK_TYPES_B, JTF_TASK_STATUSES_B, JTF_TASK_AUDITS_B — Source the assignment, task, type, status, and audit data that drive alert evaluation and the assignment status checks.
• JTF_RS_RESOURCE_EXTNS — Provides resource attributes used to resolve the assigned field service representative.
• CS_INCIDENTS_ALL, CS_INCIDENTS_ALL_B, CS_INCIDENTS_ALL_TL, CS_CUSTOMER_PRODUCTS_ALL — Supply service request and installed-base context referenced by contact and task detail routines.
• HZ_PARTIES, HZ_CONTACT_POINTS, HZ_PARTY_SITES, HZ_RELATIONSHIPS — Resolve customer, contact, and site information for notification addressing.
• WF_EVENT_T — The Workflow event structure manipulated by checkForAlerts as an IN OUT NOCOPY parameter.

Usage Notes

CSF_ALERTS_PUB is invoked primarily through Oracle Workflow event subscriptions. When a task assignment event fires, Workflow calls checkForAlerts, passing the subscription GUID and event payload; the function returns a status code indicating raised, not-raised, or error conditions. The package is referenced by one other package within the ETRM inventory, and its PUB classification permits direct calls from customer extensions.

Typical deployment scenarios include Field Service dispatch workflows that notify technicians of new, rescheduled, or cancelled assignments, and reminder alerts issued a configurable number of minutes before shift start. Because eligibility depends on profile options such as the CSF default assigned task status and priority thresholds, administrators should verify profile configuration at the application level before enabling subscriptions. Custom integrations should treat the documented signatures as stable but avoid bypassing the internal filtration performed by checkForAlerts, since downstream message routines assume those checks have already been applied.