Results for “error_text”

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

Overview

IGS.IGS_AD_OFFRESP_ERR is a transactional interface error table in the Oracle E-Business Suite Student System (IGS) module. It holds error details produced when offer response records are processed through the admissions offer response interface. Within the IGS admissions workflow, offer responses such as acceptances, declines, and deferrals are staged in an interface table and subsequently validated and transferred into the operational student tables. When a staged row fails validation — for example, due to an invalid offer response code, an unmatched applicant, or a missing prerequisite reference — the corresponding error information is written to IGS_AD_OFFRESP_ERR rather than rejected silently. This makes the table the primary diagnostic surface for the offer response interface and the first object an administrator examines when offer response data does not reach its intended destination.

The metadata identifies a primary key, IGS_AD_OFFRESP_ERR_PK, defined on the OFFRESP_ERR_ID column, and a single foreign key from OFFRESP_INT_ID to IGS_AD_OFFRESP_INT. Based on this foreign-key structure, the table is heuristically classified as satellite-leaning in a Data Vault model. This is a modeling suggestion: the table records descriptive error attributes that surround a parent interface record, which is characteristic of satellite behaviour rather than of a hub or a link.

Key Information Stored

The table contains thirteen documented columns. The most significant are described below.

• OFFRESP_ERR_ID — the surrogate primary key and the column underpinning IGS_AD_OFFRESP_ERR_PK. It uniquely identifies each error row. No separate unique business-key index is documented beyond the primary key, so this value should be treated as a technical identifier rather than a human-recognisable key.
• OFFRESP_INT_ID — the foreign key to IGS_AD_OFFRESP_INT. This is the business link that ties each error back to the originating interface row, and it is the single most important column for diagnostic joins.
• ERROR_CODE and ERROR_TEXT — the actual cause of failure. ERROR_CODE supports programmatic categorisation and filtering, while ERROR_TEXT provides the human-readable message presented to the user.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns, recording who inserted or modified the error row and when.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program context columns identifying the specific request and program execution that generated the error. These are essential when correlating errors to a particular interface run.

Common Use Cases and Queries

The canonical use case is troubleshooting a failed offer response interface run. A typical query joins the error table to its parent interface table to return the offending source data alongside the failure reason:

• Listing all errors from a specific concurrent request: SELECT * FROM igs.igs_ad_offresp_err WHERE request_id = :request_id;
• Joining to the interface table: SELECT i.*, e.error_code, e.error_text FROM igs.igs_ad_offresp_int i, igs.igs_ad_offresp_err e WHERE i.offresp_int_id = e.offresp_int_id;
• Grouping by ERROR_CODE to quantify recurring validation failures across interface runs.
• Auditing error volume by CREATION_DATE to track interface health over time.

Because the table is error-focused, it is normally queried rather than reported against for business metrics; however, recurring error patterns are frequently used as a data-quality indicator for upstream admissions data entry.

Related Objects

• IGS.IGS_AD_OFFRESP_INT — the parent interface table, joined on OFFRESP_INT_ID; this is the only documented foreign-key relationship.
• IGS_AD_OFFRESP_ERR_PK — the primary-key constraint and its backing unique index on OFFRESP_ERR_ID.
• The offer response concurrent program defined by PROGRAM_ID / PROGRAM_APPLICATION_ID, and its REQUEST_ID instance in FND_CONCURRENT_REQUESTS, which provide run-level context.
• Offer-response validation logic in the IGS admissions APIs, which populate this error table during interface processing.
• Standard EBS audit and user references implied by CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.