Results for “ar_dunning_letters_b”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_DUNNING_LETTERS_B is the base (or "_B") table in the Oracle Receivables (AR) schema that stores information about dunning letters in Oracle E-Business Suite 12.1.1 and 12.2.2. A dunning letter is the correspondence Oracle Receivables generates and delivers to a customer to request payment on overdue transactions. This table serves as the definitional core of that process, holding the header-level attributes that define and describe each dunning letter configuration used by the collections and correspondence functionality.

Being a "_B" table, it functions as the base table in the standard Oracle EBS pattern where a companion "_T" table (translation) holds language-specific descriptive text. The base table itself holds language-independent identifiers, status, and descriptive flexfield attributes. With 25 documented columns in the 12.2.2 physical schema and a single-column surrogate primary key, the object is compact and centrally positioned in the dunning-letter entity structure.

Under the heuristic Data Vault classification mined from its foreign-key structure, this table leans toward a hub style. The modeling suggestion is that DUNNING_LETTER_ID behaves as a durable business key that anchors references from multiple dependent tables, which is exactly the role a hub plays. It should be understood as a suggestion rather than a mandated design pattern.

Key Information Stored

The table centers on a single surrogate primary key and a small set of controlling columns. The most significant documented columns are:

Regarding business-key candidates, DUNNING_LETTER_ID is documented both as the primary key (AR_DUNNING_LETTERS_B_PK) and as a unique index (AR_DUNNING_LETTERS_B_UK2). The unique index AR_DUNNING_LETTERS_B_U2 additionally spans DUNNING_LETTER_ID and ZD_EDITION_NAME, reflecting the editioning requirement introduced for 12.2. No separate short code or name column appears among the documented columns, so the identifier and flexfield segments carry the descriptive load in this base table.

Common Use Cases and Queries

Typical use cases involve identifying which dunning letters are active, tracing which letter sets include a given letter, and locating the correspondence records produced from a letter. A representative query to list active letter definitions is:

  • SELECT dunning_letter_id, status, review_date FROM ar_dunning_letters_b WHERE status = 'A';
  • Joining to the letter-set lines: SELECT l.dunning_letter_id, s.dunning_letter_set_id FROM ar_dunning_letters_b l, ar_dunning_letter_set_lines s WHERE l.dunning_letter_id = s.dunning_letter_id;
  • Tracing correspondence: SELECT c.correspondence_id FROM ar_correspondences_all c, ar_dunning_letters_b l WHERE c.reference2 = l.dunning_letter_id;

Reporting uses include reconciling dunning letter definitions against the letter sets that group them, auditing newly created or modified letters through the audit columns, and querying the descriptive flexfield segments to report customer-defined attributes. Because translation text resides in the companion _T table, reports requiring user-facing letter names should join accordingly.

Related Objects

Several tables reference this object through foreign keys, and these represent the most significant dependencies:

Together these relationships confirm the table's hub-like position: a single DUNNING_LETTER_ID fans out to set membership, correspondence output, and charge definitions across both the standard Receivables and IGI schemas.