Search Results spl_sequence_number




Overview
Explore in AI Chat

Overview

The IGS_CO_OU_CO view 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. This view serves as a security-filtered representation of the underlying IGS_CO_OU_CO_ALL table, which describes the link between a person (student) and a correspondence item, such as a letter or official communication. Its primary role is to enforce Multi-Org Access Control (MOAC) by filtering records based on the operating unit context (ORG_ID) derived from the user's session, ensuring users only see data relevant to their assigned organization. The view is constructed to be transparent to applications, which can query it as if it were a standard table.

Key Information Stored

The view's columns capture the core attributes of a person-correspondence relationship and standard EBS audit and processing information. The primary key uniquely identifies a link through PERSON_ID, CORRESPONDENCE_TYPE, REFERENCE_NUMBER, and ISSUE_DT. Key transactional columns include ADDR_TYPE, TRACKING_ID, DT_SENT, and UNKNOWN_RETURN_DT, which manage the correspondence's dispatch and return status. The SPL_SEQUENCE_NUMBER field, which was the subject of the user's search, is a critical identifier, often used to sequence or uniquely identify specific correspondence items or batches within the system. The ORG_ID is the central column for the MOAC security filter. Standard EBS columns like CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, REQUEST_ID, and PROGRAM_ID provide full lifecycle tracking and integration with concurrent manager requests.

Common Use Cases and Queries

A primary use case is auditing and reporting on correspondence sent to students. For instance, to find all correspondence for a specific person, a query would filter on PERSON_ID. The SPL_SEQUENCE_NUMBER is frequently used to locate a specific correspondence item when its reference details are known. A common reporting pattern involves joining this view to person (e.g., IGS_PE_PERSON) or correspondence master tables to generate mailing lists or delivery status reports. The following sample query demonstrates retrieving key details for a specific sequence number:

  • SELECT person_id, correspondence_type, reference_number, issue_dt, dt_sent, tracking_id FROM igs_co_ou_co WHERE spl_sequence_number = :p_seq_num AND org_id = :p_org_id;

Another critical operational use case is verifying the existence and status of a correspondence link before generating a duplicate, often by checking the combination of PERSON_ID, CORRESPONDENCE_TYPE, and SPL_SEQUENCE_NUMBER.

Related Objects

The view's structure and relationships are derived directly from its base table, IGS_CO_OU_CO_ALL. The documented primary key constraint, IGS_CO_OU_CO_PK, is defined on the columns (PERSON_ID, CORRESPONDENCE_TYPE, REFERENCE_NUMBER, ISSUE_DT). This key is likely referenced by other objects or application logic for data integrity. The metadata indicates a foreign key relationship where IGS_CO_OU_CO.CORRESPONDENCE_TYPE references another table (the target is denoted as '%' in the provided data, indicating the specific referenced table name was not captured in the excerpt). This implies a lookup or validation against a master table of correspondence types. Any application logic or reports that process student correspondence will depend on this view or its underlying table as the source of the person-correspondence association.