Results for “igs_co_itm”

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

Overview

IGS_CO_ITM is a reporting and integration view owned by the APPS schema within the Oracle E-Business Suite Student System (IGS) product family. It presents correspondence items dispatched to students, encompassing both system-generated correspondence and non-system-generated items that users have elected to register against individual students. The view is a secured (multi-tenant aware) wrapper over the base table IGS_CO_ITM_ALL, and it plays a central role in operational reporting, data extraction, and downstream integration scenarios where institutions need visibility into student correspondence activity, delivery outcomes, and the concurrent request or job context that produced each item.

The view carries a status of VALID and is documented in ETRM for both Oracle EBS 12.1.1 and 12.2.2. Because the definition filters rows through an ORG_ID predicate derived from USERENV('CLIENT_INFO'), the view enforces the same Multi-Org access rules applied to the underlying table, returning only correspondence belonging to the operating unit currently set in the user's session (or rows with a null ORG_ID when no context is established).

Underlying Base Objects

The documented base object for this view is IGS_CO_ITM_ALL, from which all projected columns originate. No additional joined base objects are documented in the ETRM metadata, indicating that IGS_CO_ITM is a single-table projection view rather than a join-based presentation layer. The WHERE clause compares the operating unit column against a value parsed from the first ten characters of the CLIENT_INFO session variable, reverting to -99 when no meaningful context is supplied. This makes the view functionally identical to the base table for a correctly initialized session, while transparently restricting the row set for users operating within a specific business unit.

Key Columns

• ROW_ID — the ROWID of the underlying row, useful for direct row addressing and de-duplication in extracts.
• CORRESPONDENCE_TYPE and REFERENCE_NUMBER — classify the correspondence and provide the business reference for the item.
• S_JOB_NAME, REQUEST_JOB_ID, OUTPUT_NUM, and REQUEST_JOB_RUN_ID — tie the correspondence to the concurrent request/job that generated it, including which output file (such as a PDF or letter) corresponds to the item. The presence of REQUEST_JOB_ID is the attribute most frequently queried by users tracing a correspondence item back to its generating concurrent program run.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE — standard concurrent request audit columns identifying the request and program that created the record.
• JOB_REQUEST_ID and REQUEST_NUM — the original job request identifier and its human-readable request number.
• CAL_TYPE, CI_SEQUENCE_NUMBER, COURSE_CD, CV_VERSION_NUMBER, UNIT_CD, UV_VERSION_NUMBER — academic context linking the correspondence to a calendar type, sequence, course/unit, and version.
• ORIGINATOR_PERSON_ID — the person or student the correspondence concerns.
• ORG_ID — the operating unit, which drives the Multi-Org filter described above.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATE_DT, and COMMENTS — standard audit and descriptive columns.

Common Use Cases and Queries

The most common use case is tracing student correspondence generated by a specific concurrent request or job, since users frequently search by the request_job_id attribute. A representative query follows:

• Trace by job: SELECT correspondence_type, reference_number, s_job_name, output_num, creation_date FROM igs_co_itm WHERE request_job_id = :job_id;
• Correspondence history for a person: SELECT correspondence_type, reference_number, creation_date, program_id FROM igs_co_itm WHERE originator_person_id = :person_id ORDER BY creation_date DESC;
• Delivery audit by concurrent program: SELECT request_id, program_id, request_job_run_id, COUNT(*) FROM igs_co_itm GROUP BY request_id, program_id, request_job_run_id;
• Course-specific extract: SELECT course_cd, unit_cd, cal_type, ci_sequence_number FROM igs_co_itm WHERE course_cd = :course;

Because the view applies the ORG_ID predicate automatically, queries need not filter on operating unit, though adding an explicit ORG_ID restriction improves performance when reporting across several business units.

Oracle Proprietary, Confidential Information — Legal Notices.