Dunning text codes

The system provides two separate entities to manage dunning letter text. You must understand the difference between the entities because the entities serve different dunning processes and have different capabilities.

DunningTextCode (Enterprise-Group Level for Advanced Dunning)

The DunningTextCode entity stores body text for Advanced Dunning letters. Each record is keyed by DunningTextCode and IsoLocale. The structure supports the same code in multiple languages and includes up to 12 lines of text. The DunningLetter entity references these records. The Print Job retrieves text based on the level text code and the customer language. Text is entered in a notes-style interface. Validation occurs for line and character limits. An error message is displayed if the limits are exceeded.

DunningLetterTextCode (Company Level for Basic Dunning)

The DunningLetterTextCode entity stores text for dunning letters at the company level. Each record uses Company, IsoLocale, and DunningLetterTextCode as keys. Each record contains up to six lines of text. This capacity is half of the capacity that the enterprise-level DunningTextCode provides. The entity includes a UsedFlag (Boolean). The UsedFlag indicates whether the text code is in use. The Basic Dunning process uses this text code, not the Advanced Dunning process. The DunningLetterTextCode entity uses a notes interface for text entry. The interface validates line count and line length.

Comparison of DunningTextCode and DunningLetterTextCode

Table 1. This shows the comparison of DunningTextCode and DunningLetterTextCode
Attribute	DunningTextCode	DunningLetterTextCode
Scope	Enterprise-group level	Company level
Key Fields	DunningTextCode + IsoLocale	Company + IsoLocale + DunningLetterTextCode
Maximum Lines	12	6
Used By	Advanced Dunning	Basic Dunning
UsedFlag	No	Yes
Text Storage	DunningTextX6InArduntxtcd (12 lines)	DunningTextX6InArdunning (6 lines)

Multi-Language Support

Both text code entities use the IsoLocale field as part of the key to support multiple languages in dunning correspondence. This process works as follows:

Create text codes for each required language. For example, create the DunningTextCode “REMIND1” with IsoLocale “en_US” for english. The record contains the letter text for the specified language.
Assign a LanguageCode to each customer. On the CompanyCustomer record, the LanguageCode (IsoLocale) field specifies the preferred language of the customer.
The system matches automatically. During the Print Job, the system looks up the DunningTextCode using the text code assigned to the dunning level and the customer’s LanguageCode. If a matching locale exists, it generates the letter in the customer’s language. This capability allows a single dunning process code to serve customers in multiple languages without requiring separate process codes.