Search Results check_if_user_has_seeded_role

Overview

IGW_PROP_USERS_PVT is a private PL/SQL package body in the APPS schema that governs the association between Oracle E-Business Suite users and proposals managed within the Oracle Grants/Projects proposal subsystem (IGW). Its principal business function is to maintain the IGW_PROP_USERS records that identify which application users are attached to a given proposal, together with the active date range for that association. Because the package is classified as PVT (private), it is not intended as a public, published interface; it is called internally by the IGW proposal APIs and related components that manage proposal team membership.

In the context of the user's search term "check_errors," the package contains a documented procedure named CHECK_ERRORS. This procedure exists to standardize error handling across the package's create, update, and delete operations, converting stored message-list entries into the return status, message count, and message data outputs expected by the Oracle Application Object Library (AOL) API conventions.

Key Procedures and Functions

• CREATE_PROP_USER — Inserts a new proposal-to-user assignment into IGW_PROP_USERS. Following the standard AOL API pattern, it accepts initialization and commit flags, performs optional validation-only processing, resolves the proposal identifier and user identifier when either is not supplied, and returns the new row identifier along with the standard return status, message count, and message data outputs.
• UPDATE_PROP_USER — Modifies an existing proposal-user assignment, typically the active start and end dates or the associated user attributes for an existing row in IGW_PROP_USERS.
• DELETE_PROP_USER — Removes a user's association from a proposal, including any related role assignments held in IGW_PROP_USER_ROLES.
• CHECK_IF_USER_HAS_SEEDED_ROLE — Determines whether a given user holds a seeded (system-defined) role for a proposal. This supports business rules that restrict removal or modification of users who occupy predefined proposal roles.
• CHECK_LOCK_GET_COLS — Retrieves and locks the current column values of a proposal-user row, supporting optimistic concurrency control so that concurrent updates do not silently overwrite one another.
• CHECK_ERRORS — Consolidates and evaluates the message stack populated by the other procedures in this package. It resolves the outstanding messages into the x_return_status, x_msg_count, and x_msg_data output parameters so that the calling program can determine success or failure and present meaningful diagnostics to the end user.

Tables Accessed

• IGW_PROP_USERS — The primary table maintained by this package. It stores the mapping of users to proposals along with active date ranges; it is inserted into by CREATE_PROP_USER, modified by UPDATE_PROP_USER, and purged by DELETE_PROP_USER.
• IGW_PROP_USER_ROLES — Stores the roles assigned to users within a proposal. It is referenced when validating role membership and when cleaning up role assignments during user deletion.
• IGW_ROLES — The role definition table, consulted to determine whether a role is seeded and therefore subject to restricted handling by CHECK_IF_USER_HAS_SEEDED_ROLE.

Usage Notes

IGW_PROP_USERS_PVT is invoked internally rather than from the user interface directly. The documented ETRM metadata records zero dependent packages, meaning no other packaged API in the schema references it, which is consistent with a private helper module consumed by the IGW proposal forms and their supporting libraries. Typical callers are the proposal definition and proposal team maintenance screens, which invoke CREATE_PROP_USER, UPDATE_PROP_USER, and DELETE_PROP_USER as users assign or remove personnel from a proposal. The commit and initialize-message-list flags follow FND_API conventions, so callers must inspect x_return_status and, when x_msg_count exceeds one, call FND_MSG_PUB.GET repeatedly to retrieve the full error text. Developers extending proposal-user functionality should preserve this error-handling contract and should not call CHECK_ERRORS outside the package, since it operates on the shared message stack rather than on parameters passed by the caller. The package is present in both EBS 12.1.1 and 12.2.2, with the file header indicating a base version predating the 12.2 online patching model, so customization should be performed through supported extension mechanisms rather than direct edits.