Results for “igr_i_appl_all”

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

Overview

IGR_I_APPL_ALL is a legacy Oracle EBS table belonging to the IGS (Student System) product family, which has been classified as obsolete in Release 12.1.1 and 12.2.2. The table describes an enquiry application submitted to an educational institution. An enquiry in this context represents an expression of interest by a prospective student or party, which may be recorded at varying levels of granularity and for varying information types, such as accommodation information for a specific faculty of education.

Based on the heuristic Data Vault classification mined from the foreign key structure, this table is best modeled as a link. It connects independent entities — a party or person and an associated sales lead — through a transactional enquiry event, capturing the relationship between them rather than serving as a standalone hub or a descriptive satellite. This classification is a modeling suggestion derived from the FK topology, not a native Data Vault construct in EBS.

Per the ETRM documentation, the object is not implemented in the reference database, and its owner is IGS. The physical schema is documented with 50 columns, and the implementation status reflects that IGS functionality has been superseded by the Oracle Student System and related higher-education modules.

Key Information Stored

The table’s surrogate and business identifiers are central. The primary key IGR_I_APPL_PK is a composite of PERSON_ID and ENQUIRY_APPL_NUMBER, which together uniquely identify a single enquiry application per person. There is no separate single-column surrogate key; instead, the composite natural key functions as the unique index and business-key candidate.

• PERSON_ID — the person record associated with the enquiry, forming half of the composite primary key.
• ENQUIRY_APPL_NUMBER — the enquiry application number, the other half of the composite primary key.
• PARTY_ID — foreign key to HZ_PARTIES, linking the enquiry to a party record in the Trading Community Architecture.
• SALES_LEAD_ID — foreign key to AS_SALES_LEADS, connecting the enquiry to a sales lead.
• REGISTERING_PERSON_ID — the person who registered the enquiry.
• ENQUIRY_DT and LAST_PROCESS_DT — the date the enquiry was made and the last processing date.
• ACAD_CAL_TYPE and ACAD_CI_SEQUENCE_NUMBER — academic calendar context for the enquiry.
• ADM_CAL_TYPE and ADM_CI_SEQUENCE_NUMBER — admissions calendar context.
• INQ_ENTRY_LEVEL_ID and EDU_GOAL_ID — the enquiry entry level and educational goal.
• HOW_KNOWUS_ID and WHO_INFLUENCED_ID — sources of awareness and influencing parties.
• OVERRIDE_PROCESS_IND and PKG_REDUCT_IND — processing and package-reduction indicators.
• ORG_ID — the operating unit, enabling multi-org security in EBS.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–20 — the standard EBS descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Historical reporting on enquiry pipelines, lead-to-enquiry conversion, and recruitment analysis are the primary uses. A typical query joins the table to HZ_PARTIES and AS_SALES_LEADS to reconcile enquiry volume against marketing leads. A sample pattern:

• Enquiries per party: SELECT PERSON_ID, ENQUIRY_APPL_NUMBER, ENQUIRY_DT FROM IGR_I_APPL_ALL WHERE PERSON_ID = :p;
• Join to party: SELECT a.PERSON_ID, a.ENQUIRY_APPL_NUMBER, p.PARTY_NAME FROM IGR_I_APPL_ALL a, HZ_PARTIES p WHERE a.PARTY_ID = p.PARTY_ID;
• Join to sales leads: SELECT a.ENQUIRY_APPL_NUMBER, s.LEAD_ID FROM IGR_I_APPL_ALL a, AS_SALES_LEADS s WHERE a.SALES_LEAD_ID = s.LEAD_ID;
• Org-scoped reporting: filter by ORG_ID to respect operating unit security.

Related Objects

• HZ_PARTIES — referenced via IGR_I_APPL_ALL.PARTY_ID; the TCA party master.
• AS_SALES_LEADS — referenced via IGR_I_APPL_ALL.SALES_LEAD_ID; the sales lead source.
• IGR_I_APPL_PK — the composite primary key / unique index (PERSON_ID, ENQUIRY_APPL_NUMBER).
• HZ_PERSON_PROFILES — related person detail for PERSON_ID and REGISTERING_PERSON_ID.
• AS_SALES_LEAD_LINES — lead line detail where SALES_LEAD_ID is used.
• IGS product views/APIs — legacy IGS enquiry packages that historically consumed this table.