Results for “comments_in_offer”

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

Overview

IGS_UC_TRANSACTIONS is a transactional table within the IGS (Student System) product family in Oracle E-Business Suite, holding the admission process transactions that must be transmitted to the UCAS view known as 'TranIn'. UCAS is the United Kingdom's Universities and Colleges Admissions Service, and the TranIn view represents the inbound stream of admission data that institutions submit to UCAS. This table therefore acts as a staging and audit repository for every admission-related event—decisions, offers, modifications, and withdrawals—that the institution intends to communicate to the central admissions service during an application cycle.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries its own surrogate primary key (UC_TRAN_ID) rather than functioning as a pure junction between two hubs, and it records descriptive attributes alongside a reference to configuration defaults. It is best understood as a transaction-grain satellite attached to the admissions process, capturing the evolving state of UCAS-bound transactions over time.

Key Information Stored

The table is documented with thirty-three columns. The most operationally significant are:

• UC_TRAN_ID — the surrogate primary key, enforced by IGS_UC_TRANSACTIONS_PK and also by the unique index IGS_UC_TRANSACTIONS_U1. This is the sole business-key candidate documented.
• TRANSACTION_ID and TRANSACTION_TYPE — identify the UCAS transaction and classify its nature (for example, a decision, offer amendment, or withdrawal).
• APP_NO and CHOICE_NO — the UCAS application number and the specific choice (institution/course line) to which the transaction applies.
• DECISION and PROGRAM_CODE — the admission decision and the programme against which it is made.
• CAMPUS, ENTRY_MONTH, ENTRY_YEAR, and ENTRY_POINT — the delivery location and intake details.
• SENT_TO_UCAS and ERROR_CODE — transmission status and any failure reason, central to interface monitoring.
• HOLD_FLAG and AUTO_GENERATED_FLAG — control flags for release suppression and automated creation.
• SYSTEM_CODE — the foreign key to IGS_UC_DEFAULTS, linking the transaction to UCAS configuration.
• UCAS_CYCLE and SOC — the admissions cycle and subject/occupational classification.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE — standard EBS audit columns.

Common Use Cases and Queries

The primary use case is troubleshooting and monitoring the UCAS outbound interface. Institutions routinely query transactions that have not yet been transmitted, or that have failed transmission, to resolve submission errors before cycle deadlines.

• Identify unsent transactions: SELECT UC_TRAN_ID, APP_NO, CHOICE_NO, TRANSACTION_TYPE FROM IGS_UC_TRANSACTIONS WHERE SENT_TO_UCAS = 'N' AND HOLD_FLAG = 'N'.
• Investigate failures: SELECT * FROM IGS_UC_TRANSACTIONS WHERE ERROR_CODE IS NOT NULL ORDER BY DATETIMESTAMP DESC.
• Trace activity for a specific applicant: SELECT * FROM IGS_UC_TRANSACTIONS WHERE APP_NO = :app_no ORDER BY DATETIMESTAMP.
• Reconcile cycle volumes by transaction type: aggregate counts grouped by TRANSACTION_TYPE and UCAS_CYCLE for admissions reporting.

These patterns support daily interface reconciliation, error-clearing workflows, and audit reporting for admissions offices.

Related Objects

The documented foreign key establishes a dependency from IGS_UC_TRANSACTIONS.SYSTEM_CODE to IGS_UC_DEFAULTS, meaning every row resolves its UCAS system configuration through that parent table. The unique index IGS_UC_TRANSACTIONS_U1 on UC_TRAN_ID reinforces the primary-key constraint. Beyond these, the table is referenced by the UCAS 'TranIn' view interface, which reads transaction rows for transmission, and is typically joined to application and decision entities within the IGS Student System to enrich transaction records with applicant and programme context. Administrators should treat IGS_UC_DEFAULTS as the principal parent object and the TranIn transmission process as the principal consumer.