Search Results p_full_name

Overview

FUN_CONTACTUS_EMAIL is an Oracle Applications (APPS) PL/SQL package body that implements the server-side logic behind the "Contact Us" self-service feature in Oracle E-Business Suite. The package provides the integration point between the Contact Us BC4J (Business Components for Java) user interface and the Oracle Workflow notification engine. Its primary business purpose is to assemble the runtime attributes required to start a Workflow process item of type FUNCNCT and to dispatch an e-mail notification to a help desk analyst on behalf of a user who has submitted a Contact Us request.

The package header is versioned under the 120.1 release stream, with an originating header comment dated 26-May-2006, and the code was originally created on 22-Apr-2005. It is classified as an "OTHER" API in the ETRM registry, meaning it is not a formally published open interface or public API; it is an internal implementation package. It also does not define any dependency surface for other packages, as the metadata records zero packages referencing it.

Key Procedures and Functions

The ETRM metadata documents two procedures/functions within the package body:

• SEND_NOTIFICATION — Sets the Workflow item attributes and starts the FUNCNCT workflow process, whose sole activity is to send a notification. Based on the documented parameters, it accepts the Contact Us request identifier (used as the Workflow key), the role name of the person submitting the request, the destination e-mail address of the help desk analyst, the problem summary entered by the submitter, and alternative contact information for the submitter. Internally, the procedure declares a text offset and Workflow name/text array structures for attribute population, along with local variables for role name, role display name, display name, e-mail address, notification preference, language, and territory. It writes progress information through the FND_LOG logging facility.
• GET_USER_INFO — A helper procedure used to resolve user-related attributes required for the notification, such as the user's display name, e-mail address, notification preference, and language/territory settings. It supports SEND_NOTIFICATION by populating the contextual values that the Workflow notification template consumes.

No public parameter lists beyond those shown in the source excerpt are asserted here; the descriptions above are limited to documented behavior.

Tables Accessed

The package accesses two tables via APPS synonyms:

• FND_USER — Read to retrieve the submitter's identity attributes, including display name, e-mail address, notification preference, language, and territory. These values drive the sender/recipient context of the Workflow notification and the localization of the message.
• HZ_PARTIES — Read to resolve party-level information (for example, the person's primary name or e-mail details) where the Contact Us request references a trading community party record rather than, or in addition to, an FND user.

No insert, update, or delete operations against application tables are documented; the package's persistent side effect is the creation and execution of the Workflow item and its notification.

Usage Notes

FUN_CONTACTUS_EMAIL is typically invoked from the Contact Us BC4J layer rather than from a concurrent program or an Oracle Forms client. When a user submits a Contact Us request from the self-service interface, the middle tier calls SEND_NOTIFICATION with the request identifier and submission context, which in turn starts the FUNCNCT Workflow process and generates the analyst notification. Because the package is not a published API and exposes no documented dependencies to other packages, customizations should avoid calling it directly; the supported extension point is the FUNCNCT Workflow definition and its notification template. In both EBS 12.1.1 and 12.2.2, the package remains an internal component of the Contact Us flow, and the same source header (120.1) applies across both releases.