Search Results group_sequence_number

Overview

IGS_AS_MARK_SHEET is a multitenant security (MLS) view in the Oracle E-Business Suite Student System (IGS) product family. It is owned by the APPS schema and holds a VALID status in the EBS 12.1.1 and 12.2.2 data dictionaries. The view exposes assessment mark sheet records—the header-level data structures used to produce unit and grading period mark sheets for students—and forms the query layer over the underlying table IGS_AS_MARK_SHEET_ALL, applying an operating unit (ORG_ID) filter driven by the session's CLIENT_INFO.

The "ivms google sheet" search term that surfaces this object reflects a common practical pattern: institutions maintain the equivalent of Google Sheets externally for tracking marks, and IGS_AS_MARK_SHEET is the EBS system-of-record view that BI Publisher, OBIEE, and custom concurrent programs query to reconcile or export that data. Reporting tools and interfaces should select from this view rather than the _ALL table so that operating unit security is enforced automatically.

Underlying Base Objects

Despite the ETRM "no base objects documented" entry, the view definition clearly references a single base object: IGS_AS_MARK_SHEET_ALL (aliased as TAB). The view is a thin wrapper that:

• Projects all business columns plus TAB.ROWID as ROW_ID.
• Filters rows by ORG_ID using USERENV('CLIENT_INFO'), an MLS pattern (NVL(ORG_ID, NVL(...USERENV...)) = NVL(...USERENV...)) that restricts the result set to the caller's currently set operating unit. When CLIENT_INFO is empty, the filter resolves to -99, matching unassigned rows.

Because it is a non-key-preserved view over a single table with the MLS predicate, DML should generally be performed against IGS_AS_MARK_SHEET_ALL using the standard ORG_ID handling; the view itself is intended for read-only reporting.

Key Columns

• SHEET_NUMBER — identifier of the mark sheet, the primary business key together with the unit context.
• UNIT_CD, VERSION_NUMBER, CAL_TYPE, CI_SEQUENCE_NUMBER, LOCATION_CD, UNIT_MODE — identify the unit version and calendar instance the mark sheet belongs to.
• GROUP_SEQUENCE_NUMBER — sequence of the student group associated with the sheet.
• GRADING_PERIOD_CD — the grading period within the teaching calendar.
• PRODUCTION_DT and DUPLICATE_IND — when the sheet was produced and whether it is a duplicate run.
• ORG_ID — operating unit; enforces MLS partitioning.
• Standard WHO and request columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.
• ROW_ID — ROWID of the underlying table row, exposed for uniqueness and row identification.

Common Use Cases and Queries

Typical uses include mark sheet reconciliation, BI Publisher report data sources, and interfaces exporting assessment records.

• Listing mark sheets for the current operating unit:

  SELECT sheet_number, unit_cd, version_number, cal_type,
         grading_period_cd, production_dt, duplicate_ind
  FROM   apps.igs_as_mark_sheet
  ORDER  BY production_dt DESC;

• Locating duplicates:

  SELECT sheet_number, unit_cd, grading_period_cd
  FROM   apps.igs_as_mark_sheet
  WHERE  duplicate_ind = 'Y';

• Tracing the concurrent program that produced a sheet:

  SELECT sheet_number, request_id, program_id, program_update_date
  FROM   apps.igs_as_mark_sheet
  WHERE  request_id IS NOT NULL;

In all cases, ensure the session operating unit (CLIENT_INFO) is initialized—typically via FND_CLIENT_INFO—before querying, otherwise the ORG_ID predicate defaults to -99 and no rows are returned.