Results for “igs_sv_btch_summary”

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

Overview

The IGS_SV_BTCH_SUMMARY table resides in the IGS schema (IGS - Student System) within Oracle E-Business Suite 12.1.1 and 12.2.2. As its description states, it stores details about the information being included in each batch processed. It functions as a transactional detail table that records, for a given batch, the individual entities affected and the nature of the action applied to them. In practical terms, it links a processing batch to the person records selected for that batch, capturing the action to be performed and any associated administrative codes.

Based on the mined foreign-key structure, the heuristic Data Vault classification for this object is link. This classification is offered as a modeling suggestion rather than a declared property: the table resolves a many-to-many style relationship between batches and persons, and its grain is the intersection of those two dimensions plus the action context. It is not a descriptive satellite, because it primarily holds relationship and action references rather than a wide set of changing descriptive attributes, though it does carry audit columns.

Key Information Stored

The documented physical schema contains 13 columns. The most significant are:

• SUMMARY_ID — the surrogate primary key, enforced by the IGS_SV_BTCH_SUMMARY_PK unique index. It uniquely identifies each summary row and is the column most commonly referenced when the user searches on "summary_id".
• BATCH_ID — foreign key to IGS_SV_BATCHES, identifying the processing batch to which the summary record belongs.
• PERSON_ID — foreign key to IGS_PE_HZ_PARTIES, identifying the party (person) to whom the summarized action applies.
• ACTION_CODE — the action performed or to be performed for the batch/person combination.
• TAG_CODE — a code used to tag the summary record, typically for categorization or filtering within the batch process.
• ADM_ACTION_CODE — the admissions-related action code associated with the record, supporting admissions workflows.
• OWNER_TABLE_NAME and OWNER_TABLE_IDENTIFIER — identify the source entity that generated or owns the summary entry, enabling polymorphic linkage back to the originating record.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the row and when.

The only documented unique index is IGS_SV_BTCH_SUMMARY_PK on SUMMARY_ID; no separate business-key unique index is documented, so the surrogate key is the sole guaranteed uniqueness constraint.

Common Use Cases and Queries

Typical uses include batch reconciliation, auditing which persons were processed in a batch, and reporting on action codes applied per person. A common query retrieves all summary rows for a specific batch, joined to the batch header:

• SELECT s.summary_id, s.person_id, s.action_code, s.tag_code FROM igs.igs_sv_btch_summary s WHERE s.batch_id = :batch_id;
• Joining to the party table to resolve names: SELECT s.summary_id, p.party_name, s.action_code FROM igs.igs_sv_btch_summary s, igs.igs_pe_hz_parties p WHERE s.person_id = p.party_id AND s.batch_id = :batch_id;
• Filtering by admission action for admissions reporting: SELECT * FROM igs.igs_sv_btch_summary WHERE adm_action_code = :adm_action;
• Auditing recent activity: SELECT * FROM igs.igs_sv_btch_summary WHERE last_update_date > SYSDATE - 7;

Related Objects

• IGS_SV_BATCHES — parent batch table; joined via IGS_SV_BTCH_SUMMARY.BATCH_ID.
• IGS_PE_HZ_PARTIES — party/person table; joined via IGS_SV_BTCH_SUMMARY.PERSON_ID.
• IGS_SV_BTCH_SUMMARY_PK — the primary key constraint and unique index on SUMMARY_ID.
• Batch processing packages and concurrent programs in the IGS Student System that populate and read this summary during batch runs.
• Reporting views built over the IGS Student System that surface batch and person-level processing detail.