Results for “transaction_sequence_id”

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

Overview

IGSBV_UC_TRANSACTIONS is a read-only base view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGS (Student System) product family. Its documented purpose is to expose the UCAS transactions table — the staging and transaction record for data exchanged between an institution and UCAS (the UK Universities and Colleges Admissions Service) — in a denormalised, business-friendly form. The view renames the underlying technical columns into meaningful aliases, such as TRANSACTION_SEQUENCE_ID for UC_TRAN_ID and APPLICANT_UCAS_NUMBER for APP_NO, so that downstream reports, concurrent programs, and interfaces can reference admissions-transaction data without depending on the raw physical column names.

Because UCAS admissions processing generates a high volume of applicant, choice, decision, and offer records, this view serves as a stable reporting and integration surface. It is declared WITH READ ONLY, confirming that it is intended strictly for query and retrieval; all inserts and updates must be performed against the base table or through the Student System's UCAS processing APIs. The view is documented as VALID in both EBS 12.1.1 and 12.2.2, with no structural differences noted between the two releases.

Underlying Base Objects

The view text is defined over a single base table, IGS_UC_TRANSACTIONS, referenced with the alias TR. ETRM documentation does not list additional referenced objects, and the underlying table is not joined to any other entity within the view definition. Consequently, all columns exposed by IGSBV_UC_TRANSACTIONS map one-to-one to columns of IGS_UC_TRANSACTIONS; the view adds no filter predicates, joins, or derived expressions. This one-to-one relationship makes the view a transparent projection layer: the row count, key structure, and transactional semantics are entirely inherited from the base table. The APPS synonym or grant structure should be relied upon for access, since the view is owned by APPS and is not defined in the IGS schema itself.

Key Columns

The view exposes thirty-one columns spanning applicant identity, choice, decision, and audit information. Significant columns include:

• TRANSACTION_SEQUENCE_ID (UC_TRAN_ID) — the sequence identifier for the transaction record.
• TRANSACTION_ID, TRANSACTION_TYPE, UPDATER, and ERROR_CODE — identify the transaction, its processing category, the updating process, and any error returned during UCAS processing.
• APPLICANT_UCAS_NUMBER and APPLICANT_CHOICE_NUMBER — the UCAS applicant identifier and the specific choice (institution/course preference) to which the transaction relates.
• UCAS_CYCLE, ENTRY_MONTH, ENTRY_YEAR, and ENTRY_POINT — the admissions cycle and the requested point of entry, including the entry point value that is the subject of this search.
• DECISION, UCAS_PROGRAM_CODE, and UCAS_CAMPUS — the decision recorded against the choice and the associated programme and campus codes.
• SUMMARY_OF_CONDITIONS, COMMENTS_IN_OFFER, RETURN1, RETURN2, and TEST_CONDITION_CATEGORY/TEST_CONDITION_NAME — offer conditions, free-text comments, return fields, and any test/qualification conditions attached to the offer.
• HOLD_FLAG, SENT_TO_UCAS_FLAG, AUTO_GENERATED_FLAG, and INSTITUTION_REFERENCE, UCAS_SYSTEM_CODE, MODULAR, PART_TIME — processing controls, transmission status, and programme delivery attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard Oracle WHO audit columns.

Common Use Cases and Queries

Typical use cases include monitoring UCAS transaction flow between the institution and UCAS, reconciling sent versus held transactions, reporting on decisions and offers by cycle or entry point, and diagnosing processing errors. The following query retrieves all transactions for a given UCAS cycle with their entry point and decision:

SELECT applicant_ucas_number,
       applicant_choice_number,
       transaction_type,
       decision,
       entry_point,
       entry_month,
       entry_year,
       sent_to_ucas_flag
FROM   apps.igsbv_uc_transactions
WHERE  ucas_cycle = :p_cycle
ORDER  BY applicant_ucas_number, applicant_choice_number;

To identify records that failed UCAS processing, filtering on the error column is effective:

SELECT transaction_id,
       transaction_type,
       applicant_ucas_number,
       error_code,
       last_update_date
FROM   apps.igsbv_uc_transactions
WHERE  error_code IS NOT NULL;

Because the view is read-only and defined over a single table, query performance depends on indexes and statistics on IGS_UC_TRANSACTIONS; predicates on UCAS_CYCLE, APPLICANT_UCAS_NUMBER, and the transaction key columns generally offer the best selectivity.