Search Results update_object_func




Overview
Explore in AI Chat

Overview

IGS_SC_DATA_SEC_APIS_PKG is the primary application programming interface for the Oracle Student System (IGS) security data model. Authored by Don Shellito and first created on April 8, 2003, the package provides the procedural layer through which grants, object groups, object attributes, attribute methods, functions, and local roles are inserted and maintained within the Student System security framework. Its documented purpose is the processing and gathering of the security process for Oracle Student System.

Functionally, the package operates against the security schema that underpins row-level and function-level access control in IGS. Rather than permitting direct DML against the underlying security entities, callers invoke these APIs so that standard EBS API conventions — API version validation, message list initialization, optional commit control, and standardized return status reporting — are consistently applied. In EBS 12.1.1 and 12.2.2 this package remains classified as an OTHER API and is referenced by two additional packages, indicating that it sits beneath higher-level security administration logic rather than being an entry point itself.

Key Procedures and Functions

The 43 documented procedures fall into two logical families: insert routines and update routines. The insert family includes INSERT_GRANT, INSERT_GRANT_COND, INSERT_OBJECT_GROUP, INSERT_OBJECT_ATTR, INSERT_OBJECT_ATTR_METHOD, INSERT_OBJECT_FUNC, INSERT_OBJECT, INSERT_USER_ATTR, INSERT_LOCAL_ROLE, and INSERT_LOCAL_USER_ROLE. The update family mirrors these entities: UPDATE_GRANT, UPDATE_GRANT_COND, UPDATE_OBJECT_GROUP, UPDATE_OBJECT_ATTR_METHOD, UPDATE_OBJECT_FUNC, UPDATE_OBJECT_ATTR, UPDATE_USER_ATTR, UPDATE_LOCAL_ROLE, and UPDATE_LOCAL_USER_ROLE.

The procedure most relevant to the search term is INSERT_OBJECT_ATTR_METHOD, which creates a record in the object attribute method entity. This links a security object attribute to the method by which its value is derived or evaluated during security checking. INSERT_OBJECT_ATTR and UPDATE_OBJECT_ATTR manage the attribute definitions themselves, while INSERT_OBJECT_FUNC and UPDATE_OBJECT_FUNC associate functions with security objects. INSERT_GRANT and UPDATE_GRANT establish and modify the privileges (select, insert, update, delete flags) granted to a user group over an object group.

The public procedures follow the documented signature pattern: p_api_version, p_init_msg_list defaulting to FND_API.G_FALSE, p_commit defaulting to FND_API.G_FALSE, entity-specific IN or IN OUT parameters, and OUT NOCOPY x_return_status and x_return_message. The July 18, 2005 revision by prbhardw added a parameter to UPDATE_GRANT_COND to support updating the condition number.

Tables Accessed

The package reads and writes the core IGS security tables through APPS synonyms. IGS_SC_GRANTS and its shadow table IGS_SC_GRANTS_S hold grant definitions, with IGS_SC_GRANT_CONDS storing conditional qualifiers. IGS_SC_OBJECTS, IGS_SC_OBJ_GROUPS, IGS_SC_OBJ_FUNCTNS, IGS_SC_OBJ_ATTRIBS, and IGS_SC_OBJ_ATT_VALS define the secured object model, including attribute values. IGS_SC_OBJ_ATT_MTHS holds the attribute method definitions manipulated by INSERT_OBJECT_ATTR_METHOD. IGS_SC_USR_ATTRIBS stores user attribute definitions. WF_LOCAL_USER_ROLES supports the local role and local user role procedures, and FND_OBJECTS, FND_OBJECTS_S, and FND_USER provide the Oracle Applications foundation object and user references that IGS security extends.

Usage Notes

These APIs are not intended for direct end-user invocation. They are called by the Student System security administration forms, by concurrent programs that synchronize or seed security metadata, and by the two dependent packages documented in the ETRM registry. Custom code should invoke them only with a valid p_api_version, should inspect x_return_status for FND_API.G_RET_STS_SUCCESS or G_RET_STS_ERROR, and should read x_return_message for diagnostics. Because p_commit defaults to FND_API.G_FALSE, transaction control remains with the caller, permitting multiple security entities to be committed atomically. The package header carries no 12.2-specific changes; behavior is consistent across 12.1.1 and 12.2.2.