Results for “conc_request_id”

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

Overview

IGS_HE_EXT_RUN_DTLS is a table in the IGS (Student System) product schema of Oracle E-Business Suite, documented as VALID in ETRM for releases 12.1.1 and 12.2.2. Its stated purpose is to contain all the Extract Run Details for each run of the Extract process, making it the central record of an extract execution in the Higher Education statistics extraction and return submission flow. Each row corresponds to one run of the extract process, identified by a surrogate run identifier, and carries the submission context, processing phase, concurrent request linkage, and file output details for that run. In a Data Vault modeling sense, the mined relationship structure suggests a hub-leaning classification: the table is anchored on a single surrogate key (EXTRACT_RUN_ID) and is referenced by multiple child tables rather than acting as a transactional satellite of another hub. This makes it a natural candidate for a hub entity with dependent satellites and links for the referencing tables.

Key Information Stored

The primary key is IGS_HE_EXT_RUN_DTLS_PK, defined on EXTRACT_RUN_ID, which is the surrogate identifier for an extract run and is also documented as the single unique index candidate (IGS_HE_EXT_RUN_DTLS_U1). The most significant columns include:

• EXTRACT_RUN_ID — surrogate primary key and foreign key target for all dependent tables.
• SUBMISSION_NAME, USER_RETURN_SUBCLASS, RETURN_NAME — the submission and return context for the run; these participate in the foreign key to IGS_HE_SUBMSN_RETURN.
• EXTRACT_PHASE — the stage of extraction the run represents.
• STUDENT_EXT_RUN_ID — linkage to the student-level extract run.
• CONC_REQUEST_ID, CONC_REQUEST_STATUS — the concurrent request that executed the extract and its current status.
• EXTRACT_RUN_DATE — date the extract run was executed.
• FILE_NAME, FILE_LOCATION, DATE_FILE_SENT — the generated extract file, where it resides, and when it was transmitted.
• EXTRACT_OVERRIDE, VALIDATION_KIT_RESULT, HESA_VALIDATION_RESULT — override flag and the results of validation kit and HESA validation processing.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical reporting traces the lifecycle of an extract run and its outcome. A frequent pattern joins the run header to its parameters, data lines, exceptions, and interim records on EXTRACT_RUN_ID:

SELECT d.extract_run_id, d.return_name, d.extract_phase,
       d.conc_request_id, d.conc_request_status,
       d.file_name, d.extract_run_date
FROM   igs.igs_he_ext_run_dtls d
WHERE  d.submission_name = :submission_name
AND    d.extract_run_date >= :from_date
ORDER  BY d.extract_run_date DESC;

Auditing validation outcomes uses the VALIDATION_KIT_RESULT and HESA_VALIDATION_RESULT columns, while operational monitoring correlates CONC_REQUEST_ID and CONC_REQUEST_STATUS with the concurrent manager. Historical reconciliation of transmitted files relies on FILE_NAME, FILE_LOCATION, and DATE_FILE_SENT.

Related Objects

• IGS_HE_SUBMSN_RETURN — referenced by this table via SUBMISSION_NAME, USER_RETURN_SUBCLASS, and RETURN_NAME; provides the submission and return definition.
• IGS_HE_EX_RN_DAT_LN — child table keyed by EXTRACT_RUN_ID, holding extract run data lines.
• IGS_HE_EXT_RUN_PRMS — child table keyed by EXTRACT_RUN_ID, holding extract run parameters.
• IGS_HE_EXT_RUN_INTERIM — child table keyed by EXTRACT_RUN_ID, holding interim extract data.
• IGS_HE_EXT_RUN_EXCP — child table keyed by EXTRACT_RUN_ID, holding extract exceptions.