Search Results igs_ad_imp_stats

Overview

The IGS.IGS_AD_IMP_STATS table is a transactional statistics repository within the Oracle EBS IGS – Student System product family. As documented in the ETRM 12.1.1 physical schema, it holds statistical information about the processing that occurs during a single run of the admission import process. Rather than storing the imported admission records themselves, this table captures the counts and outcomes — totals processed, warnings raised, successes, and errors — for each logical entity handled during that run. This makes it a diagnostic and monitoring object used by administrators and technical staff to verify the health of a batch load after the fact.

From a Data Vault modeling perspective, the mined relationship data classifies this object as standalone, with a heuristic suggestion of a satellite pattern. That is, it records descriptive, run-scoped metrics keyed to a parent processing event (the interface run), rather than representing an independent hub or a linking construct between other business entities. No foreign keys are documented, reinforcing its role as an isolated statistics snapshot.

Key Information Stored

All columns reside in the IGS schema, and the documented column count is sixteen. The most significant columns are:

• INTERFACE_RUN_ID — The identifier of the admission import run. Along with ENTITY_NAME it forms the composite primary key, tying each row to a specific batch execution.
• ENTITY_NAME — The logical entity or object being processed within the run; the second component of the composite key, so statistics are segmented per entity.
• SRC_CAT_CODE — The source category code identifying the origin or classification of the imported data.
• TOTAL_REC_NUM — The total number of records considered for the entity during the run.
• TOTAL_WARN_NUM — The number of records that produced warnings.
• TOTAL_SUCCESS_NUM — The number of records successfully processed.
• TOTAL_ERROR_NUM — The number of records that failed with errors.
• CREATED_BY, CREATION_DATE — Standard audit columns recording who created the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns for the most recent modification.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context identifying the requesting run, the application, the program, and its update timestamp.

The surrogate primary key is IGS_AD_IMP_STAT_PK, defined over the composite business-key candidate (INTERFACE_RUN_ID, ENTITY_NAME). The unique index IGS_AD_IMP_STAT_PK is the documented business-key candidate enforcing one statistics row per run-entity combination.

Common Use Cases and Queries

Typical use cases center on post-run verification, reconciliation, and reporting of admission import activity. Administrators query this table to confirm whether a load completed cleanly or to isolate entities producing errors. A representative query for a specific run is:

• SELECT entity_name, src_cat_code, total_rec_num, total_success_num, total_warn_num, total_error_num FROM igs_ad_imp_stats WHERE interface_run_id = :run_id ORDER BY entity_name;

Reporting queries frequently summarize success and error ratios across recent runs, or join the run context to concurrent program logs using REQUEST_ID. Another common pattern aggregates per-entity totals to detect chronic failure points:

• SELECT entity_name, SUM(total_success_num), SUM(total_error_num) FROM igs_ad_imp_stats GROUP BY entity_name;

Because audit and concurrent program columns are present, the table also supports trend analysis of import quality over time.

Related Objects

The mined relationship data classifies this table as standalone, so no foreign-key parents or children are documented. In practice, the following objects are contextually significant:

• Admission import interface tables in the IGS schema, keyed by the same interface run identifier that seeds INTERFACE_RUN_ID.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to correlate statistics with concurrent program runs.
• FND_CONCURRENT_PROGRAMS — referenced via PROGRAM_ID and PROGRAM_APPLICATION_ID.
• IGS_AD_IMP_STAT_PK — the primary key constraint and unique index governing row uniqueness.
• IGS admission import concurrent programs and their execution logs, which populate this table during each run.