Search Results ent_org_unit_id




Overview
Explore in AI Chat

Overview

The IGS.IGR_I_E_ORGUNITS table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Institutional Grants and Research (IGS) module. Its primary function is to manage the relationship between organizational units and inquiry types, serving as a configuration table that defines which departments or units within an institution are responsible for handling specific types of prospective student or applicant inquiries. This table acts as a critical junction, linking the master list of organizational units (parties) to the defined inquiry types, thereby enabling targeted inquiry routing and management within the admissions and recruitment processes.

Key Information Stored

The table stores configuration records that map organizational units to inquiry types. Key columns include:

  • ENT_ORG_UNIT_ID: The primary key and unique identifier for each record in this table.
  • PARTY_ID: A foreign key referencing HZ_PARTIES, uniquely identifying the organizational unit (e.g., Admissions Office, Biology Department).
  • INQUIRY_TYPE_ID: A foreign key identifying the specific type of inquiry (e.g., Undergraduate, Graduate, International). This column, combined with PARTY_ID, forms a unique constraint (IGR_I_E_ORGUNITS_UK).
  • CLOSED_IND: A flag indicating whether the organizational unit's association with the inquiry type is active ('N') or closed/inactive ('Y').
  • INQ_ENTRY_STAT_ID: Documented as obsolete; its functional purpose in current implementations is deprecated.
  • Standard WHO Columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN): For auditing and tracking record creation and modifications.

Common Use Cases and Queries

This table is central to operational and reporting tasks in student recruitment. A common use case is determining the responsible department for a new inquiry based on its type, which is essential for workflow automation. Administrators may query the table to audit or modify these assignments. For reporting, it is frequently joined with party and inquiry type descriptions to generate lists of active unit-type mappings.

Sample SQL to retrieve all active organizational unit assignments for a given inquiry type: 

SELECT hou.name org_unit_name,
       iu.party_id,
       iu.ent_org_unit_id
FROM   igr_i_e_orgunits iu,
       hz_parties hp,
       hr_organization_units hou
WHERE  iu.inquiry_type_id = :p_inquiry_type_id
AND    iu.closed_ind = 'N'
AND    hp.party_id = iu.party_id
AND    hou.organization_id = hp.party_id;
Another critical query involves validating the unique constraint before inserting a new assignment, checking for existing PARTY_ID and INQUIRY_TYPE_ID combinations.

Related Objects

The IGR_I_E_ORGUNITS table maintains defined relationships with other key EBS entities, primarily through foreign key constraints:

  • Primary Key: IGR_I_E_ORGUNITS_PK on ENT_ORG_UNIT_ID.
  • Foreign Key (Reference): The PARTY_ID column references HZ_PARTIES.PARTY_ID, linking to the Trading Community Architecture's master list of parties and organizations.
  • Foreign Key (Reference): The INQUIRY_TYPE_ID column references a corresponding inquiry type master table (specific table name inferred from metadata pattern), defining the category of inquiry.
  • Unique Key: IGR_I_E_ORGUNITS_UK on the combination of INQUIRY_TYPE_ID and PARTY_ID, enforcing business logic that an organizational unit can be assigned to a specific inquiry type only once.
The table is referenced by other application objects within the IGS module, as indicated by its listing under dependencies, though specific object names are not detailed in the provided excerpt.