Results for “preced_ca_sequence_number”

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

Overview

IGS_PR_MILESTONE_V is a validation view owned by the APPS schema within the IGS (Student System) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes progression milestone data drawn from the IGS_PR_MILESTONE base table, providing a read-only, presentation-layer projection of milestone records for reporting, notification processing, and integration with downstream student progression logic. The view materialises one row per milestone event tied to a person and to a customer account sequence number, joining milestone definitions to their due dates, achieved dates, and override notification parameters.

Underlying Base Objects

Per the ETRM metadata, IGS_PR_MILESTONE_V has no separately documented referenced base objects; however, its view text is a direct projection over the single table IGS_PR_MILESTONE, aliased as MIL. The SELECT list does not join to any additional table, and no WHERE clause filters rows, so the view returns every row from the base table, supplemented by two literal expressions:

• INCLUDE_REACHED_MILESTONES is hard-coded to the literal 'N', indicating the view is intended to exclude already-reached milestones from notification consideration by default.
• PRECED_PERSON_ID and PRECED_CA_SEQUENCE_NUMBER are emitted using NVL(…, NULL) expressions, preserving the underlying values while normalising null handling.

Because the view is a straight projection, it inherits all column-level semantics, data types, and constraints from IGS_PR_MILESTONE, and any DML against the base table is immediately reflected in query results.

Key Columns

• PERSON_ID – identifies the person (student or applicant) to whom the milestone applies.
• CA_SEQUENCE_NUMBER, SEQUENCE_NUMBER – surrogate and ordinal identifiers for the milestone instance.
• MILESTONE_TYPE, MILESTONE_STATUS – classification and current state of the milestone.
• DUE_DT, ACTUAL_REACHED_DT – scheduled and actual completion dates.
• OVRD_NTFCTN_IMMINENT_DAYS, OVRD_NTFCTN_REMINDER_DAYS, OVRD_NTFCTN_RE_REMINDER_DAYS – override values controlling the imminent-notification window, the initial reminder window, and the re-reminder window respectively. These are the columns referenced by the search term ovrd_ntfctn_imminent_days and drive notification scheduling when the standard defaults on the milestone definition are superseded.
• PRECED_* columns – identify a preceding person/milestone sequence, supporting chained or dependent milestones.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard WHO columns for auditability.
• DESCRIPTION, COMMENTS – free-text context.

Common Use Cases and Queries

Typical usage includes identifying milestones approaching their due date so that notification jobs can be triggered, auditing override settings, and feeding progression analytics.

• List imminent milestones for a person:

  SELECT person_id, milestone_type, due_dt, ovrd_ntfctn_imminent_days
  FROM   apps.igs_pr_milestone_v
  WHERE  person_id = :p_person_id
  AND    milestone_status = 'INCOMPLETE';

• Find milestones with an overtightened imminent window:

  SELECT * FROM apps.igs_pr_milestone_v
  WHERE  ovrd_ntfctn_imminent_days < 7;

• Report due milestones over the next 30 days.

Because the view is a single-table projection, it is safe for read-only integration and BI Publisher reporting, but not for direct DML.