Search Results current_inst

Overview

IGS_AD_RELACAD_INT is a reporting and integration view belonging to the IGS - Student System product family in Oracle E-Business Suite. In ETRM 12.2.2 metadata the object is flagged as Obsolete, and the implementation notes state "Not implemented in this database." This qualification is significant: the view is a legacy artifact carried forward from earlier Student System releases and is not deployed in all environments. Where it does exist, IGS_AD_RELACAD_INT exposes staged academic relations and academic attainment interface records — the inbound records that feed the student academic record structures used by Student System registration, records, and graduation processing.

The view functions as a thin, row-addressed projection over the interface staging table. It does not perform transformation, validation, or aggregation; filtering, matching, and error detection are driven by the STATUS, ERROR_CODE, and MATCH_IND columns that the view surfaces. Reporting on interface loads, reconciliation of staging rows, and troubleshooting of rejected records are the primary uses.

The column PLAN_COMPLETION_DATE, which the user searched for, is the anticipated or actual date on which the student is expected to complete the program of study associated with the academic relation. It is a single date attribute on the interface record, distinct from START_DATE, END_DATE, and the PROGRAM_UPDATE_DATE audit column.

Underlying Base Objects

The ETRM metadata documents no referenced base objects, but the view text is explicit: the sole source object is IGS_AD_RELACAD_INT_ALL. The view is defined as a single SELECT from that table, aliased as TAB, projecting ROWID as ROW_ID together with every business and audit column. There are no joins, no unions, and no filters in the definition.

Note the two inline NULL expressions positioned between CURRENT_INST and PROGRAM_CODE. These occupy the slots corresponding to the PROGRAM_TYPE_ATTEMPTED and PROGRAM_TYPE_EARNED columns listed in the view's column dictionary, meaning the view and its documented column list are not perfectly aligned — the view text does not project those two attributes. This mismatch is a characteristic of obsolete interface views and should be accounted for when interpreting column positions or building dependent objects. Because the view is unobscured, any index or partition strategy on IGS_AD_RELACAD_INT_ALL applies directly, and row-level access is governed by the underlying table's security rather than by any view-level predicate.

Key Columns

• ROW_ID — the ROWID of the underlying row, used to address the staged record for update or correction.
• ORG_ID — operating unit / business group identifier, the multi-tenant discriminator for the record.
• INTERFACE_RELACAD_ID and INTERFACE_RELATIONS_ID — the interface row identifier and the related relations identifier linking the staging row to its academic relation context.
• INSTITUTION_CODE and CURRENT_INST — the institution associated with the record and an indicator of whether it is the student's current institution.
• PROGRAM_CODE and VERSION_NUMBER — the program of study and its version.
• START_DATE and END_DATE — the effective span of the academic relation.
• PLAN_COMPLETION_DATE — the expected or planned completion date for the program.
• DEGREE_ATTEMPTED and DEGREE_EARNED — the degree being pursued and the degree awarded.
• MATCH_IND, STATUS, ERROR_CODE — the integration control flags: whether the row matched an existing record, its processing status, and the rejection reason when processing fails.
• COMMENTS — free-text note carried from the staging record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard who-columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the load process that staged the row.

Common Use Cases and Queries

The dominant use case is monitoring interface processing. Administrators list unprocessed or errored staging rows, then drill into the underlying table to correct them and resubmit the load.

Locating records by planned completion date:

SELECT interface_relacad_id, program_code, plan_completion_date,
       degree_earned, status, error_code
FROM   igs_ad_relacad_int
WHERE  plan_completion_date BETWEEN :p_from AND :p_to
ORDER  BY plan_completion_date;

Identifying failed rows for a specific concurrent request:

SELECT row_id, interface_relations_id, status, error_code, comments
FROM   igs_ad_relacad_int
WHERE  request_id = :request_id
AND    status NOT IN ('PROCESSED','SUCCESS');

Reporting unmatched records awaiting reconciliation:

SELECT org_id, institution_code, program_code, version_number,
       start_date, end_date, plan_completion_date, match_ind
FROM   igs_ad_relacad_int
WHERE  match_ind IS NULL OR match_ind = 'N';

Because the object is marked obsolete and may be absent, implementations should verify existence in ALL_VIEWS before referencing it in custom code or reports, and should migrate long-term interfaces to the supported successor objects in the Student System data model.