Search Results igs_pr_milestone




Overview
Explore in AI Chat

Overview

IGS_PR_MILESTONE is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, belonging to the IGS (Student System) product family. It exposes prospect milestone data — the discrete progression checkpoints that an admissions or recruitment prospect passes through — in a multi-organization–aware, row-level-secured form. The view is defined over the IGS_PR_MILESTONE_ALL base table and is designed to return only those milestone rows that belong to the organization currently set in the user's session, as determined by the ORG_ID stored in the FND CLIENT_INFO environment value.

Because the view encapsulates organization security, it is the preferred access point for concurrent programs, OAF/Forms pages, reports, and outbound interfaces that need to query prospect milestones without re-implementing the org filter logic. It is available in both Oracle EBS 12.1.1 and 12.2.2; the object is documented as VALID in the ETRM metadata for the 12.2.2 release.

Underlying Base Objects

The view is defined solely over the table IGS_PR_MILESTONE_ALL, aliased as TAB. The ETRM metadata records no other referenced base objects, so all columns exposed are either direct projections of base-table columns or the synthetic ROW_ID column, which is derived from TAB.ROWID. There are no joins, unions, or lookup tables involved.

The WHERE clause applies the multi-org predicate: the row's ORG_ID is compared against the organization identifier decoded from the first ten characters of USERENV('CLIENT_INFO'). A leading blank character is treated as NULL, and both sides default to -99 when no organization context is present. This pattern is the standard Oracle multi-organization view convention, ensuring that queries against IGS_PR_MILESTONE return only records valid for the operating unit or organization under which the session is running.

Key Columns

  • ROW_ID — Synthetic row identifier derived from the base table ROWID; useful for uniquely addressing a milestone row in the current organization context.
  • PERSON_ID — Party/person identifier of the prospect or applicant to whom the milestone belongs.
  • CA_SEQUENCE_NUMBER — Sequence number of the related contact/application activity to which the milestone is attached.
  • SEQUENCE_NUMBER — Ordinal position of the milestone within the prospect's milestone track.
  • MILESTONE_TYPE — Code classifying the milestone (for example, an inquiry, application, or admission checkpoint).
  • MILESTONE_STATUS — Current status of the milestone (reached, pending, overdue, and so on).
  • DUE_DT / ACTUAL_REACHED_DT — Target date for the milestone and the date it was actually completed.
  • PRECED_SEQUENCE_NUMBER — The sequence number of the predecessor milestone, enabling ordered traversal of the milestone chain.
  • DESCRIPTION / COMMENTS — Free-text description and user comments.
  • OVRD_NTFCTN_IMMINENT_DAYS, OVRD_NTFCTN_REMINDER_DAYS, OVRD_NTFCTN_RE_REMINDER_DAYS — Override notification lead times for imminent, reminder, and re-reminder alerts.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.
  • ORG_ID — Organization (operating unit) owning the milestone record; also the driving column of the view's security predicate.

Common Use Cases and Queries

Typical scenarios include prospect pipeline reporting, milestone aging and overdue analysis, notification-generation jobs that must observe organization security, and integrations feeding CRM or data-warehouse extracts. Because the view is org-secured, callers must initialize the organization context before querying.

List all milestones for a prospect:

  • SELECT person_id, sequence_number, milestone_type, milestone_status, due_dt, actual_reached_dt FROM igs_pr_milestone WHERE person_id = :p_person_id ORDER BY sequence_number;

Identify overdue milestones in the current organization:

  • SELECT person_id, ca_sequence_number, sequence_number, milestone_type, due_dt FROM igs_pr_milestone WHERE milestone_status = :p_pending_status AND due_dt < SYSDATE ORDER BY due_dt;

Count milestones by type for pipeline metrics:

  • SELECT milestone_type, milestone_status, COUNT(*) FROM igs_pr_milestone GROUP BY milestone_type, milestone_status;

Where organization-level access is intentionally bypassed, applications query IGS_PR_MILESTONE_ALL directly; all secured reads should use the view.