Search Results igi_exp_doc_type_pk




Overview
Explore in AI Chat

Overview

IGI_EXP_DOC_TYPE is a reference table residing in the IGI schema (Public Sector Financials International) within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store information on the various documents used by the exchange protocol. The exchange protocol functionality supports public-sector procurement and inter-agency document exchange, where a standardized catalogue of document types is required so that transactions can be classified, routed, and validated consistently. The table acts as the controlling vocabulary for document classification: each row defines a document type that downstream transaction records reference.

From a dimensional modeling perspective, the heuristic Data Vault classification supplied in the metadata is hub-leaning. This suggests treating IGI_EXP_DOC_TYPE as a hub entity whose business key is represented by the primary key column, with dependent descriptive attributes ideally separated into a satellite. In practice, because the table carries both an identifier and descriptive columns such as name and description, it functions as a combined hub-and-satellite reference table in the delivered EBS schema.

Key Information Stored

The documented physical schema for release 12.2.2 contains nine columns. The most important are:

  • DOC_TYPE_ID — the surrogate primary key, enforced by the unique index IGI_EXP_DOC_TYPE_PK. It uniquely identifies each document type and is the column referenced by foreign keys elsewhere.
  • DOC_TYPE_NAME — the business-meaningful label for the document type; the column most commonly displayed in list-of-values and lookup queries.
  • DESCRIPTION — free-text explanation of the document type, used for disambiguation when similar document types exist.
  • APPLICATION — identifies the application context to which the document type belongs, supporting multi-application deployments of the exchange protocol.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — the standard EBS WHO columns providing audit lineage for each row.

No unique index other than the primary key is documented, so DOC_TYPE_NAME should be treated as a descriptive attribute rather than a guaranteed business key. Implementers should not assume uniqueness of the name column without validating against actual data.

Common Use Cases and Queries

Typical uses include populating document-type list-of-values on entry forms, reporting on the distribution of transaction types by document type, and validating inbound exchange payloads against the registered catalogue. A basic lookup query is:

  • SELECT doc_type_id, doc_type_name, description FROM igi.igi_exp_doc_type ORDER BY doc_type_name;
  • SELECT t.trx_type_id, t.doc_type_id, d.doc_type_name FROM igi.igi_exp_trx_type t, igi.igi_exp_doc_type d WHERE t.doc_type_id = d.doc_type_id;
  • SELECT d.doc_type_name, COUNT(*) FROM igi.igi_exp_doc_type d JOIN igi.igi_exp_trx_type t ON t.doc_type_id = d.doc_type_id GROUP BY d.doc_type_name;

Because the table is small and rarely changes, it is a common candidate for caching in concurrent programs and for inclusion in BI Publisher data templates.

Related Objects

The documented foreign key relationship identifies the principal dependent object. Significant related tables include:

  • IGI_EXP_TRX_TYPE — the primary referencing table, joining via IGI_EXP_TRX_TYPE.DOC_TYPE_ID = IGI_EXP_DOC_TYPE.DOC_TYPE_ID. This is the only foreign key documented in the ETRM metadata.
  • IGI_EXP_DOC_TYPE_PK — the unique index backing the primary key, essential for join performance.
  • Other IGI exchange-protocol tables (transaction headers, lines, and party or agreement tables) that participate in the same document exchange flow and indirectly depend on the document-type catalogue.
  • Standard EBS administrative views and concurrent programs that present document-type lookups within the Public Sector Financials responsibility.

Developers extending the exchange protocol should preserve referential integrity to IGI_EXP_DOC_TYPE and avoid deleting rows referenced by IGI_EXP_TRX_TYPE.