Results for “duplicate_ind”

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

Overview

IGS_AS_MARK_SHEET_ALL is a transactional table within the Oracle E-Business Suite IGS — Student System module, which is documented as obsolete in the ETRM 12.1.1 and 12.2.2 reference sets. The table stores mark sheet definitions associated with a specified unit offering pattern. In functional terms, a mark sheet is the assessment instrument used to record and consolidate student results for a teaching unit delivered under a particular offering pattern, calendar type, and version. The table therefore acts as the parent record for individual assessment attempt rows captured against students.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is satellite-leaning. In Data Vault terms, a satellite records descriptive attributes that change over time and depend on a parent hub or link key. Here the natural hub is the unit offering pattern (IGS_PS_UNIT_OFR_PAT_ALL) and the sheet itself, while the attempt-level detail (IGS_AS_MSHT_SU_ATMPT) hangs beneath it. Modelers should treat SHEET_NUMBER as the stable surrogate key and the combination of unit, version, calendar type, and sequence as the descriptive context rather than as an independent business entity.

The metadata records "Not implemented in this database," meaning the table is present in the 12.1.1 ETRM physical schema definition (owner IGS, 21 documented columns) but is not deployed in the specific database instance referenced. Organizations still running legacy Student System assessment functionality may encounter it in upgraded or custom installations.

Key Information Stored

The primary key is IGS_AS_MARK_SHEET_ALL_PK, defined on SHEET_NUMBER. A unique index, IGS_AS_MARK_SHEET_ALL_U1, also exists on SHEET_NUMBER, confirming it as the business-key candidate and the single column used to identify a mark sheet row.

• SHEET_NUMBER — surrogate and business identifier for the mark sheet; the column referenced by dependent attempt rows.
• UNIT_CD, VERSION_NUMBER, CAL_TYPE, CI_SEQUENCE_NUMBER — the composite foreign key to IGS_PS_UNIT_OFR_PAT_ALL, tying the mark sheet to a precise unit offering pattern.
• GRADING_PERIOD_CD — the grading period in which the mark sheet applies.
• GROUP_SEQUENCE_NUMBER and LOCATION_CD — grouping and organizational context for the assessment.
• UNIT_MODE — the mode of unit delivery associated with the sheet.
• PRODUCTION_DT and DUPLICATE_IND — scheduling and duplication-control attributes.
• ORG_ID — multi-org operating unit discriminator.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — standard EBS audit and concurrent-program columns.

Common Use Cases and Queries

Typical reporting scenarios include identifying all mark sheets created for a unit offering pattern, reconciling attempt volumes per sheet, and auditing sheet creation by concurrent program. A representative join retrieves mark sheets alongside their offering pattern:

• SELECT m.SHEET_NUMBER, m.UNIT_CD, m.VERSION_NUMBER, m.CAL_TYPE, m.GRADING_PERIOD_CD FROM IGS_AS_MARK_SHEET_ALL m WHERE m.UNIT_CD = :unit_cd AND m.CAL_TYPE = :cal_type;
• SELECT m.SHEET_NUMBER, COUNT(a.SHEET_NUMBER) attempts FROM IGS_AS_MARK_SHEET_ALL m, IGS_AS_MSHT_SU_ATMPT a WHERE m.SHEET_NUMBER = a.SHEET_NUMBER GROUP BY m.SHEET_NUMBER;
• Operational checks on PRODUCTION_DT and DUPLICATE_IND to detect stale or duplicated sheet generation.
• Audit queries filtered on ORG_ID and REQUEST_ID to trace which process populated the sheet.

Related Objects

• IGS_PS_UNIT_OFR_PAT_ALL — referenced by IGS_AS_MARK_SHEET_ALL through UNIT_CD, VERSION_NUMBER, CAL_TYPE, and CI_SEQUENCE_NUMBER; the parent unit offering pattern definition.
• IGS_AS_MSHT_SU_ATMPT — child table referencing IGS_AS_MARK_SHEET_ALL.SHEET_NUMBER; holds student assessment attempt records captured against the sheet.
• IGS_AS_MARK_SHEET_ALL_PK and IGS_AS_MARK_SHEET_ALL_U1 — primary key constraint and unique index on SHEET_NUMBER, governing row identity and enabling FK lookups from attempt rows.

No additional dependents are documented in the ETRM excerpt; integration or reporting layers built in custom schemas may reference the sheet by SHEET_NUMBER and should be validated against the deployed instance.