Results for “igs_co_ou_co_all”

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

Overview

IGS_CO_OU_CO_ALL is a transactional table in the Oracle E-Business Suite IGS (Student System) product family, which Oracle classifies as obsolete in Release 12.1.1 and 12.2.2. The table describes the link between a person and a correspondence item, capturing the correspondence generated for or issued to a specific party together with delivery, tracking, and workflow metadata. In the ETRM documentation the object is marked "Not implemented in this database," meaning the physical table is not instantiated in the reference environment; nonetheless the documented schema of 21 columns and the associated constraints describe its intended structure.

Because the primary key is a composite of PERSON_ID, CORRESPONDENCE_TYPE, REFERENCE_NUMBER, and ISSUE_DT — all descriptive business attributes rather than a single surrogate identifier — the table behaves as a link between parties and correspondence definitions while carrying its own descriptive attributes. A heuristic Data Vault classification mined from the foreign-key structure suggests this object is satellite-leaning: it attaches descriptive state (address type, tracking, sent and return dates, comments) to a business key that itself is composed of foreign references to HZ_PARTIES and the IGS correspondence definition tables. This classification should be treated as a modeling suggestion rather than a documented Oracle designation.

Key Information Stored

The composite unique index IGS_CO_OU_CO_U1 (PERSON_ID, CORRESPONDENCE_TYPE, REFERENCE_NUMBER, ISSUE_DT) mirrors the primary key IGS_CO_OU_CO_PK and represents the business-key candidate for the record. The most significant documented columns are:

• PERSON_ID — the party for whom the correspondence was generated; a foreign key to HZ_PARTIES.
• CORRESPONDENCE_TYPE — classification of the correspondence; joins to IGS_CO_ITM_ALL and IGS_CO_S_LTR.
• REFERENCE_NUMBER — the business reference identifying the correspondence instance.
• ISSUE_DT — the date the correspondence was issued, completing the primary key.
• ADDR_TYPE — the address type used for delivery of the correspondence.
• TRACKING_ID — foreign key to IGS_TR_ITEM_ALL for item tracking.
• DT_SENT and UNKNOWN_RETURN_DT — dispatch and undeliverable/return dates.
• LETTER_REFERENCE_NUMBER and SPL_SEQUENCE_NUMBER — letter reference and sequence values; SPL_SEQUENCE_NUMBER joins to IGS_CO_S_LTR.
• COMMENTS — free-text annotation.
• ORG_ID — multi-org operating unit context.

The WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent-manager columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) provide audit and process provenance.

Common Use Cases and Queries

Typical reporting scenarios include identifying all correspondence issued to a person, analysing undelivered or returned items, and reconciling correspondence against tracking records. Because the object is obsolete and not implemented, these patterns are primarily relevant to legacy data migration, archival reporting, and historical reconciliation.

• Correspondence history for a party: select from IGS_CO_OU_CO_ALL filtered by PERSON_ID, ordering by ISSUE_DT.
• Undeliverable items: filter where UNKNOWN_RETURN_DT is not null to isolate returns.
• Tracking reconciliation: join TRACKING_ID to IGS_TR_ITEM_ALL to compare sent versus tracked records.
• Volume by type and period: group by CORRESPONDENCE_TYPE and ISSUE_DT for trend reporting.
• Multi-org reporting: restrict by ORG_ID to satisfy operating-unit security.

A representative pattern is: SELECT c.PERSON_ID, c.CORRESPONDENCE_TYPE, c.ISSUE_DT, c.DT_SENT FROM IGS_CO_OU_CO_ALL c WHERE c.ORG_ID = :org_id AND c.UNKNOWN_RETURN_DT IS NOT NULL.

Related Objects

The following dependencies are documented in the ETRM metadata and represent the most significant joins and constraints:

• HZ_PARTIES — joined via IGS_CO_OU_CO_ALL.PERSON_ID; supplies party identity.
• IGS_CO_ITM_ALL — joined via CORRESPONDENCE_TYPE; the correspondence item definition.
• IGS_CO_S_LTR — joined via CORRESPONDENCE_TYPE and SPL_SEQUENCE_NUMBER; the letter template.
• IGS_TR_ITEM_ALL — joined via TRACKING_ID; item tracking records.
• IGS_CO_OU_CO_REF_ALL — a dependent child table referencing PERSON_ID, CORRESPONDENCE_TYPE, REFERENCE_NUMBER, and ISSUE_DT back to this object.

No documented views or public APIs accompany this table in the supplied metadata, consistent with its obsolete status.