Results for “igs_ss_pertyp_resp_groups_all”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_SS_PERTYP_RESP_GROUPS_ALL is a table within the IGS - Student System product family, which Oracle classifies as obsolete in Release 12.1.1 and 12.2.2. The table stores person type responsibility group details, defining the association between a Person Type code and an Oracle EBS Responsibility, scoped by operating unit. In functional terms, it acts as a configuration repository that governs which responsibility is designated as the approval or processing group for a given person type within the Student System. As the _ALL suffix indicates, the table is partitioned or filtered by ORG_ID and is therefore multi-org enabled, meaning rows are stored per operating unit.

The ETRM metadata notes that this object is not implemented in the reference database, and its obsolete product classification means it will rarely be encountered in a standard, currently supported EBS instance. From a Data Vault modeling perspective, the heuristic classification supplied with the metadata is standalone. Because the table's primary key is a composite of business attributes and no FK dependencies were mined, it is best modeled as a hub-like structure anchored on the natural key (ORG_ID, RESPONSIBILITY_ID, PERSON_TYPE_CODE), with descriptive and audit attributes potentially split into a satellite should a warehouse model be constructed. This is a modeling suggestion only, not an Oracle-documented design.

Key Information Stored

The documented physical schema contains 10 columns. The primary key constraint, IGS_SS_PERTYP_RESP_GROUPS_PK, is defined over the composite of ORG_ID, RESPONSIBILITY_ID, and PERSON_TYPE_CODE. The unique index of the same name lists the columns in the order PERSON_TYPE_CODE, RESPONSIBILITY_ID, ORG_ID, which represents the business-key candidate set. There is no independent surrogate sequence key; the composite of these three business columns functions as the logical identifier.

• ORG_ID — the operating unit that owns the row; enforces multi-org data segregation and forms part of the composite primary key.
• RESPONSIBILITY_ID — foreign reference to the Oracle EBS responsibility assigned as the group for the person type; part of the composite key.
• PERSON_TYPE_CODE — the student system person type to which the responsibility group applies; part of the composite key.
• REQUIRE_APPROVAL_FLAG — controls whether approval is mandated for the person type/responsibility combination, driving workflow and validations.
• COMMENTS — free-text descriptive notes explaining the configuration or its purpose.
• CREATED_BY, CREATION_DATE — standard audit columns capturing row creation identity and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns capturing the most recent modification identity, timestamp, and login session.

Common Use Cases and Queries

The primary practical use is configuration review and diagnostics, since the object governs which responsibility serves a person type and whether approval is required. Typical reporting queries retrieve the mapping for a specific operating unit or responsibility, or audit changes against the standard WHO columns. A representative pattern is:

• SELECT person_type_code, responsibility_id, require_approval_flag, comments FROM igs_ss_pertyp_resp_groups_all WHERE org_id = :p_org_id;
• SELECT r.responsibility_name, p.person_type_code FROM igs_ss_pertyp_resp_groups_all p, fnd_responsibility_vl r WHERE p.responsibility_id = r.responsibility_id AND p.org_id = :p_org_id;
• Audit query: SELECT last_updated_by, last_update_date FROM igs_ss_pertyp_resp_groups_all WHERE last_update_date >= :p_since;

Because the table is obsolete and not implemented in the reference database, queries should be preceded by existence checks against ALL_TABLES before use in a live environment.

Related Objects

The metadata documents the primary key and unique index but no explicit foreign keys; relationship classification is standalone. The most significant related objects, therefore, are the standard EBS reference tables implied by the key columns and the audit infrastructure:

• FND_RESPONSIBILITY / FND_RESPONSIBILITY_VL — joined on RESPONSIBILITY_ID to resolve the responsibility name and application.
• FND_APPLICATION / FND_APPLICATION_VL — resolves the application owning the responsibility.
• HR_ALL_ORGANIZATION_UNITS / ORG_ORGANIZATION_DEFINITIONS — joined on ORG_ID to resolve the operating unit name.
• IGS person type reference tables (e.g., person type lookup or IGS_SS person type definitions) — joined on PERSON_TYPE_CODE.
• FND_USER — joined on CREATED_BY and LAST_UPDATED_BY for audit attribution.
• FND_LOGINS — joined on LAST_UPDATE_LOGIN where session-level audit tracing is required.

No dependent child tables were identified in the mined relationship data, confirming the standalone classification.