Search Results igi_exp_dial_doc_temp

Overview

IGI_EXP_DIAL_DOC_TEMP is a temporary staging table within the IGI – Public Sector Financials International product family. It is owned by the IGI schema and holds transient rows generated during the dialog unit creation process, a Public Sector budgeting and funds-control mechanism in which expenditure documents are matched against dialog units before final posting. Because the table exists solely to support this intermediate processing step, its contents are typically short-lived and session-scoped via the SESSION_ID column, allowing concurrent dialog-creation runs to be isolated from one another.

The heuristic Data Vault classification supplied with the object metadata identifies it as a standalone structure. Under a Data Vault model this would suggest a single hub-like or work-table construct without modeled link or satellite dependencies, which is consistent with the fact that no foreign-key or referencing objects were mined from the schema. In practice, the table behaves as a transient staging area rather than a durable warehouse entity, and any Data Vault treatment should be regarded as a modeling suggestion rather than a persistence strategy.

Key Information Stored

The table documents ten columns, and the most significant are those that identify and classify the document records being staged. DOCUMENT_NUM carries the externally recognized document number, while DOCUMENT_ID provides the internal EBS identifier for the same document. Together they anchor any lookup that begins from a user-facing document number and ends at the internal key.

The unique index IGI_EXP_DIAL_DOC_TEMP_U1 spans DOCUMENT_NUM, DOCUMENT_ID, ACCOUNT, AMOUNT, ENGAGEMENT_NUMBER, and SESSION_ID, marking these as the business-key candidate set. The primary key constraint IGI_EXP_DIAL_DOC_TEMP_U1, as documented in the ETRM excerpt, covers DOCUMENT_NUM, DOCUMENT_ID, ACCOUNT, ENGAGEMENT_NUMBER, and SESSION_ID — the same set minus AMOUNT. This distinction is important: AMOUNT participates in the uniqueness of staged rows but is not part of the primary key definition shown in the excerpt.

ACCOUNT holds the accounting distribution the dialog row relates to, CONNECTION: ENGAGEMENT_NUMBER identifies the underlying engagement or funds commitment, and AMOUNT records the monetary value under consideration. DOCUMENT_DATE supports date-based selection and period logic, DESCRIPTION captures a free-text label, DIALOGUE_UNIT_ID and DIAL_UNIT_LINK provide the association between the staged document and the created dialog unit, and SESSION_ID partitions the temporary data by processing run.

Common Use Cases and Queries

The primary operational scenario is validating that dialog units were built correctly from source documents. A typical diagnostic query isolates a single processing run and compares staged documents with the resulting units:

• Session isolation: SELECT * FROM igi.igi_exp_dial_doc_temp WHERE session_id = :p_session_id;
• Document lookup by business number: SELECT document_id, account, amount, engagement_number FROM igi.igi_exp_dial_doc_temp WHERE document_num = :p_document_num;
• Aggregate reconciliation: SELECT document_num, SUM(amount) FROM igi.igi_exp_dial_doc_temp WHERE session_id = :p_session_id GROUP BY document_num;
• Gap analysis between staged and created units: SELECT t.document_num FROM igi.igi_exp_dial_doc_temp t WHERE t.dialogue_unit_id IS NULL;

Reporting uses are limited by the transient nature of the data, but reconciliation reports, failed-unit exception listings, and post-run audit extracts are common. Because the table is a temporary work area, queries should always be bounded by SESSION_ID or by a recent DOCUMENT_DATE to avoid returning rows from unrelated or abandoned runs.

Related Objects

The metadata records no foreign-key relationships, so related objects are inferred from the functional context of the dialog unit creation process rather than from documented constraints.

• Dialog unit tables in the IGI schema, joined on DIALOGUE_UNIT_ID, receive the units created from staged rows.
• Engagement tables referenced through ENGAGEMENT_NUMBER supply the commitment context for each staged document.
• Accounting distribution tables matched on ACCOUNT and DOCUMENT_ID provide the funds-control detail.
• Supplier and invoice interface objects keyed by DOCUMENT_NUM supply the source document identity.
• Concurrent program and request log tables joined on SESSION_ID or request ID trace the dialog creation run that produced the temporary rows.

Direct querying of IGI_EXP_DIAL_DOC_TEMP for permanent reporting is inadvisable; it should be treated as an implementation and troubleshooting object whose rows are meaningful only within the lifecycle of a single dialog unit creation run.