Search Results fun_contactus_email




Overview
Explore in AI Chat

Overview

FUN_CONTACTUS_EMAIL is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is classified under the ETRM "OTHER" API category, indicating that it is an internal utility package rather than a formally published open interface or public API. Its business purpose is to support the "Contact Us" / web inquiry notification flow, allowing the application to notify a designated recipient (for example, a system administrator or support mailbox) when a user submits a problem or feedback through a self-service screen. The package provides two documented entry points: one that dispatches the notification e-mail, and one that resolves basic user information used to populate or enrich that notification. The header comment references a 2005 source revision, confirming that the package is a long-standing, stable component of the Oracle self-service infrastructure.

Key Procedures and Functions

  • SEND_NOTIFICATION — The principal worker procedure. Its documented parameters include a request identifier, a source ("from") role, a destination e-mail address, a problem summary, and an alternative contact value. It is responsible for composing and dispatching the "Contact Us" notification to the specified recipient, carrying the problem description and any alternate contact details supplied by the requesting user.
  • GET_USER_INFO — A lookup procedure that accepts a user identifier and returns the corresponding full name, e-mail address, and a return status indicator. This is the procedure most commonly associated with the "get_user_info" search term. It resolves an FND_USER identifier into the human-readable identity and mail address needed by the notification logic, and reports success or failure through its status output so the calling code can handle unresolvable or invalid users gracefully.

Both procedures are declared in the package specification. No additional public procedures or functions are documented in the ETRM metadata.

Tables Accessed

The package accesses two documented tables through APPS synonyms:

  • FND_USER — The Oracle Applications user repository. This is queried by GET_USER_INFO to translate a user identifier into the user's full name and e-mail address, and is the authoritative source for resolving the identity of the person referenced in the notification.
  • HZ_PARTIES — The Trading Community Architecture party table. It is referenced to obtain or cross-reference party-level contact information, which is the standard EBS source for person and organization contact details. Together with FND_USER, it supplies the address and identity data that populate the outbound notification.

No other tables are documented as referenced by this package, and it is not listed as referenced by any other package, indicating that its callers invoke it directly rather than through a wrapper.

Usage Notes

FUN_CONTACTUS_EMAIL is typically invoked from the Oracle Applications self-service framework in support of the "Contact Us" or feedback functionality, where a user-entered inquiry must be routed by e-mail to a responsible party. It is most often driven either by a form button or by a concurrent program or workflow activity that accepts the collected inquiry details and calls SEND_NOTIFICATION. Customizations that need to resolve a user identifier to a name and e-mail may call GET_USER_INFO directly, although because the package is classified as OTHER — not a published public API — such calls should be treated as internal and validated against the specific EBS patch level in use. Callers must supply a valid notification request identifier and destination address to SEND_NOTIFICATION, and must handle the return status value emitted by GET_USER_INFO to avoid failures when a user record is missing or incomplete. Organizations upgrading between 12.1.1 and 12.2.2 should confirm the signature remains unchanged, as the package has no documented dependents that would signal an interface change.