Search Results igi_dos_doc_types_n1

Overview

IGI.IGI_DOS_DOC_TYPES is a transactional configuration table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the IGI schema and registered under the FND Design Data repository as IGI.IGI_DOS_DOC_TYPES. The table stores the Dossier Document Types defined by administrators within the Oracle Financials for Europe / Public Sector dossier functionality. Each row represents a distinct dossier document type, capturing the numbering scheme, chart of accounts reference, hierarchy assignment, budget-balance behavior, workflow association, and relationship semantics that govern how a dossier — and its associated accounting events — is processed and reported. The table physically resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, reflecting its role as an actively maintained transactional data set rather than a static reference lookup.

From a Data Vault modeling perspective, the table exhibits a satellite-leaning profile. The heuristic classification derived from the foreign-key structure suggests that IGI_DOS_DOC_TYPES functions primarily as a descriptive satellite attached to a dossier business key, rather than as a pure hub or link. The presence of many descriptive attributes (numbering scheme, balance indicator, workflow name, status) that qualify a single natural key supports this interpretation.

Key Information Stored

The table contains 39 documented columns, of which the following are most operationally significant:

• DOSSIER_ID — The surrogate primary key (IGI_DOS_DOC_TYPES_PK) that uniquely identifies each dossier document type and serves as the principal join column to dependent tables.
• DOSSIER_NAME — The business-key candidate protected by the unique index IGI_DOS_DOC_TYPES_U2, storing the administrator-defined dossier name (VARCHAR2(60)).
• DOSSIER_NUMBERING — The numbering scheme name (VARCHAR2(50)) that controls document sequence generation; this column participates in a documented foreign-key relationship.
• COA_ID and SOB_ID — Identifiers linking the dossier type to a Chart of Accounts and a Set of Books respectively; SOB_ID is indexed non-uniquely via IGI_DOS_DOC_TYPES_N1.
• HIERARCHY_ID — References the hierarchy applied to the dossier structure.
• BALANCED — Indicator controlling whether the dossier enforces a balanced budget journal.
• MULTI_ANNUAL — Indicator denoting whether the dossier spans multiple fiscal years.
• DOSSIER_STATUS and RETIRED_FLAG — Lifecycle attributes governing availability and retirement of the document type.
• WORKFLOW_NAME — The workflow associated with the dossier type (VARCHAR2(30)).
• DOSSIER_RELATIONSHIP and RELATED_DOSSIER_ID — Define and link related dossiers with display variants.
• AMOUNT_TYPE and DOSSIER_DESCRIPTION — Additional descriptive qualifiers.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield structure and segment columns enabling administrator-defined extensions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns, with CREATED_BY and LAST_UPDATED_BY being foreign keys to FND_USER.USER_ID.

Common Use Cases and Queries

Typical usage centers on validating dossier configuration, driving conditional processing logic, and supporting reporting. A common pattern retrieves all active document types for a given set of books:

SELECT d.dossier_id, d.dossier_name, d.sob_id, d.coa_id, d.dossier_numbering
FROM igi.igi_dos_doc_types d
WHERE d.sob_id = :p_sob_id
  AND NVL(d.retired_flag,'N') = 'N';

Because IGI_DOS_DOC_TYPES_U2 enforces uniqueness on DOSSIER_NAME, lookups by name are efficient and are frequently used to validate configuration prior to transaction entry. The IGI_DOS_DOC_TYPES_N1 index on SOB_ID supports set-of-books-scoped reporting. Budget-balance and multi-annual indicators are commonly extracted for financial reporting and reconciliation against dossier transaction history, while flexfield attributes support customer-specific reporting extensions.

Related Objects

IGI_DOS_DOC_TYPES is referenced by several dossier transaction tables through the DOCUMENT_ID foreign key, making it a pivotal parent in the dossier data model:

• IGI_DOS_DESTINATIONS — references DOSSIER_ID; holds destination allocation definitions.
• IGI_DOS_ITEMS — references DOSSIER_ID; stores dossier line items.
• IGI_DOS_TRX_HEADERS_HIST — references DOSSIER_ID; the historical transaction header store.
• IGI_DOS_TRX_DEST_HIST — references DOSSIER_ID; historical transaction destination records.
• IGI_DOS_TRX_SOURCES_HIST — references DOSSIER_ID; historical transaction source records.
• FND_USER — related via the CREATED_BY and LAST_UPDATED_BY audit columns.
• FND_LOGINS — related via the LAST_UPDATE_LOGIN audit column.