Search Results total_warn_num

Overview

IGS.IGS_AD_IMP_STATS is a statistical tracking table within the Oracle E-Business Suite Advanced Planning and Admissions Import process, owned by the IGS schema. It stores per-run, per-entity processing statistics generated during each execution of the Admission Import concurrent program. Each row captures how many records belonging to a specific source category and interface entity were selected, successfully processed, flagged with warnings, or failed with errors during a single import run.

The table resides in the APPS_TS_INTERFACE tablespace, confirming its role as an interface-run metadata store rather than a transactional admissions table. It is populated by the import process itself and queried primarily for reconciliation, error diagnosis, and run-history reporting. It contains 16 documented columns — six business statistics columns plus the standard WHO audit columns and concurrent program (REQUEST_ID, PROGRAM_ID) columns.

Based on the mined relationship data, the object is classified heuristically as a standalone model with no foreign-key links to parent structures. In Data Vault terms, this suggests modeling it as a satellite-like statistics fact attached to an import-run hub identified by INTERFACE_RUN_ID, with SRC_CAT_CODE and ENTITY_NAME acting as business descriptors rather than relational parents.

Key Information Stored

• INTERFACE_RUN_ID — Admission Import Process instance identifier; uniquely identifies a single run and forms the first component of the composite primary key.
• ENTITY_NAME — Interface entity name for the source category (e.g., the staging entity being processed); second component of the composite key.
• SRC_CAT_CODE — Source Category Code included in the run; the value the user searched on, used to scope statistics to a particular admission source category (VARCHAR2 30).
• TOTAL_REC_NUM — Total records queued for processing (Status='2') in the entity for that run.
• TOTAL_SUCCESS_NUM — Records successfully processed.
• TOTAL_WARN_NUM — Records that completed with warnings (Status='4').
• TOTAL_ERROR_NUM — Records that failed with errors (Status='3').
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program WHO columns linking the statistics to the specific request that produced them.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

The surrogate/business key is the unique index IGS_AD_IMP_STAT_PK on (INTERFACE_RUN_ID, ENTITY_NAME). Note that SRC_CAT_CODE is a descriptive attribute rather than a key component; a single run and entity combination yields one statistics row regardless of source category detail.

Common Use Cases and Queries

Typical reporting retrieves the outcome of a specific import run or aggregates success/error ratios across runs for a source category. For example, to reconcile a run:

SELECT src_cat_code, entity_name,
       total_rec_num, total_success_num,
       total_warn_num, total_error_num
FROM   igs.igs_ad_imp_stats
WHERE  interface_run_id = :run_id;

To trace a source category historically via the concurrent request:

SELECT s.interface_run_id, s.entity_name,
       s.total_rec_num, s.total_error_num,
       s.request_id, s.creation_date
FROM   igs.igs_ad_imp_stats s
WHERE  s.src_cat_code = :src_cat_code
ORDER  BY s.creation_date DESC;

Common scenarios include post-import reconciliation (verifying total_rec_num equals success + warn + error), identifying entities with high error counts, and auditing which concurrent request produced a given statistics row through REQUEST_ID.

Related Objects

• IGS_AD_IMP_STAT_PK — the unique index backing the composite primary key; joins are typically made on INTERFACE_RUN_ID + ENTITY_NAME.
• Admission interface staging tables keyed by INTERFACE_RUN_ID and SRC_CAT_CODE — the source entities summarized by TOTAL_REC_NUM, TOTAL_WARN_NUM, TOTAL_SUCCESS_NUM, and TOTAL_ERROR_NUM.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to identify the concurrent program run that generated the statistics.
• FND_CONCURRENT_PROGRAMS — joined via PROGRAM_ID / PROGRAM_APPLICATION_ID to resolve the import program definition.

Because the documented model is standalone, no foreign-key relationships constrain REPORTING against other IGS tables; joins are value-based via INTERFACE_RUN_ID and SRC_CAT_CODE.