Search Results igs_fi_crd_int_all




Overview

The table IGS.IGS_FI_CRD_INT_ALL belongs to the IGS (Student System) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Per the documented ETRM metadata, its status is VALID but its description is explicitly recorded as "No longer used." This designation is significant: while the object remains physically present in the schema with 54 documented columns, it is not part of the active functional data model for the current release. It appears to have historically supported the capture of credit instrument and credit card receipt information associated with student financial transactions, a role now superseded by other structures in the student financials subsystem.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure identifies this table as standalone. The table carries two foreign key references — CREDIT_TYPE_ID pointing to IGS_FI_CR_TYPES_ALL and SUBACCOUNT_ID pointing to IGS_FI_SUBACCTS_ALL — but no inbound dependencies are documented. In Data Vault terms, the presence of a surrogate primary key, descriptive attributes, and outbound references to two independent reference entities suggests a satellite-like or link-like design; the standalone classification reflects the absence of documented child relationships rather than the absence of integration points. This classification should be treated as a modeling suggestion, not an authoritative architectural statement.

Key Information Stored

The table is keyed by CREDIT_INT_ID, which serves as both the primary key (IGS_FI_CRD_INT_ALL_PK) and the sole documented unique index (IGS_FI_CRD_INT_ALL_U1). This surrogate identifier is the only business-key candidate recorded in the metadata; no natural composite unique key is documented.

The most functionally significant columns include:

Twenty generic ATTRIBUTE1 through ATTRIBUTE20 columns provide extensibility, and standard audit columns (LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE) plus concurrent program context columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID) are present.

Common Use Cases and Queries

Because the object is documented as no longer used, the primary practical use cases are historical reconciliation, migration validation, and archival reporting. Typical queries include joining the table to its type and subaccount parents to reconstruct the credit classification, and filtering by GL_DATE for period-based general ledger analysis.

SELECT c.credit_int_id, c.credit_number, t.credit_type,
       c.amount, c.currency_cd, c.gl_date
FROM   igs.igs_fi_crd_int_all c,
       igs.igs_fi_cr_types_all t
WHERE  c.credit_type_id = t.credit_type_id
AND    c.org_id = :org_id;

Analysts performing data migration assessments frequently count rows and inspect orphaned foreign keys, since CREDIT_TYPE_ID and SUBACCOUNT_ID must resolve to their parent tables. Reports that previously consumed this table should be re-pointed to the successor credit-intake structures in the Student System.

Related Objects

The most significant related objects, based on documented foreign key relationships, are:

  • IGS_FI_CR_TYPES_ALL — joined via CREDIT_TYPE_ID; supplies the credit type classification.
  • IGS_FI_SUBACCTS_ALL — joined via SUBACCOUNT_ID; provides the subaccount context.
  • IGS_FI_CRD_INT_ALL_PK — the primary key constraint enforcing CREDIT_INT_ID uniqueness.
  • IGS_FI_CRD_INT_ALL_U1 — the unique index on CREDIT_INT_ID, the sole business-key candidate.

No child tables, views, or APIs are documented as depending on IGS_FI_CRD_INT_ALL, consistent with its standalone classification and deprecated status.