Search Results dunning_receivables_trx_name




Overview

IGI_AR_SYSTEM_OPTIONS_V is an APPS-owned database view within the Oracle E-Business Suite Receivables subsystem, exposed by the ETRM (E-Business Suite Technical Reference Manual) for releases 12.1.1 and 12.2.2. It presents configuration and setup information maintained at the operating unit level for Receivables-related processing, specifically the default settings that govern Receivables Processing Instructions (RPI) and dunning activities. The view resolves the Receivables transaction reference from the underlying system options table into a human-readable transaction name, enabling concurrent programs, reports, and integration interfaces to consume system option data without re-implementing the join logic themselves.

The "IGI" prefix associates the object with Oracle's Public Sector / Financials family of products rather than core Receivables, although the view is registered under the APPS schema and is therefore accessible through standard APPS-privileged access paths. From a reporting standpoint the view behaves as a denormalized read-only representation of a single base configuration table, augmented with descriptive attributes drawn from the Receivables transaction definition table.

Underlying Base Objects

The documented base objects referenced by the view are IGI_AR_SYSTEM_OPTIONS and AR_RECEIVABLES_TRX_ALL, both exposed to the view definition as APPS synonyms. The view joins these two objects on the Receivables transaction identifier and operating unit identifier.

  • IGI_AR_SYSTEM_OPTIONS — the primary base table holding system option records keyed by SET_OF_BOOKS_ID and ORG_ID, including RPI header and line context codes, charge identifiers, generation sequences, price break numbers, and the dunning receivables transaction reference.
  • AR_RECEIVABLES_TRX_ALL — the Receivables transactions table, which supplies the transaction NAME used to describe the dunning activity configured in the system options.

The join predicate is deliberately written with DECODE expressions so that a NULL dunning transaction identifier is preserved rather than eliminated. When DUNNING_RECEIVABLES_TRX_ID is NULL, both sides of the join evaluate to -1, allowing the row to survive with a NULL name. The ORG_ID equality condition enforces multi-org security partitioning.

Key Columns

Because the view is defined with SELECT DISTINCT, duplicate rows are collapsed before results are returned.

Common Use Cases and Queries

Typical applications include validation of dunning configuration prior to collections processing, extraction of RPI settings for reconciliation reporting, and diagnostic queries during Receivables setup reviews.

Retrieve all system options for the active operating unit:

  • SELECT set_of_books_id, rpi_header_context_code, rpi_line_context_code, dunning_receivables_trx_id FROM igi_ar_system_options_v WHERE org_id = :org_id;

Identify the dunning transaction configured for a ledger:

  • SELECT set_of_books_id, dunning_receivables_trx_id, DECODE(dunning_receivables_trx_id, NULL, NULL, name) dunning_name FROM igi_ar_system_options_v WHERE set_of_books_id = :sob_id;

Locate operating units where no dunning transaction is configured:

  • SELECT org_id, set_of_books_id FROM igi_ar_system_options_v WHERE dunning_receivables_trx_id IS NULL;

Audit recently changed configuration:

  • SELECT org_id, last_updated_by, last_update_date FROM igi_ar_system_options_v WHERE last_update_date > :since_date ORDER BY last_update_date;

All queries are subject to multi-org views and APPS-level security applied by the invoking responsibility.