Search Results actual_reached_dt




Overview
Explore in AI Chat

Overview

APPS.IGS_PR_MILESTONE_V is a reporting and integration view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. It belongs to the Oracle Student System / Student Records (IGS) product family, specifically the Progression (PR) module that tracks academic milestones for learners. The view exposes milestone records together with a set of synthesized columns that are not stored directly on the underlying table, most notably the INCLUDE_REACHED_MILESTONES flag, the PRECED_PERSON_ID and PRECED_CA_SEQUENCE_NUMBER columns, and the notification override columns including OVRD_NTFCTN_RE_REMINDER_DAYS. Its primary role is to provide a stable, read-only projection of milestone data for use in forms, concurrent programs, BI Publisher reports, and inbound/outbound integrations without requiring consumers to reference the base table directly.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: IGS_PR_MILESTONE (aliased as MIL in the view definition). No additional base tables, synonyms, or join dependencies are documented. The view is a straightforward, single-table projection rather than a join, meaning that all persisted columns — including PERSON_ID, CA_SEQUENCE_NUMBER, SEQUENCE_NUMBER, MILESTONE_TYPE, MILESTONE_STATUS, DUE_DT, ACTUAL_REACHED_DT, the notification override columns, and the standard WHO audit columns — are carried directly from IGS_PR_MILESTONE. The remaining columns are derived literals or functions applied at query time.

Key Columns

  • PERSON_ID and CA_SEQUENCE_NUMBER — identify the learner (party/person) and the course attempt context to which the milestone belongs.
  • SEQUENCE_NUMBER, MILESTONE_TYPE, MILESTONE_STATUS — the milestone identifier, its classification, and its current lifecycle status.
  • DUE_DT and ACTUAL_REACHED_DT — the scheduled due date and the date the milestone was actually attained.
  • INCLUDE_REACHED_MILESTONES — a hard-coded literal 'N', used by consuming logic to filter out already-reached milestones when the calling program requests only outstanding items.
  • PRECED_PERSON_ID and PRECED_CA_SEQUENCE_NUMBER — defined as NVL(PERSON_ID, NULL) and NVL(CA_SEQUENCE_NUMBER, NULL) respectively; these simplify the expression to the same value as the source column but provide a named alias for precedent-milestone joins in downstream queries.
  • PRECED_SEQUENCE_NUMBER — the sequence number of the preceding milestone in the chain.
  • OVRD_NTFCTN_IMMINENT_DAYS, OVRD_NTFCTN_REMINDER_DAYS, and OVRD_NTFCTN_RE_REMINDER_DAYS — notification override thresholds. OVRD_NTFCTN_RE_REMINDER_DAYS specifically controls the number of days used for the repeat (re-reminder) notification window when a milestone remains outstanding after the initial reminder. These overrides supersede the default notification lead times configured at the milestone-type level.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, COMMENTS — standard audit and free-text columns.

Common Use Cases and Queries

The view is typically queried to drive milestone notification concurrent programs, learner self-service pages, and progression reports. A frequent scenario is retrieving all outstanding milestones for a person together with their notification override windows:

  • Milestone notification scheduling — selecting OVRD_NTFCTN_RE_REMINDER_DAYS alongside DUE_DT to determine when repeat reminders should fire.
  • Progression tracking reports — joining back to person and course attempt tables using PERSON_ID and CA_SEQUENCE_NUMBER.
  • Integration extracts — feeding milestone status and override days into external student systems.
SELECT person_id,
       ca_sequence_number,
       sequence_number,
       milestone_type,
       milestone_status,
       due_dt,
       ovrd_ntfctn_imminent_days,
       ovrd_ntfctn_reminder_days,
       ovrd_ntfctn_re_reminder_days
  FROM apps.igs_pr_milestone_v
 WHERE person_id = :p_person_id
   AND milestone_status = 'OUTSTANDING'
   AND include_reached_milestones = 'N';

Because the view is defined only over IGS_PR_MILESTONE, it is lightweight and safe for direct querying; however, consumers should treat it as read-only and apply the appropriate APPS schema grants when accessed through custom code.