Search Results or_org_type




Overview
Explore in AI Chat

Overview

IGS_OR_UNIT_V is a seeded Oracle E-Business Suite view owned by the APPS schema and defined in the Oracle Student System (formerly Oracle HRMS/Student Information) product family. The object name follows the institutional "IGS" naming convention used across the Student System (IGS) schema, and represents a reporting and integration layer over organization unit data associated with TCA parties. Its primary purpose is to consolidate information about organizational units — their status, type, member type, and preferred external identifiers — into a single queryable structure that joins the institution's student-system party extensions, TCA party records, status lookups, and alternate identifier data.

The view is commonly referenced by reports, concurrent programs, and custom extensions that need a denormalized, human-readable rendering of organizational units. Because it exposes both coded values (for example OU_ORG_TYPE) and their corresponding lookup meanings (for example TYPE_DESC), it is well suited for both data extraction and integration interfaces where descriptive text is required.

Underlying Base Objects

The view text documents the following base objects:

  • HZ_PARTIES (HP) — the TCA party master record, supplying party identity, party number, and descriptive attributes.
  • IGS_PE_HZ_PARTIES (IHP) — the institution's party extension table, carrying organizational-unit-specific attributes such as OU_ORG_TYPE, OU_ORG_STATUS, OU_MEMBER_TYPE, and institution code.
  • IGS_OR_STATUS (OS) — the organization status definition, joined on OU_ORG_STATUS to resolve a descriptive status.
  • IGS_LOOKUP_VALUES (OT) — lookup values with LOOKUP_TYPE = 'OR_ORG_TYPE', resolving OU_ORG_TYPE to a meaning (TYPE_DESC). This is the direct basis for the user's search term or_org_type.
  • IGS_LOOKUP_VALUES (MT) — lookup values with LOOKUP_TYPE = 'OR_MEMBER_TYPE', resolving OU_MEMBER_TYPE to a meaning (MEMBER_DESC).
  • IGS_OR_ORG_ALT_IDS / IGS_OR_ORG_ALT_IDTYP (pid subquery) — a dated subquery returning the preferred (PREF_UNIT_IND = 'Y') alternate identifier for the organization structure, honoring the valid date range.

No additional base objects are documented in the ETRM metadata; the joins above constitute the complete documented dependency set.

Key Columns

  • ROW_ID — the ROWID of the IGS_PE_HZ_PARTIES record, useful for direct updates or identifying the source row.
  • PARTY_ID / TCA_PARTY_NUMBER / DESCRIPTION — TCA party identity and name.
  • ORG_UNIT_CD — the organization structure code (OSS_ORG_UNIT_CD); this is the key joining to the preferred alternate identifier subquery.
  • OU_START_DT / OU_END_DT — validity dates for the organizational unit.
  • OU_ORG_STATUS / OS.DESCRIPTION — status code and its description.
  • OU_ORG_TYPE / TYPE_DESC — the organization type code and its lookup meaning from OR_ORG_TYPE. This pairing is the defining column family for the searched term.
  • OU_MEMBER_TYPE / MEMBER_DESC — member type code and lookup meaning from OR_MEMBER_TYPE.
  • INSTITUTION_CD — institution context for multi-institution deployments.
  • PREF_UNIT_ID_TYPE / PREF_UNIT_ALT_ID — the preferred alternate identifier type and value for the unit.
  • ATTRIBUTE1 through ATTRIBUTE20, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — descriptive flexfield and audit columns propagated from HZ_PARTIES.

Common Use Cases and Queries

Typical uses include retrieving all active organizational units of a given type, resolving type codes to descriptions for reports, and exporting organization unit data with preferred identifiers for integrations.

SELECT party_id, tca_party_number, org_unit_cd, description,
       OU_ORG_TYPE, TYPE_DESC, OU_ORG_STATUS, PREF_UNIT_ALT_ID
  FROM apps.igs_or_unit_v
 WHERE OU_ORG_TYPE = 'ACADEMIC';

Filtering by valid period and institution is also common:

SELECT org_unit_cd, description, type_desc, ou_start_dt, ou_end_dt
  FROM apps.igs_or_unit_v
 WHERE institution_cd = :p_institution
   AND SYSDATE BETWEEN ou_start_dt AND NVL(ou_end_dt, SYSDATE);

Because the view exposes both coded and descriptive fields, and includes a resolved preferred identifier, it remains a convenient single source for organization-unit reporting and downstream integration workloads within Oracle EBS 12.1.1 and 12.2.2.