Search Results igs_ss_pertyp_resp_groups_pk

Overview

The table IGS_SS_PERTYP_RESP_GROUPS_ALL is a data object within the Oracle E-Business Suite (EBS) Student System (IGS) module. Its primary role is to define and store the mapping between specific user responsibilities and person type codes, thereby establishing a security and access control mechanism based on a user's assigned responsibility and the type of person record they are interacting with. This table is designated as "All," indicating it is a multi-organization (Multi-Org) enabled table, storing data partitioned by the operating unit identifier (ORG_ID). It is critical to note that the provided ETRM metadata explicitly states the Student System module is marked as "Obsolete" and that this specific table is "Not implemented in this database," suggesting it may be a legacy or reference object from an earlier version that is not actively used in standard EBS 12.1.1 or 12.2.2 deployments.

Key Information Stored

The table's structure is defined by its composite primary key, which consists of three columns that together uniquely identify a record. The data stored is fundamentally a set of these key values, forming an association rule.

• ORG_ID: Stores the operating unit identifier, enabling Multi-Org security and data segregation.
• RESPONSIBILITY_ID: Stores the internal identifier for an EBS responsibility (from FND_RESPONSIBILITY). This links to the application menu and set of functions a user can access.
• PERSON_TYPE_CODE: Stores a code representing a classification or category of a person (e.g., STUDENT, INSTRUCTOR, APPLICANT) within the Student System's person model.

Each record signifies that the specified responsibility is authorized or configured to process or view data for the specified person type within the given operating unit.

Common Use Cases and Queries

Given its role in access control, this table would be queried to validate or determine the permissible person types for a user session. A common use case is during a student-centric transaction, where the system needs to verify if the current user's responsibility allows actions on the person type of the record in context. A typical validation query would join to the session's responsibility and organization context.

Sample Validation Query:
SELECT 'Y'
FROM igs_ss_pertyp_resp_groups_all
WHERE responsibility_id = :resp_id
AND person_type_code = :person_type
AND org_id = :org_id;

For reporting and administration, a query might list all responsibility-to-person-type mappings for an operating unit, potentially joining to FND_RESPONSIBILITY_TL for the responsibility name and a person type lookup table for the description.

Related Objects

Based on the provided relationship data, the table's primary purpose is defined by its primary key constraint (IGS_SS_PERTYP_RESP_GROUPS_PK). The columns forming this key imply foreign key relationships to other core EBS tables, though these are not explicitly named in the provided metadata.

• FND_RESPONSIBILITY: The RESPONSIBILITY_ID column would typically reference FND_RESPONSIBILITY.RESPONSIBILITY_ID to link to the EBS responsibility definition.
• HR_ORGANIZATION_UNITS / Financials Setup: The ORG_ID column references the operating unit, typically sourced from HR_ORGANIZATION_UNITS or related financials setup tables.
• IGS Person Type Lookup: The PERSON_TYPE_CODE would reference a person type code lookup within the IGS module, such as IGS_PE_PERSON_TYPES or a similar code table.

The table itself is likely referenced by application logic within the Student System's forms and APIs to enforce responsibility-based data access rules for different person classifications.