Results for “igs_pe_mil_services”

27 results




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

Overview

The view IGS_PE_MIL_SERVICES belongs to the IGS – Student System product family within Oracle E-Business Suite. The IGS modules (Intelligent Grants/Student System components) were developed to support higher-education and grants-oriented student data management, including admissions, registration, records, and related person-extension data. The ETRM metadata for this object carries the designation Obsolete, and the documented implementation note states that the view is not implemented in this database at the release level documented (12.1.1 / 12.2.2).

Functionally, IGS_PE_MIL_SERVICES presents military service information for persons (students, applicants, or staff) tracked in the IGS person-extension model. It exposes a flat, reporting-friendly projection of military service records, including service type, service period, separation classification, and financial-assistance tracking. As a view, it is intended for read-only consumption by reports, concurrent programs, and integration interfaces rather than for direct data entry.

Underlying Base Objects

The documented ETRM metadata lists no referenced base objects (owner and referenced objects are blank), which is consistent with the "obsolete / not implemented" classification. The view text itself, however, is fully documented and reveals a single source: IGS_PE_MIL_SERVICES_ALL, aliased as TAB. The view is therefore a thin, virtually one-to-one projection over that base table.

The _ALL naming convention in Oracle EBS indicates a multi-org (operating unit) table partitioned by ORG_ID. This is corroborated by the presence of ORG_ID among the projected columns and by the use of TAB.ROWID as the synthesized ROW_ID. Because the view selects all columns explicitly and defines no WHERE clause, no row filtering or row-level security is applied at the view layer; any operating-unit restriction must be enforced by the calling application or report.

Key Columns

  • ROW_ID — The physical ROWID of the underlying row, used by Oracle Forms and generic EBS frameworks to uniquely address records.
  • ORG_ID — Operating unit identifier, supporting multi-org data segregation.
  • MILIT_SERVICE_ID — Primary key of the military service record.
  • PERSON_ID — Foreign key to the person (student/applicant) to whom the military service pertains; links to the IGS person tables.
  • MILITARY_TYPE_CD — Coded value describing the type/branch of military service.
  • START_DATE / END_DATE — The period during which the service was performed.
  • SEPARATION_TYPE_CD — Classification of how/why service ended.
  • ASSISTANCE_TYPE_CD / ASSISTANCE_STATUS_CD — Type and current status of any military-related financial assistance associated with the record.
  • Who-columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN provide standard EBS audit tracking.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — The standard EBS descriptive flexfield (DFF) columns, allowing customer-specific extensions without schema change.

Common Use Cases and Queries

Because the object is obsolete and, per the ETRM record, not implemented in the database, most practical usage consists of reference inspection or legacy migration analysis. Where the underlying IGS_PE_MIL_SERVICES_ALL table exists in an earlier or customized instance, typical patterns include:

  • Retrieving all military service records for a given person.
  • Reporting active versus separated service within a date range.
  • Extracting assistance-status data for financial aid reconciliation.
  • Reading DFF attribute values for institution-specific reporting.
SELECT person_id, military_type_cd, start_date, end_date,
       separation_type_cd, assistance_status_cd
  FROM igs_pe_mil_services
 WHERE person_id = :p_person_id
   AND org_id    = :p_org_id
 ORDER BY start_date;
SELECT org_id, assistance_status_cd, COUNT(*)
  FROM igs_pe_mil_services
 WHERE start_date >= :p_from_date
 GROUP BY org_id, assistance_status_cd;

Consultants migrating to 12.2.2 should confirm object existence in their specific environment, as the ETRM metadata explicitly documents the view as not implemented at this release.