Search Results igr_is_info_req

Overview

The table IGR_IS_INFO_REQ is a data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically belonging to the IGS (Student System) product family, which is documented as obsolete. Its primary function is to serve as a staging table for Self Service information requests. In the context of student information systems, such staging tables are typically used to temporarily hold data submitted via web-based self-service portals before it is validated and processed into the core transactional tables. The "Obsolete" status indicates that the associated functionality may have been deprecated, superseded, or planned for removal in future releases, and its use in new developments is not recommended.

Key Information Stored

Based on the provided ETRM metadata, the table's structure centers on a unique identifier and foreign key relationships. The primary column is INQ_INFO_REQ_ID, which serves as the unique primary key for each staged information request record. Two critical foreign key columns establish relationships with other entities: PACKAGE_ITEM_ID and INQ_INQ_ID. While the exact nature of the referenced tables is not fully specified in the excerpt, these columns likely link a specific information request to a particular item or package within a student's record (PACKAGE_ITEM_ID) and to a master inquiry or application record (INQ_INQ_ID). The table's purpose suggests it may also store the actual data submitted by the student or applicant, such as updated contact details, document submissions, or responses to queries.

Common Use Cases and Queries

The primary use case for IGR_IS_INFO_REQ is to support the data flow from a student self-service portal into the backend IGS system. A common operational query would involve selecting records that have been staged but not yet processed. For example, a batch job might use a pattern like: SELECT * FROM IGR_IS_INFO_REQ WHERE process_flag = 'N'; (assuming a process flag column exists). Reporting use cases would focus on auditing the volume and type of information requests. Analysts might join this table to related inquiry tables to generate reports on student engagement, using SQL that joins on the INQ_INQ_ID column. Given the table's obsolete status, a critical use case in upgrades or migrations is to identify any remaining dependencies on this table before decommissioning the associated functionality.

Related Objects

The ETRM documentation specifies the following key relationships for IGR_IS_INFO_REQ:

• Primary Key: IGR_IS_INFO_REQ_PK on column INQ_INFO_REQ_ID.
• Foreign Keys (This table references):
  • Table: IGR_IS_INFO_REQ column PACKAGE_ITEM_ID references an unspecified parent table (denoted by '%' in the metadata).
  • Table: IGR_IS_INFO_REQ column INQ_INQ_ID references an unspecified parent table (denoted by '%' in the metadata).

These foreign keys indicate that IGR_IS_INFO_REQ is a child table. The INQ_INQ_ID strongly suggests a relationship to a core inquiry or application header table, which would likely be named similarly (e.g., IGR_INQUIRIES). The PACKAGE_ITEM_ID likely points to a table defining specific data items or forms within the student system. Other related objects would include any APIs or concurrent programs responsible for processing the staged data from this table into the live system.