Search Results privacy_level_id




Overview
Explore in AI Chat

Overview

The IGS_PE_PRIV_LEVEL table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically under the IGS (Oracle Student Management) product family. It functions as the central repository for defining and managing privacy levels associated with persons, such as students or staff. Its primary role is to enforce data privacy rules by linking a person to specific data groups and assigning a privacy level and action for each. This enables granular control over who can access or act upon certain categories of a person's information, supporting compliance with institutional and regulatory privacy policies.

Key Information Stored

The table's structure is designed to capture the essential components of a privacy rule. The key columns include:

  • PRIVACY_LEVEL_ID: The primary key (PK) uniquely identifying each privacy level record.
  • PERSON_ID: The foreign key (FK) linking to HZ_PARTIES, identifying the individual to whom the privacy level applies.
  • DATA_GROUP and DATA_GROUP_ID: These columns define the category of data (e.g., contact information, academic records) being protected. DATA_GROUP_ID is a foreign key to IGS_PE_DATA_GROUPS_ALL.
  • LVL: A numeric value representing the specific privacy level assigned to the data group for the person.
  • ACTION: Specifies the operation (e.g., 'HIDE', 'RESTRICT') that must be taken for data at this level.
  • WHOM: Indicates the type of person relationship (e.g., 'ALL', 'FACULTY') to which the privacy rule applies.
  • REF_NOTES_ID: A foreign key to IGS_GE_NOTE for storing explanatory notes or justifications.
  • START_DATE and END_DATE: Define the effective date range for the privacy rule.
  • Standard WHO columns (CREATED_BY, CREATION_DATE, etc.) for auditing.

Common Use Cases and Queries

A primary use case is auditing or reporting on the privacy settings for a specific individual or data group. For instance, to retrieve all active privacy rules for a person, a query would filter by PERSON_ID and a valid date range. Application logic uses this table to dynamically suppress or restrict data display based on the user's relationship to the person (WHOM) and the defined ACTION and LVL. A common reporting query pattern is: 

SELECT ppl.PRIVACY_LEVEL_ID, ppl.PERSON_ID, pp.DISPLAY_NAME,
       ppl.DATA_GROUP, ppl.LVL, ppl.ACTION, ppl.WHOM, ppl.START_DATE, ppl.END_DATE
FROM IGS.IGS_PE_PRIV_LEVEL ppl,
     HZ_PARTIES pp
WHERE ppl.PERSON_ID = pp.PARTY_ID
  AND pp.PARTY_NUMBER = :student_number
  AND SYSDATE BETWEEN NVL(ppl.START_DATE, SYSDATE) AND NVL(ppl.END_DATE, SYSDATE);
This joins to the HZ_PARTIES table to get the person's name and filters for currently effective rules.

Related Objects

The IGS_PE_PRIV_LEVEL table is integral to the privacy data model and has defined relationships with several other EBS objects:

  • Primary Key: IGS_PE_PRIV_LEVEL_PK on PRIVACY_LEVEL_ID.
  • Foreign Keys (Referenced by this table):
    • PERSON_ID references HZ_PARTIES (the universal party table in Trading Community Architecture).
    • DATA_GROUP_ID references IGS_PE_DATA_GROUPS_ALL (master list of privacy data groups).
    • REF_NOTES_ID references IGS_GE_NOTE (generic notes table).
  • Indexes: IGS_PE_PRIV_LEVEL_U1 (unique on PRIVACY_LEVEL_ID) and IGS_PE_PRIV_LEVEL_N1 (non-unique on PERSON_ID) for performance.
The table is referenced by the APPS synonym IGS_PE_PRIV_LEVEL, which is the standard access point for application code.