Hierarchy
FI-CA (Software Component) FI-CA⤷
FI-CA (Application Component) Contract Accounts Receivable and Payable⤷
FKKB (Package) Contract A/R & A/P: Central Objects
Basic Data
| Data Element | RHYTH_KK |
| Short Description | Dunning frequency in days |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUM03 | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Dun. freq. |
| Medium | 15 | Dunning freq. |
| Long | 20 | Dunning frequency |
| Heading | 3 | DF |
Documentation
Definition
Minimum number of days that have to have elapsed since the date of issue of the last dunning notice, so that another dunning notice can be created for the items in the original notice.
Dependencies
You have to specify either a dunning frequency or a number of days in arrears.
In Customizing, you can define for a dunning procedure that the days in arrears and the dunning frequency are to be calculated in accordance with a factory calendar.
Use
The specification of a dunning frequency prevents a customer receiving two dunning notices in a short space of time. This can happen if the customer has several open items that are due shortly after each other.
The basis for determining the dunning frequency is the highest dunning level of all items contained in a dunning notice.
Example
For a dunning procedure, 10 days are defined as the days in arrears for dunning level 1, and 20 days for dunning level 2.
The customer account contains two open items with due dates 1/1 and 1/5.
If you do not specify a dunning frequency, a dunning notice is created at dunning level 1 for the first open item on 1/11, and a further dunning notice for both items at dunning level 1 on 1/16, since the second item has not reached the days in arrears for the second dunning level.
The second dunning notice at dunning level 1 is prevented if you specify a dunning frequency of 10 days for dunning level 1. In that case, a second dunning notice at dunning level 2 is created on 1/21, since the days in arrears for dunning level 2 have been reached.
If you only specify a dunning frequency of 10 days for dunning level 2, and do not specify days in arrears, in this case the second dunning notice at dunning level 2 is also created on 1/21.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
