Results for “igs_or_inst_org_base_v”

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

Overview

IGS_OR_INST_ORG_BASE_V is a seeded Oracle E-Business Suite database view owned by the APPS schema and delivered as part of the IGS (Student System) product family. Its documented purpose is to serve as a base view holding basic institution and organization-related information. In Oracle EBS 12.1.1 and 12.2.2, the view acts as a simplified, reusable presentation layer over the Oracle Trading Community Architecture (TCA) party model, exposing only those parties that have been flagged as institutions or organizations. Because it consolidates party identity, organization unit attributes, and higher-education institution attributes into a single row per organization, it is commonly used as a foundation for reporting extracts, integration interfaces, and downstream IGS views rather than being populated by user transactions directly.

Underlying Base Objects

The view text joins two documented base objects: HZ_PARTIES and IGS_PE_HZ_PARTIES. The join condition is on PARTY_ID, and the filter restricts the result set to parties whose HZ_PARTIES.STATUS equals 'A' (active) and whose IGS_PE_HZ_PARTIES.INST_ORG_IND is not null. The IGS_PE_HZ_PARTIES table is the IGS extension of the TCA party record and stores organization-unit and institution-specific attributes. Because the query drives institution and organization semantics from INST_ORG_IND, the view effectively returns only parties that participate in the institutional or organizational relationship model. Note that the ETRM metadata lists no additional documented base objects, and the core dependency is limited to these two tables.

Key Columns

The view aliases several columns to distinguish contexts. ROW_ID is the HZ_PARTIES row identifier. PARTY_ID is the primary party key. TCA_PARTY_NUMBER carries HZ_PARTIES.PARTY_NUMBER, while PARTY_NUMBER is re-mapped from IGS_PE_HZ_PARTIES.OSS_ORG_UNIT_CD, the organization unit code. PARTY_NAME holds the party name. START_DATE and END_DATE derive from OU_START_DT and OU_END_DT and bound the validity of the organization unit record.

• INST_ORG_IND — identifies whether the party is an institution or an organization; this is the column typically sought when users search for "inst_org_ind" and is the discriminator that the view requires to be non-null.
• INSTITUTION_STATUS — from OI_INSTITUTION_STATUS, indicating the institution's lifecycle status.
• ORG_STATUS — from OU_ORG_STATUS, the organization unit status.
• OU_INSTITUTION_CD — the institution code mapped from INSTITUTION_CD.
• OI_LOCAL_INSTITUTION_IND, OI_GOVT_INSTITUTION_CD, OI_INST_CONTROL_TYPE, OI_INSTITUTION_TYPE — classification attributes describing local versus external institutions, government codes, control type, and institution type.
• OU_MEMBER_TYPE and OU_ORG_TYPE — organization membership and organization type attributes.

Common Use Cases and Queries

This view is typically used to list active institutions and organizations, to feed validation lists in institution enrollment or organization setup, and to join institution identifiers to other IGS entities such as programs, offerings, or admissions records. A representative query filtering by the often-searched discriminator column is:

• SELECT party_id, party_number, party_name, inst_org_ind, institution_status, ou_institution_cd FROM igs_or_inst_org_base_v WHERE inst_org_ind = 'I';
• SELECT ou_institution_cd, party_name, start_date, end_date FROM igs_or_inst_org_base_v WHERE inst_org_ind IS NOT NULL AND org_status = 'A';

Because the view enforces STATUS = 'A' and INST_ORG_IND IS NOT NULL internally, queries cannot retrieve inactive parties or non-institutional organizations through it. Consumers requiring historical or inactive records must query the base tables directly.