Search Results interface_reladdr_id

Overview

The IGS_AD_RELADDR_INT view is a public synonym-facing database object owned by the APPS schema within the Oracle E-Business Suite Student System (IGS) product family. It functions as a relational interface view that exposes data staged for the relationship address interface process, which is used to load and validate address information associated with person or organization relationships in Oracle Student System. The suffix _INT signals that this object is an interface (staging) view rather than a base transactional entity; records in the interface are prepared, validated, and ultimately transferred to permanent relationship address tables during concurrent processing.

Because it is a view defined with the ROWID pseudo-column exposed as ROW_ID, it is updatable against its underlying interface table, permitting direct DML from forms, APIs, and correction scripts. The view is registered as VALID in the data dictionary, and reference to it appears in ETRM metadata for releases 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over a single documented base object, IGS_AD_RELADDR_INT_ALL, and applies an ORG_ID filter pattern characteristic of Oracle multi-org views. No additional base tables are documented in the referenced metadata. The _ALL suffix of the underlying table indicates it stores rows for all operating units, while the view presents those rows with ORG_ID carried forward as a selectable column rather than filtered at view definition. Practically, this means the view exposes the full set of interface rows; operating-unit security is enforced either by the calling application, by a securing WHERE clause, or by the standard multi-org policy applied at the table level in releases that use Virtual Private Database.

All column names in the view map one-to-one to columns in the base table, with the sole exception of the first column, where TAB.ROWID is aliased as ROW_ID. This identity mapping preserves the integrity of bulk interface loads performed by SQL*Loader or the interface APIs.

Key Columns

• ROW_ID — the physical row identifier of the underlying interface record; used for targeted updates and deletes.
• ORG_ID — operating unit identifier supporting multi-org security.
• INTERFACE_RELADDR_ID — primary key of the address interface row.
• INTERFACE_RELATIONS_ID — foreign key linking the address row to the relationship interface record being processed.
• CORRESPONDENCE — flag or indicator denoting whether the address is used for correspondence.
• START_DT / END_DT — effective date range for the address.
• ADDR_LINE_1 through ADDR_LINE_4, CITY, STATE, PROVINCE, COUNTY, COUNTRY, POSTAL_CODE — the standard address attribute set.
• OTHER_DETAILS_1 through OTHER_DETAILS_3 — overflow or locale-specific address details.
• MATCH_IND, STATUS, ERROR_CODE — processing control columns indicating whether the row matched an existing address, its current interface status, and any validation error encountered.
• SITE_USE_CODE_1 and SITE_USE_CODE_2 — the site usage designators (for example, mailing, billing, or correspondence) assigned to the first and second site records associated with the address interface row. These are the columns most frequently searched by functional users troubleshooting address imports.
• LOCATION_1 and LOCATION_2 — location identifiers or location codes corresponding to the two site use entries.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns identifying the process that populated the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard who-columns.

Common Use Cases and Queries

Typical use cases include auditing interface data before submission, diagnosing rejected rows by inspecting STATUS and ERROR_CODE, and reporting on site usage codes carried in through the interface.

SELECT interface_reladdr_id,
       interface_relations_id,
       addr_line_1,
       city,
       site_use_code_1,
       site_use_code_2,
       status,
       error_code
  FROM apps.igs_ad_reladdr_int
 WHERE status = 'ERROR';

Locating rows by site usage code, the subject of the user's original search:

SELECT interface_reladdr_id,
       interface_relations_id,
       addr_line_1,
       site_use_code_1,
       site_use_code_2
  FROM apps.igs_ad_reladdr_int
 WHERE site_use_code_1 = 'MAIL';

Reviewing rows produced by a specific concurrent request:

SELECT interface_reladdr_id,
       request_id,
       program_id,
       status,
       error_code
  FROM apps.igs_ad_reladdr_int
 WHERE request_id = :request_id;

Because the view is updatable through ROW_ID, correction statements can be issued directly against interface rows to reset STATUS or ERROR_CODE prior to resubmitting the relationship address interface concurrent program.