Results for “igs_uc_trans_types”

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

Overview

IGS_UC_TRANS_TYPES is a reference (seed) table in the IGS — Student System product of Oracle E-Business Suite. It stores the set of UCAS (Universities and Colleges Admissions Service) transaction types that are valid for each UCAS system code recognized by the institution. In the UK higher-education admissions process, UCAS submits and receives applicant data through a range of transaction types (for example, applications, amendments, withdrawals, and replies). This table acts as the validation and decoding layer that maps each transaction type to a supported UCAS system, allowing the IGS UCAS integration programs to determine whether an inbound or outbound transaction is recognized before processing.

From a dimensional or Data Vault modeling perspective, the mined relationship classification for this object is standalone. It has no foreign keys to other documented tables and no dependent children, which suggests it is best modeled as a small, stable reference hub or reference satellite: a business-key-driven lookup table whose rows change only when UCAS introduces or retires transaction types. The row count is expected to be low (tens of rows), making it a natural candidate for caching in integration code.

Key Information Stored

The table is compact, with nine documented columns. Its primary key is the composite IGS_UC_TRANS_TYPES_PK (SYSTEM_CODE, TRANSACTION_TYPE), which is also the only unique index and therefore the business key. There is no separate surrogate sequence-driven identifier; the two business columns together serve as the row identity.

• SYSTEM_CODE — The UCAS system for which the transaction type is valid. Part of the composite primary key and the leading column in every lookup.
• TRANSACTION_TYPE — The code identifying the specific UCAS transaction. Second component of the composite primary key.
• DESCRIPTION — Human-readable description of the transaction type, used in inquiry screens, LOVs, and reports.
• ENABLED — Flag indicating whether the transaction type is currently active. Disabled rows are retained for history but are ignored by validation logic.
• CREATED_BY, CREATION_DATE — Standard WHO audit columns recording the seed or manual creation of the row.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the most recent change to the row, including the login that performed it.

The columns beyond the primary key are descriptive and audit-oriented. Because the table holds seeded information, most implementations should treat it as read-only and manage changes through the delivered seed data rather than through ad hoc DML.

Common Use Cases and Queries

The most common requirement is to confirm which transaction types are active for a given UCAS system, either during integration troubleshooting or when building a validation lookup. A typical query is:

• SELECT transaction_type, description FROM igs_uc_trans_types WHERE system_code = :p_system AND enabled = 'Y' ORDER BY transaction_type;
• Reporting on all supported transaction types across systems: SELECT system_code, transaction_type, description, enabled FROM igs_uc_trans_types ORDER BY system_code, transaction_type;
• Finding disabled types retained for historical transactions: SELECT * FROM igs_uc_trans_types WHERE enabled = 'N';
• Audit reconstruction using the WHO columns: SELECT transaction_type, last_updated_by, last_update_date FROM igs_uc_trans_types WHERE system_code = :p_system;

Because the table is small, it is frequently joined to staging or interface tables on SYSTEM_CODE and TRANSACTION_TYPE to filter invalid transactions and to supply the descriptive text on reports.

Related Objects

IGS_UC_TRANS_TYPES is documented as standalone, with no enforced foreign keys. Functionally, it is referenced by the UCAS integration and staging tables in the IGS schema that carry inbound and outbound transaction payloads. Typical dependent or sibling objects include:

• UCAS system definition table (for example IGS_UC_SYSTEMS), joined on SYSTEM_CODE.
• UCAS transaction or staging tables joined on SYSTEM_CODE and TRANSACTION_TYPE, where this table validates and decodes the transaction.
• IGS UCAS interface concurrent programs and packages that read this table to determine valid transactions.
• IGS UCAS inquiry forms and value sets built over SYSTEM_CODE and TRANSACTION_TYPE.

Any integration or report that processes UCAS transactions should treat this table as the authoritative reference for valid transaction types per system, filtering on ENABLED = 'Y' where only current activity is required.