Results for “igs_pe_data_groups”

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

Overview

IGS_PE_DATA_GROUPS is a reporting and integration view within the Oracle E-Business Suite Student System (IGS) product family. In the ETRM metadata for release 12.2.2, the object is classified under the IGS – Student System module and carries an Obsolete designation, indicating that it belongs to a legacy component of the E-Business Suite that is no longer actively maintained in current installations. The view exposes a filtered, organization-aware projection of personnel data group records, presenting columns such as DATA_GROUP, DESCRIPTION, LVL, LVL_DESCRIPTION, and CLOSED_IND alongside standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).

Its principal design characteristic is that it does not return every row from its base object. Instead, it applies an ORG_ID predicate that resolves against the session-level CLIENT_INFO context established by Oracle Application Object Library multi-org security. This makes the view suitable for multi-organization reporting where the caller's current organization context must be honored automatically. The LVL and LVL_DESCRIPTION columns describe the hierarchy level associated with each data group, which is the attribute most commonly targeted by users searching on the term "lvl_description."

Underlying Base Objects

The view is defined over a single documented base object: IGS_PE_DATA_GROUPS_ALL. The _ALL suffix follows the standard EBS multi-organization naming convention, meaning the table stores rows partitioned by ORG_ID, with organization-specific records coexisting in one physical table. The view text selects all columns from this table and appends the ROWID as ROW_ID:

SELECT TAB.ROWID ROW_ID, TAB.ORG_ID, TAB.DATA_GROUP_ID, TAB.DATA_GROUP, TAB.DESCRIPTION, TAB.LVL, TAB.LVL_DESCRIPTION, TAB.CLOSED_IND, TAB.CREATED_BY, TAB.CREATION_DATE, TAB.LAST_UPDATED_BY, TAB.LAST_UPDATE_DATE, TAB.LAST_UPDATE_LOGIN FROM IGS_PE_DATA_GROUPS_ALL TAB WHERE ...

The WHERE clause compares the row's ORG_ID to the organization identifier parsed from the session's USERENV('CLIENT_INFO'), using NVL and TO_NUMBER(DECODE(SUBSTRB(...))) to handle null or blank client information. When no organization context is available, both sides default to -99, so the view behaves as a secured, context-sensitive subset rather than a plain synonym. No additional referenced base objects are documented in the ETRM metadata.

Key Columns

• ROW_ID — the ROWID of the underlying IGS_PE_DATA_GROUPS_ALL row, useful for direct row addressing.
• ORG_ID — the operating unit or organization owning the data group record; drives the view's security filter.
• DATA_GROUP_ID — the primary surrogate identifier for the data group.
• DATA_GROUP — the descriptive code or name of the personnel data group.
• DESCRIPTION — human-readable text describing the data group.
• LVL — the numeric hierarchy level assigned to the data group.
• LVL_DESCRIPTION — the descriptive label corresponding to that hierarchy level; this is the column most frequently sought by users searching on "lvl_description."
• CLOSED_IND — indicator showing whether the data group is inactive or closed to further use.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — standard EBS auditing columns recording who created and last modified the record and when.

Common Use Cases and Queries

Typical use is reporting on the hierarchy levels of personnel data groups for the current organization, or joining the view to other IGS personnel tables by DATA_GROUP_ID. A representative query listing all open data groups with their level descriptions is:

SELECT data_group_id, data_group, description, lvl, lvl_description FROM igs_pe_data_groups WHERE closed_ind = 'N' ORDER BY lvl, data_group;

A second common pattern retrieves only level information for cross-validation against a hierarchy table:

SELECT data_group, lvl_description FROM igs_pe_data_groups WHERE lvl IS NOT NULL;

Because the view is marked obsolete and not implemented in the referenced database, these queries should be validated against the target instance before being relied upon. Where the object is absent, equivalent information may reside in successor tables within the current Student System data model.