Search Results dunning_letters




Overview
Explore in AI Chat

Overview

IGI_DUN_CUSTOMER_PROFILE_V is a reporting view owned by the APPS schema within the IGI – Public Sector Financials International product family. Its stated purpose is to hold information about dunning customer profiles, presenting, in a single denormalized row, the customer-level attributes that determine whether and how dunning letters are generated for a customer and a specific bill-to site. Dunning is the process of issuing escalating reminder letters to customers with overdue receivables activity; the profile assigned to a customer drives the dunning letter set, the customer profile classification, and the charge treatment applied when letters are produced. In Oracle EBS 12.1.1 and 12.2.2 the view therefore serves as the primary read interface between the IGI dunning extension tables and the Oracle Receivables customer profile infrastructure, exposing a join that would otherwise require knowledge of several AR and RA base tables plus the IGI extension table IGI_DUN_CUST_PROF.

The view is status VALID in the ETRM 12.2.2 repository. Because it is a view rather than a table, it stores no data of its own; all values are derived at query time from the underlying Receivables and IGI tables.

Underlying Base Objects

The documented referenced base object in ETRM 12.2.2 is DUAL (synonym), reflecting that the view text is resolved through synonyms that ultimately terminate at DUAL for the IGI-side join anchor. The view definition itself selects from seven objects:

The DECODE logic is central to the view's behavior: when a site-level profile exists it takes precedence, otherwise the customer-level profile is used for DUNNING_LETTER_SET_ID, DUNNING_LETTERS, CUSTOMER_PROFILE_ID, and CUSTOMER_PROFILE_CLASS_ID. Records are returned only where a dunning letter set is non-null and the DUNNING_LETTERS indicator equals 'Y'.

Key Columns

  • ROW_ID – the ROWID of the IGI_DUN_CUST_PROF row, for row-level identification.
  • CUSTOMER_ID / CUSTOMER_NAME – the Receivables customer identity.
  • SITE_USE_ID / ADDRESS_ID – the bill-to site use and address.
  • CONCATENATED_ADDRESS – formatted address from AR_ADDRESSES_V.
  • DUNNING_LETTER_SET_ID / DUNNING_LETTER_SET_NAME – the effective letter set, resolved from AR_DUNNING_LETTER_SETS.
  • CUSTOMER_PROFILE_ID – the effective profile, site-level if present, otherwise customer-level.
  • USE_DUNNING_FLAG – IGI flag controlling whether dunning applies.
  • DUNNING_CHARGE_TYPE – charge classification used when dunning letters are generated.
  • Audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include verifying which letter set a customer site will receive, auditing dunning configuration across the customer base, and feeding downstream dunning letter generation or reconciliation reports.

  • List active dunning customers and their letter sets.
  • Identify customers whose effective profile is at customer level rather than site level.
  • Validate charge types in use before month-end dunning runs.

Sample query:

SELECT customer_name, concatenated_address, dunning_letter_set_name, customer_profile_id, use_dunning_flag, dunning_charge_type FROM apps.igi_dun_customer_profile_v WHERE use_dunning_flag = 'Y' ORDER BY customer_name;

Filtering by CUSTOMER_ID or SITE_USE_ID is the most efficient access path. Because the view already enforces the DUNNING_LETTERS = 'Y' and non-null letter set predicates, no additional filtering on those attributes is required.