Search Results igr_i_char_int_n2

Overview

The IGS.IGR_I_CHAR_INT table is an Oracle E-Business Suite interface (staging) table that holds inquiry characteristics records awaiting import. It belongs to the IGS product (Oracle Advanced Outbound / iRecruitment / Graduate Recruitment family) and is stored in the APPS_TS_INTERFACE tablespace, the standard staging area for inbound data destined for a production table. The table acts as a child to IGR_I_APPL_INT; the INTERFACE_INQ_APPL_ID column links rows between the two staging tables, and records ultimately migrate to the production table IGR_I_A_CHARTYP.

In Oracle EBS 12.1.1 and 12.2.2 the object is documented as VALID, with a public scope and an active lifecycle. The FND Design Data reference is IGS.IGR_I_CHAR_INT. From a data-modeling perspective, the supplied heuristic classifies this table as standalone — there is no documented foreign-key parent within the Data Vault mining. As a modeling suggestion only, this object behaves as a link/relationship style staging table: it carries the inquiry-to-application association (via INTERFACE_INQ_APPL_ID) and the characteristic detail as dependent attributes, which would normally be modeled as a satellite around that link. No FK-based hub classification was mined, so the standalone label reflects the physical interface schema rather than a true dimensional model.

Key Information Stored

The table contains 19 documented columns. The most significant are:

• INTERFACE_INQ_CHAR_ID — numeric (15) surrogate primary key, backed by the unique index IGR_I_CHAR_INT_PK. This is the only documented unique-business-key candidate.
• INTERFACE_INQ_APPL_ID — numeric (15); the interface inquiry application identifier and the linking column to IGR_I_APPL_INT. It is supported by non-unique index IGR_I_CHAR_INT_N1.
• INQUIRY_CHARACTERISTIC_TYPE — varchar2(30); the type of characteristic being imported.
• STATUS — recording state: 1 = Completed, 2 = Pending, 3 = Error, 4 = Warning. Indexed via IGR_I_CHAR_INT_N2 for status filtering.
• MATCH_IND — match outcome code (e.g. 18/19 for matched records, 20/21/22 for review states, 11 for no match).
• ERROR_CODE and ERROR_TEXT — capture validation failures during import processing.
• INTERFACE_RUN_ID — groups rows by a given concurrent import run; indexed via IGR_I_CHAR_INT_N3.
• REQUEST_ID — standard concurrent-program who column, identifying the submitting request.
• PERSON_ID — reference to the person associated with the inquiry characteristic.
• ENQUIRY_APPL_NUMBER — the enquiry application business number carried on the interface row.
• Standard WHO columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical usage centres on monitoring and troubleshooting the inbound interface before and after the import concurrent program runs.

• Retrieve all pending characteristics awaiting import for a specific application:

  SELECT c.interface_inq_char_id, c.interface_inq_appl_id,
         c.inquiry_characteristic_type, c.match_ind
  FROM   igs.igr_i_char_int c
  WHERE  c.status = '2';

• Join the child characteristic rows to the parent application interface rows on the linking column:

  SELECT a.interface_inq_appl_id, c.interface_inq_char_id, c.status
  FROM   igs.igr_i_appl_int a, igs.igr_i_char_int c
  WHERE  a.interface_inq_appl_id = c.interface_inq_appl_id;

• Raise error reports grouped by run:

  SELECT interface_run_id, error_code, error_text, COUNT(*)
  FROM   igs.igr_i_char_int
  WHERE  status = '3'
  GROUP  BY interface_run_id, error_code, error_text;

• Reconciliation reporting to confirm matched versus retained records using MATCH_IND.

Related Objects

• IGS.IGR_I_APPL_INT — parent interface table; joined via INTERFACE_INQ_APPL_ID.
• IGS.IGR_I_A_CHARTYP — the production (destination) table populated after successful import.
• IGR_I_CHAR_INT_PK / _N1 / _N2 / _N3 — the primary-key and supporting indexes on INTERFACE_INQ_CHAR_ID, INTERFACE_INQ_APPL_ID, STATUS, and INTERFACE_RUN_ID respectively.
• FND concurrent request tables — correlated through REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID to trace the submitting import process.
• PER_PEOPLE_F — related via PERSON_ID where person context is required.