Results for “igs_ad_txcpt_int_all”

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

Overview

The IGS_AD_TXCPT_INT_ALL table belongs to the IGS (Student System) product family within Oracle E-Business Suite. Its documented description states that it "holds transcript details." The table functions as an interface staging object, as indicated by the "INT" (interface) suffix in its name and by the primary key structure. In the Oracle EBS architecture, interface tables of this type serve as a landing zone for data extracted from external student information systems or feeder applications before validation, transformation, and loading into the core transcript tables of the Student System.

The metadata classifies this table as obsolete within the EBS 12.1.1 and 12.2.2 codebase. It is explicitly noted as "Not implemented in this database," meaning the object may exist only as a shipped stub, a legacy artifact from earlier releases, or a placeholder retained for backward compatibility. Because the table is a staging interface, records are typically transient in nature — populated, processed, and purged or archived rather than retained indefinitely.

Per the heuristic Data Vault classification derived from the foreign key structure, this object is modeled as standalone. In Data Vault terms, a standalone classification suggests the table has no outward foreign key dependencies on other hub entities within the mined relationship graph, and its single-column surrogate primary key aligns most naturally with a hub-style construct — one row per unique interface transcript record. This is a modeling suggestion only; because the IGS Student System is obsolete and the object is unimplemented, no enforcement of these relationships should be assumed in a production EBS 12.1.1 or 12.2.2 instance.

Key Information Stored

The documented metadata exposes a limited column inventory for this object. The most significant documented element is the surrogate primary key, which is defined as follows:

• INTERFACE_TRANSCRIPT_ID — The single documented column, serving as the surrogate primary key of the table and the sole column of the IGS_AP_TXCPT_INT_PK constraint. This identifier uniquely distinguishes each interface transcript row within the staging set.

Because the primary key constraint IGS_AP_TXCPT_INT_PK is composed exclusively of INTERFACE_TRANSCRIPT_ID, the surrogate key and the enforcement key coincide; no separate business-key unique index is documented in the supplied metadata. In a typical interface table design, one would expect companion columns for the source system key, student or person identifier, academic period, transcript type, and interface status, but such columns are not enumerated in the provided ETRM excerpt and should not be assumed without direct inspection of the shipped DDL. Where transcript details are involved, business-key candidates would ordinarily include a person/student identifier combined with an academic term or transcript reference; however, no such unique index is documented here.

Common Use Cases and Queries

Interface transcript tables support inbound data integration: external transcripts are loaded into the staging table, validated against student records, and then promoted into the core transcript structures. Reporting on such an object typically addresses load reconciliation and error tracking. A representative query pattern for reconciliation might count staged rows by processing batch:

• Counting staged transcript records: SELECT COUNT(*) FROM IGS_AD_TXCPT_INT_ALL;
• Retrieving a specific staged record by surrogate key: SELECT * FROM IGS_AD_TXCPT_INT_ALL WHERE INTERFACE_TRANSCRIPT_ID = :id;
• Verifying primary key integrity: SELECT INTERFACE_TRANSCRIPT_ID, COUNT(*) FROM IGS_AD_TXCPT_INT_ALL GROUP BY INTERFACE_TRANSCRIPT_ID HAVING COUNT(*) > 1;
• Confirming object presence and status in the data dictionary: SELECT TABLE_NAME, STATUS FROM DBA_TABLES WHERE TABLE_NAME = 'IGS_AD_TXCPT_INT_ALL';

Given the documented "Not implemented in this database" status, the practical use case in 12.1.1/12.2.2 is most often impact assessment: confirming whether the object exists, whether any data is present, and whether legacy customizations or concurrent programs reference it before migration.

Related Objects

The supplied metadata documents no foreign key relationships for IGS_AD_TXCPT_INT_ALL, consistent with its standalone Data Vault classification. The only documented structural associate is its primary key constraint, IGS_AP_TXCPT_INT_PK, which is enforced on the INTERFACE_TRANSCRIPT_ID column:

• IGS_AP_TXCPT_INT_PK — Primary key constraint; column INTERFACE_TRANSCRIPT_ID.

In a functional deployment of the IGS Student System, one would expect corresponding base transcript tables and the concurrent interface-loading programs to reference staged records via the surrogate key, but no such object names are provided in this metadata and therefore none can be asserted as documented dependencies. The absence of FK data reinforces that this table is an isolated staging artifact. Because the product is obsolete and the table is unimplemented, related-object analysis should be performed directly against the specific EBS instance's data dictionary rather than inferred from documentation.