Search Results igi_dun_letter_set_cur




Overview
Explore in AI Chat

Overview

The table IGI_DUN_LETTER_SET_CUR is a core data object within the Oracle E-Business Suite module IGI (Public Sector Financials International). It functions as a child table in the dunning letter management system, specifically designed to handle multi-currency requirements. Its primary role is to define and store the valid currencies that can be associated with a specific dunning letter set. A dunning letter set is a collection of rules and templates governing the generation of payment reminder notices. By allowing currency records to be entered against a parent set, this table enables organizations operating across multiple countries to manage their receivables dunning processes in the functional currencies of their transactions, ensuring compliance and clarity in international collections.

Key Information Stored

The table's structure is defined by a composite primary key, which dictates the fundamental business rule it enforces. The two critical columns are DUNNING_LETTER_SET_ID and CURRENCY_CODE. The DUNNING_LETTER_SET_ID is a foreign key that links each record back to its parent definition in the IGI_DUN_LETTER_SETS table. The CURRENCY_CODE column stores the three-character ISO currency code (such as USD, EUR, GBP) that is permitted for use with the linked dunning letter set. Together, these columns create a unique pairing, ensuring that a currency is not duplicated for a given set. While the provided metadata focuses on these key columns, typical implementations might include audit columns like CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY to track record maintenance.

Common Use Cases and Queries

The primary use case is the validation and configuration of currencies for dunning processes. Before a dunning letter can be generated for a transaction, the system validates that the transaction's currency is defined for the applicable letter set. Common reporting and operational queries involve listing all configured currencies for a set or identifying which sets support a specific currency. For example, to audit all active currency assignments, a query would join to the parent IGI_DUN_LETTER_SETS table. A typical SQL pattern is: SELECT s.set_name, c.currency_code FROM igi.igi_dun_letter_set_cur c, igi.igi_dun_letter_sets s WHERE c.dunning_letter_set_id = s.dunning_letter_set_id ORDER BY s.set_name, c.currency_code;. Troubleshooting a failure in letter generation for a particular currency would also involve verifying its existence in this table.

Related Objects

IGI_DUN_LETTER_SET_CUR sits at the center of a key relationship hierarchy within the IGI dunning module. It has a direct foreign key dependency on the parent table IGI_DUN_LETTER_SETS via the DUNNING_LETTER_SET_ID column. Furthermore, it serves as a parent table itself. The table IGI_DUN_LETTER_SET_LINES references IGI_DUN_LETTER_SET_CUR through a composite foreign key on both DUNNING_LETTER_SET_ID and CURRENCY_CODE. This establishes a critical data integrity chain: a dunning letter line (which defines specific letter text or conditions) must be associated with both a valid letter set and a currency that has been explicitly authorized for that set. This design ensures that letter content is properly scoped to its applicable currency context.