Results for “c_usertype_registered”

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

Overview

IBY_EMAIL_REPORT is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, shipped as part of the Payments (IBY) module. Its declared purpose, reflected in the header comment of the package specification, is to generate and send an email report. The package is compiled with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the calling session rather than the definer, and it depends on APPS synonyms when resolving referenced objects.

The package is classified as an "OTHER" API in the ETRM repository, indicating that it is internal supporting infrastructure rather than a published, externally supported integration interface. The source header carries the identifier ibyvmals.pls 115.1, dated 2002, and the file designation noship, which is consistent with a long-lived utility routine that predates the 12.x release train and has remained stable. Its scope is narrow: it parses email recipient information supplied as a string, assembles a report, and dispatches that report by mail on behalf of the payments workflow. The package exposes two constants, C_USERTYPE_ADHOC ('ADHOC_USER') and C_USERTYPE_REGISTERED ('REGD_USER'), which distinguish ad hoc, unregistered recipients from registered users of the application when building the mailing list.

Key Procedures and Functions

The package declares three documented program units:

• POPULATE_USERINFO — Accepts a delimited string of email user information and decomposes it into the package's internal data structures. The specification defines a record type UserInfo_rec_type containing username, email address, and user type, together with a corresponding UserInfo_tbl_type collection, so this procedure is the mechanism by which the recipient list is parsed and staged for later mail generation.
• SEND_MAIL — Documented as the public API that "sends an email report." Its declared signature takes an item key and a user name as inputs and returns a standard EBS return status and message count through x_return_status and x_msg_count. The version history comments record version 1.0 as the initial, current, and previous version.
• SEND_REPORT — Documented as the third program unit; it is the report-generation counterpart to SEND_MAIL, assembling the report payload that is subsequently delivered to the recipients identified by POPULATE_USERINFO.

Tables Accessed

The package resolves three objects through APPS synonyms:

• IBY_PUSHMAIL_KEY_S — A sequence in the Payments module whose name associates it with push-mail (notification) key generation. The package draws values from this sequence to obtain unique keys for queued mail records, ensuring each outgoing email report is uniquely identifiable.
• DUAL — Used for single-row SELECT expressions, typically to evaluate sequence values or simple scalar computations without referencing an application table.
• PLITBLM — The standard EBS PL/SQL table-to-index conversion utility, invoked to translate collection structures into index-by tables suitable for SQL access. This is consistent with the package's use of the UserInfo_tbl_type collection to hold parsed recipient data.

Usage Notes

IBY_EMAIL_REPORT is not referenced by any other package in the ETRM repository, and it is not a published integration point. In practice it is invoked internally by Payments-related concurrent programs or workflow notification activities that must deliver report output by email. The typical invocation pattern is to call POPULATE_USERINFO to stage recipients, then SEND_REPORT or SEND_MAIL to produce and dispatch the message, checking x_return_status and inspecting x_msg_count with the standard FND_MSG_PUB message stack when a failure status is returned.

Because the package runs under AUTHID CURRENT_USER, custom code invoking it must have direct execution privileges and the necessary object grants on the underlying sequence and utility objects. Customers integrating with the search term "kawagishibridge ir email" should note that no such object or parameter exists in the documented metadata; the correct reference for email report delivery in this area is IBY_EMAIL_REPORT.SEND_MAIL. As with all OTHER-classified APIs, Oracle does not guarantee backward compatibility, so sites should avoid tight coupling to this package and prefer supported notification infrastructure where available.