Search Results validate_logged_user_rights




Overview
Explore in AI Chat

Overview

The IGW_PROP_PERSON_BIOSKETCH_PVT package body is a private (PVT) PL/SQL API within the Oracle E-Business Suite Grants Management (IGW) application. It supports the maintenance of person biosketch records associated with proposals. In the research administration domain, a biosketch is a structured summary of an investigator's qualifications, publications, and professional history, typically required as part of a grant or proposal submission. This package provides the internal processing logic that updates biosketch rows for persons attached to a specific proposal.

As a private package, IGW_PROP_PERSON_BIOSKETCH_PVT is not intended for direct invocation by external consumers. Rather, it is called by the corresponding public package IGW_PROP_PERSON_BIOSKETCH_PUB, which acts as the externally supported entry point. The private layer encapsulates the implementation details of record locking, validation, error handling, and the actual data manipulation against the underlying table. This separation of public and private layers follows the standard Oracle Application Object Library (AOL) API architecture, allowing Oracle to revise internal logic without breaking the published contract exposed to integrators. The package header carries a version date of November 2002, indicating it belongs to the earlier IGW code baseline that has been carried forward into the 12.1.1 and 12.2.2 releases essentially unchanged.

Key Procedures and Functions

The ETRM metadata documents four procedures within this package body:

  • UPDATE_PROP_PERSON_BIOSKETCH — The principal procedure of the package. It performs the update of a person biosketch record. Internally it optionally creates a savepoint when the commit flag is asserted, initializes the message list, sets the return status to success, invokes locking validation, and then delegates the physical row update to the table handler package IGW_PROP_PERSON_BIOSKETCH_TBH when the caller is not running in validate-only mode. Standard AOL API parameters such as p_init_msg_list, p_commit, p_validate_only, and p_record_version_number govern its transactional and validation behavior.
  • CHECK_LOCK — A validation helper that verifies the caller holds a valid lock on the target row by comparing the supplied rowid and record version number. This enforces optimistic concurrency control; if another session has modified the record, the version number check fails and the update is rejected.
  • CHECK_ERRORS — A utility that inspects the accumulated message stack and the return status after each internal step. It is called after CHECK_LOCK and after other validation or DML steps so that processing can be short-circuited and errors propagated when any check reports a failure.
  • VALIDATE_LOGGED_USER_RIGHTS — A procedure originally intended to confirm that the currently logged-in application user holds the privileges required to modify the specified proposal's biosketch data. Within UPDATE_PROP_PERSON_BIOSKETCH the call to this procedure is present but commented out in the shipped source, meaning the rights check is effectively bypassed in the delivered code path while remaining available for use.

Tables Accessed

The package operates against a single documented table, IGW_PROP_PERSON_BIOSKETCH, accessed through the APPS synonym. This table stores the biosketch rows belonging to persons associated with a proposal. The read/write activity is largely indirect: UPDATE_PROP_PERSON_BIOSKETCH does not issue the SQL itself but calls IGW_PROP_PERSON_BIOSKETCH_TBH.UPDATE_ROW to persist changes to columns such as P_PROPOSAL_ID, P_PERSON_BIOSKETCH_ID, P_SHOW_FLAG, and P_LINE_SEQUENCE. CHECK_LOCK resolves the row through the rowid passed by the caller, which ultimately points at a record in this same table. No other tables are documented as being referenced.

Usage Notes

This package is invoked in the context of user-driven maintenance of proposal biosketch data, most commonly from the Grants Management forms that present person biosketch information on a proposal. The form acquires the row lock, obtains the rowid and record version number, and then calls the public wrapper, which in turn calls UPDATE_PROP_PERSON_BIOSKETCH here. It may also be reached from concurrent programs or custom extensions that perform bulk or programmatic maintenance of biosketch records, provided those callers go through the published API.

Because the private package is not a supported integration surface, direct calls to it from custom code are discouraged. Callers should supply the correct rowid and a current record version number, and should honour the p_init_msg_list, p_commit, and p_validate_only conventions of the AOL API framework so that errors are surfaced through FND_MSG_PUB and the transaction is managed correctly. The bypass of VALIDATE_LOGGED_USER_RIGHTS means that authorization enforcement depends on the invoking form or the public API layer rather than on this package body itself.