Search Results interface_lines_id

Overview

IGR_I_LINES_INT is an interface (staging) table owned by the IGS schema within the Oracle E-Business Suite Student System (IGS) product family. In Oracle EBS 12.1.1 and 12.2.2, it stores academic interests captured through the inquiry interface, acting as the transient landing area for inbound inquiry records before validation and transfer into the operational recruiting and admissions tables. Each row represents a single interest line tied to an inquiry application, carrying the applicant's stated program preference, matching status, and error diagnostics produced during import.

From a Data Vault modeling perspective, the ETRM metadata's heuristic classification of this object is link. This reflects its structure: the primary key INTERFACE_LINES_ID is a surrogate identifier, while the substantive attributes are foreign references to external master data (product categories, code definitions, sales leads), positioning the table as an associative entity connecting an inquiry application to the academic interests or programs selected.

Key Information Stored

The table contains 27 documented columns. The most operationally significant are:

• INTERFACE_LINES_ID — surrogate primary key, enforced by the unique index IGR_I_LINES_INT_PK. No separate business-key unique index is documented; uniqueness of the line is established solely through this surrogate.
• INTERFACE_INQ_APPL_ID — groups each interest line back to its parent inquiry application in the interface batch.
• PREFERENCE and PROGRAM_CODE_ID — the ranked order of the applicant's program interest and the program code (foreign key to FV_DMS_CODE_DEFINITIONS_ALL).
• PRODUCT_CATEGORY_ID and PRODUCT_CATEGORY_SET_ID — foreign keys into MTL_CATEGORIES_B and MTL_CATEGORY_SETS_B, describing the academic product/category of interest.
• SALES_LEAD_ID — foreign key to AS_SALES_LEADS, linking the inquiry to a recruiting lead.
• STATUS, MATCH_IND, ERROR_CODE, and ERROR_TEXT — processing state, match flag, and error diagnostics for each line.
• PERSON_ID, ENQUIRY_APPL_NUMBER, INQUIRY_ENTRY_STATUS_ID, INQUIRY_DATE, and INQUIRY_SOURCE_TYPE — the applicant identity and inquiry context.
• INTERFACE_RUN_ID and audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) — concurrency and batch-trace metadata.

Common Use Cases and Queries

Typical usage centers on validating inbound inquiry loads, reporting unmatched or errored lines, and reconciling interface batches before promotion to the operational tables. A common diagnostic query isolates failed lines:

• List lines with errors for a specific run: SELECT INTERFACE_LINES_ID, ERROR_CODE, ERROR_TEXT FROM IGR_I_LINES_INT WHERE STATUS = 'E' AND INTERFACE_RUN_ID = :run_id;
• Link interest lines to their categories: join PRODUCT_CATEGORY_ID to MTL_CATEGORIES_B and PRODUCT_CATEGORY_SET_ID to MTL_CATEGORY_SETS_B.
• Resolve program codes via PROGRAM_CODE_ID → FV_DMS_CODE_DEFINITIONS_ALL for valid program descriptions.
• Associate inquiries to recruiting leads through SALES_LEAD_ID → AS_SALES_LEADS.

Reporting typically aggregates interest lines by program and source type to measure inquiry demand before conversion.

Related Objects

The most significant related objects, per the documented foreign-key relationships, are:

• MTL_CATEGORIES_B — referenced via PRODUCT_CATEGORY_ID.
• MTL_CATEGORY_SETS_B — referenced via PRODUCT_CATEGORY_SET_ID.
• FV_DMS_CODE_DEFINITIONS_ALL — referenced via PROGRAM_CODE_ID.
• AS_SALES_LEADS — referenced via SALES_LEAD_ID.
• The parent inquiry interface structures implied by INTERFACE_INQ_APPL_ID and INTERFACE_RUN_ID, which group lines by application and batch run respectively.

These dependencies make IGR_I_LINES_INT a linking staging object that draws reference data from inventory categories and descriptive flexfield code definitions while feeding inquiry processing within the IGS Student System.