Search Results insert_object_func

Overview

IGS_SC_DATA_SEC_APIS_PKG is the core data-security application programming interface for the Oracle Student System (Oracle iGS) in Oracle E-Business Suite 12.1.1 and 12.2.2. Created by Don Shellito in April 2003 and shipped under the $Header IGSSC02S.pls 120.3 line, the package encapsulates the insert and update operations that populate and maintain the Student System security data model. Its stated purpose is the processing and gathering of security definitions, exposing a stable, FND_API-style interface that shields callers from direct DML against the underlying security tables.

The package is classified as OTHER in ETRM and is owned by APPS, meaning all procedures execute under the APPS schema and depend on APPS synonyms for the iGS security tables. It exposes 43 documented procedures organized around four functional areas: grants, grant conditions, object metadata, and user/local role security. It is referenced by two other packages, indicating that it functions as a shared foundation layer rather than a top-level entry point.

Key Procedures and Functions

The API surface is dominated by paired INSERT and UPDATE procedures. Because every procedure follows the FND_API convention of an p_api_version input, an optional p_init_msg_list, and x_return_status/x_return_message outputs, each call is transactional and returns structured error information to the caller.

• Grant APIs — INSERT_GRANT, INSERT_GRANT_COND, UPDATE_GRANT, and UPDATE_GRANT_COND create and maintain grant records and their associated conditions. UPDATE_GRANT_COND was extended in July 2005 with an additional parameter to update the condition number, the only documented post-initial change history entry.
• Object metadata APIs — INSERT_OBJECT and UPDATE_OBJECT manage the security object registry; INSERT_OBJECT_GROUP and UPDATE_OBJECT_GROUP manage groupings of objects; INSERT_OBJECT_ATTR, INSERT_OBJECT_ATTR_METHOD, INSERT_OBJECT_FUNC and their UPDATE counterparts register object attributes, attribute methods, and object-level functions.
• User and role APIs — INSERT_USER_ATTR and UPDATE_USER_ATTR manage user security attributes; INSERT_LOCAL_ROLE, INSERT_LOCAL_USER_ROLE, UPDATE_LOCAL_ROLE, and UPDATE_LOCAL_USER_ROLE maintain local role definitions and their assignment to users.

The user-visible procedure INSERT_OBJECT_FUNC inserts a row into the object-function table, mapping a security function to a registered object and thereby making that function securable within the Student System data model.

Tables Accessed

The package reads and writes the following APPS-synonymed tables. Operationally the INSERT procedures write to the base tables (IGS_SC_GRANTS, IGS_SC_GRANT_CONDS, IGS_SC_OBJECTS, IGS_SC_OBJ_ATTRIBS, IGS_SC_OBJ_ATT_MTHS, IGS_SC_OBJ_FUNCTNS, IGS_SC_OBJ_GROUPS, IGS_SC_USR_ATTRIBS) and these base tables are kept in lockstep with their _S or related derivative tables (IGS_SC_GRANTS_S, IGS_SC_OBJ_ATTRIBS_S, IGS_SC_OBJ_ATT_VALS). FND_OBJECTS and FND_OBJECTS_S provide the EBS-wide object registry that iGS security objects reference, while WF_LOCAL_USER_ROLES supports the local role and user-role assignment APIs and FND_USER supplies the user identity source. No documented table is accessed outside the security model and role framework.

Usage Notes

This package is a programming interface, not a concurrent program or form-backed API. It is invoked in three typical ways: (1) from Oracle Forms and OAF pages within Oracle Student System that maintain security definitions, where the form calls the API instead of performing direct DML; (2) from the two referencing packages, which layer higher-level security workflows on top of these atomic operations; and (3) from custom PL/SQL that registers objects, grants, or local roles on behalf of an institution. Callers must supply a valid p_api_version, should honour p_init_msg_list and p_commit when chaining multiple calls, and must check x_return_status after every invocation. Because inserts target the base tables, any custom code that bypasses this package risks leaving the _S shadow tables inconsistent.