Search Results attrib_rec

Overview

IGS_SC_GEN_001 is a PL/SQL package owned by the APPS schema within the Oracle E-Business Suite environment. Its stated purpose, as recorded in the original source header dated April 8, 2003, is the "processing and gathering of the security process for Oracle Student System." It therefore functions as a foundational security engine for the Student System (IGS) product family, providing the runtime mechanism by which record-level and attribute-level access restrictions are enforced across student data.

The package is classified as API type OTHER in the ETRM documentation for release 12.1.1, indicating it is an internal engine rather than a public, supported extension API. It is referenced by 129 other packages, which underscores its role as a shared security service rather than a component invoked in isolation. It is not an interface table or a concurrent program; it is infrastructure code that other Student System modules call to establish session security context and to evaluate whether a given user may see, insert, update, or delete specific records.

Key Procedures and Functions

• SET_CTX — Establishes the security context for the current database session. This is the initialization entry point that prepares the session for subsequent security checks, typically by binding user-derived values to session state through DBMS_SESSION.
• UNSET_CTX — Clears or resets the security context previously established by SET_CTX, ensuring that context values do not leak beyond the scope of the calling operation.
• CHECK_INS_SECURITY — Evaluates insert security, determining whether the current user is permitted to create new records of the relevant Student System object.
• CHECK_SEL_UPD_DEL_SECURITY — A combined check covering select, update, and delete operations, used to determine whether the current user may read or modify existing records.
• CHECK_PERSON_SECURITY — Applies person-level security logic, restricting visibility of data associated with particular persons based on the user's grants and attributes.
• CHECK_USER_POLICY — The procedure most commonly searched for by name. It evaluates the applicable user policy to determine whether access should be granted for the operation under consideration. It serves as the decision routine that interprets the user's configured grants, conditions, and attributes against the object being accessed.

The package additionally declares a public record type, ATTRIB_REC, containing roughly twenty-five VARCHAR2(4000) fields such as ADVISOR, PERSON_ID, PROGRAM_TYPE, ORGANIZATIONAL_UNIT_CODE, and RESPONSIBLE_ORG_UNIT_CODE. This record type carries the attribute values evaluated during security checking.

Tables Accessed

The package reads and writes Student System security configuration tables through APPS synonyms:

• FND_USER, WF_LOCAL_USER_ROLES — to resolve the identity and role membership of the current user.
• FND_OBJECTS — to associate security definitions with registered application objects.
• IGS_SC_GRANTS, IGS_SC_GRANT_CONDS — to retrieve grants and their qualifying conditions.
• IGS_SC_OBJECTS, IGS_SC_OBJ_ATTRIBS, IGS_SC_OBJ_ATT_MTHS, IGS_SC_OBJ_ATT_VALS, IGS_SC_OBJ_GRANTS, IGS_SC_OBJ_GROUPS — to resolve the object hierarchy, its attributes, the methods used to derive attribute values, permissible values, and object-to-grant or object-to-group mappings.
• IGS_SC_USR_ATTRIBS, IGS_SC_USR_ATT_VALS — to obtain user attribute values compared against object attribute criteria.
• DBMS_SESSION, DBMS_SQL — used respectively to set and clear session context and to construct dynamic SQL where attribute methods require it.

Usage Notes

IGS_SC_GEN_001 is normally invoked indirectly. Student System forms and business logic call SET_CTX when a user session begins work with secured data, perform the CHECK_* routines as records are queried or modified, and call UNSET_CTX when the operation completes. Custom code extending Student System security should follow the same pattern and should not assume that context persists across unrelated transactions. Because the package is an internal engine referenced by 129 packages, direct modification is unsupported; 12.1.1 and 12.2.2 sites should treat it as read-only infrastructure and apply patches only through standard Oracle maintenance.