Search Results igr_is_info_req_n1

Overview

The IGS.IGR_IS_INFO_REQ table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically in the IGS (iGrants) product family. As documented, its primary function is to hold "Sel Service Staging Information Requested records." This indicates it serves as a staging or transactional table within a self-service interface, likely related to processing information requests or required documentation for inquiries. The table's role is to track specific information items or package components that have been requested or are required as part of an inquiry process, linking an inquiry to specific package items and managing their fulfillment status.

Key Information Stored

The table's structure is designed to manage the lifecycle of an information request. The most critical columns include the primary key, INQ_INFO_REQ_ID, which uniquely identifies each requested information record. The INQ_INQ_ID column links the request to its parent inquiry record, while PACKAGE_ITEM_ID is a foreign key identifying the specific information item or document from a package catalog. The STATUS column tracks the current state of the information request (e.g., Pending, Received, Complete). Standard EBS "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent program tracking columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) provide full auditability and integration with batch processes.

Common Use Cases and Queries

A primary use case is generating reports on outstanding information requests for inquiries or tracking the completion status of required documentation. Administrators may query this table to identify bottlenecks in the inquiry processing workflow. Common SQL patterns involve joining to the parent inquiry and package item tables to get descriptive information. For instance, to find all pending information requests for a specific inquiry, one might use:

• SELECT req.* FROM igs.igr_is_info_req req WHERE req.inq_inq_id = :p_inquiry_id AND req.status = 'PENDING';

Another frequent operation is auditing changes via the Who columns, or using the REQUEST_ID to trace records created by a specific concurrent program execution. The table is central to any self-service process where applicants or inquiries must submit supplemental information.

Related Objects

Based on the provided metadata, IGR_IS_INFO_REQ has defined relationships with other tables via its foreign key columns. The table itself is referenced by an APPS synonym (IGR_IS_INFO_REQ), which is standard for EBS object access. Its primary key is enforced by the unique index IGR_IS_INFO_REQ_PK on INQ_INFO_REQ_ID. The documented foreign keys indicate it references two parent tables:

• TABLE: IGS.IGR_IS_INFO_REQ.INQ_INQ_ID → This column is a foreign key to a parent inquiry table (likely named IGR_INQUIRY or similar), establishing the core relationship between an information request and the original inquiry.
• TABLE: IGS.IGR_IS_INFO_REQ.PACKAGE_ITEM_ID → This column is a foreign key to a package item table (exact name not fully specified in snippet, but referenced as "Packge Item table"), linking to the catalog of requestable information items or documents.

The non-unique indexes IGR_IS_INFO_REQ_N1 (on INQ_INQ_ID) and IGR_IS_INFO_REQ_N2 (on PACKAGE_ITEM_ID) are optimized for performance in queries joining on these foreign key relationships.