Search Results interface_ps_appl_inst_id

Overview

The view IGS_AD_EDUGOAL_INT 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) module, which is documented as obsolete. This view serves as a direct interface layer for processing and storing education goal data associated with student applications. Its primary role is to act as a staging or intermediary point for education goal information that is being loaded or synchronized into the core application tables from external systems or batch processes. The view is built directly on the underlying table IGS_AD_EDUGOAL_INT_ALL, exposing its columns for querying and integration purposes. The documentation note "Not implemented in this database" indicates that while the object definition exists, it may not be populated or actively used in all deployment instances.

Key Information Stored

The view's columns are designed to manage the interface lifecycle for education goal records. Key columns include the unique identifier INTERFACE_EDUGOAL_ID and the foreign key INTERFACE_APPL_ID, which links to the parent application interface record. The EDU_GOAL_ID holds the actual goal code or identifier, while the MATCH_IND and STATUS columns are critical for tracking the processing state of the interface record (e.g., pending, matched, error). The ERROR_CODE column stores validation or processing failure information. Standard EBS audit columns such as CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE are present for tracking record history. The ORG_ID column supports multi-organization security, and the PROGRAM_ID, REQUEST_ID, and related columns are used for identifying concurrent requests that created or updated the data.

Common Use Cases and Queries

The primary use case for this view is monitoring and troubleshooting the data load process for application education goals. System administrators or integration developers would query this view to identify records that have failed to process into the core system. A typical query would check for records with a STATUS indicating an error or a specific ERROR_CODE. For example, to find all pending or errored records for a specific application interface ID, one might use: SELECT * FROM IGS_AD_EDUGOAL_INT WHERE INTERFACE_APPL_ID = <id> AND STATUS IN ('PENDING', 'ERROR');. Reporting on the volume and success rate of interface data loads over a period is another common scenario, leveraging the CREATION_DATE and STATUS columns. Since this is an interface object, direct data manipulation (DML) is typically performed via dedicated concurrent programs or APIs rather than ad-hoc SQL against the view itself.

Related Objects

Based on the provided relationship data, IGS_AD_EDUGOAL_INT has a defined dependency on another interface table. The key documented relationship is:

• Foreign Key Reference: The column INTERFACE_PS_APPL_INST_ID in IGS_AD_EDUGOAL_INT references the table IGS_AD_PS_APPL_INST_INT. This establishes a link between an education goal interface record and its corresponding program or course application instance within the interface schema, ensuring referential integrity during the data loading process.

The view itself is based on the table IGS_AD_EDUGOAL_INT_ALL, and its primary key is defined as IGS_AD_EDUGOAL_INT_ALL_PK on the INTERFACE_EDUGOAL_ID column.