Search Results original_content_id

Overview

IGS.IGS_CO_PREV_REQS is a transactional table in the Oracle E-Business Suite Integrated Gestión? No — in the Oracle EBS Intelligent Grants/Student Systems (IGS) product family, specifically the Correspondence (CO) module. It is used to stage and hold a correspondence request for preview, and subsequently for distribution. Each row captures the complete payload required to render, preview, and dispatch an outbound communication — an award letter, admission notification, or similar system letter — to a recipient such as an applicant, student, or external party.

The table sits in the APPS_TS_TX_DATA tablespace, and it is populated by concurrent processes that prepare correspondence output before the fulfillment server delivers it. Because the row is created at preview time and only released for distribution afterward, the table functions as a staging area between request generation and actual delivery.

From a dimensional-modeling perspective, the mined dependency classification is satellite-leaning. This suggests treating the table as a satellite attached to a correspondence-request hub, with the composite key CONCURRENT_REQUEST_ID + FF_REQUEST_HIST_ID providing the grain; the many descriptive attributes (recipient, content, media, award) are the satellite's descriptive payload. This is a heuristic suggestion, not a documented Data Vault implementation.

Key Information Stored

The primary key IGS_CO_PREV_REQS_PK is a composite of CONCURRENT_REQUEST_ID and FF_REQUEST_HIST_ID. These two columns are also the documented business-key candidates via the unique index. Every other column is descriptive. The most operationally significant columns are:

• CONCURRENT_REQUEST_ID — the concurrent request that generated the correspondence row.
• FF_REQUEST_HIST_ID — fulfillment request history identifier, tying the row to delivery tracking.
• LETTER_TYPE_CODE and SYS_LTR_CODE — the document type and system letter code driving letter selection.
• PERSON_ID and ORG_UNIT_ID — recipient party identifiers.
• EMAIL_ADDRESS, REPLY_EMAIL, SENDER_EMAIL, CC_EMAIL, FAX_NUMBER — delivery endpoints.
• MEDIA_TYPE_CODE — delivery channel (EMAIL, FAX, PRINT).
• ORIGINAL_CONTENT_ID, CURRENT_CONTENT_ID, ORIGINAL_VERSION_ID, CURRENT_VERSION_ID — pointers to the rendered content and versions.
• AWD_CAL_TYPE, AWD_CI_SEQ_NUMBER, AWARD_PRD_CD, AWARD_YEAR — award calendar and award-cycle context; AWD_CI_SEQ_NUMBER is the sequence number the user searched for.
• REQUEST_STATUS_CODE — workflow state of the preview/distribution request.
• REPLY_DAYS — interval before a resend is permitted.
• OBJECT_VERSION_NUMBER and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) — concurrency and audit control.

Common Use Cases and Queries

Because the table holds preview-stage correspondence, it is queried heavily for operational monitoring: identifying letters awaiting release, diagnosing delivery failures, and auditing what was sent to which recipient.

• Status monitoring: SELECT CONCURRENT_REQUEST_ID, FF_REQUEST_HIST_ID, REQUEST_STATUS_CODE, MEDIA_TYPE_CODE FROM IGS.IGS_CO_PREV_REQS WHERE REQUEST_STATUS_CODE = 'PENDING';
• Recipient lookup: join on PERSON_ID to person tables to reconcile recipients with email/fax endpoints.
• Award-cycle drill-down using AWD_CAL_TYPE, AWD_CI_SEQ_NUMBER, and AWARD_PRD_CD to verify which awards were communicated in a cycle.
• Resend eligibility: SELECT EMAIL_ADDRESS, REPLY_DAYS, LAST_UPDATE_DATE FROM IGS.IGS_CO_PREV_REQS WHERE SYSDATE > LAST_UPDATE_DATE + REPLY_DAYS;
• Content reconciliation: compare ORIGINAL_CONTENT_ID to CURRENT_CONTENT_ID to detect re-rendered letters.

Reports typically aggregate counts by LETTER_TYPE_CODE, MEDIA_TYPE_CODE, and status for throughput and SLA analysis.

Related Objects

• IGS_CO_MAPPING — referenced by the SYS_LTR_CODE foreign key; maps system letter codes to letter templates and sources.
• FF_REQUEST_HIST (fulfillment request history) — related through FF_REQUEST_HIST_ID, carrying the delivery lifecycle.
• Content tables keyed by CONTENT_ID — the original and current content payloads referenced by ORIGINAL_CONTENT_ID and CURRENT_CONTENT_ID.
• Person/Party tables keyed by PERSON_ID and ORG_UNIT_ID — recipient identification.
• Concurrent request tables (FND_CONCURRENT_REQUESTS) — linked via CONCURRENT_REQUEST_ID for request-level traceability.
• IGS_CO_PREV_REQS_N1 index — a non-unique index on FF_REQUEST_HIST_ID, supporting fulfillment-based access paths.

The table is primarily referenced through joins by key rather than by dependent child objects, reinforcing its satellite role relative to correspondence and fulfillment hubs.