Hierarchy
⤷ FI-CA (Application Component) Contract Accounts Receivable and Payable
⤷ FKKB (Package) Contract A/R & A/P: Central Objects
Basic Data
Data Element | SETDL_KK |
Short Description | Consideration with Dunning Level of Dunning Notice |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | 3 | DL |
Medium | 7 | DunnLvl |
Long | 10 | Dunn.Level |
Heading | 3 | DL |
Documentation
Definition
Has the effect that for an open items with a transaction indicated accordingly, the system checks whether it was posted as a charges or interest document in a dunning run. If this is the case, the dunning program treats the item as if it had the dunning level of the dunning notice in which it was created. This is important for grouping dunning notices by dunning level.
When grouping dunning notices by previous dunning level, note that the charges or interest document can receive a different dunning level as the relevant main receivable due to the later due date. In the following events you can determine that the main receivable and charges or interest document are always dunned together.
- Event 0300: Function module FKK_FKKMAVS_DL_ADAPT_0300 (dunning items receive dunning level of dunning header)
- Event 0306: Function module FKK_SPLIT_PER_MAHNS_0306 (grouping by previous dunning level)
Example
For a dunning notice with dunning level 2, you post dunning charges with main transaction 0199 and subtransaction 0199. A rule for additional receivables was defined for this external transaction, and this indicator is set in this rule.
The dunning run groups receivables by previous dunning level. The open item dunned at dunning level 2 and the dunning charges therefore appear in the same dunning group.
Note that this means that a dunning charge can have a high dunning level that it would not have reached based on the days in arrears up to this point.
If an item has already been dunned, and has a dunning level larger than zero in the dunning history, the system does not check whether the item is an additional receivable from a different dunning notice.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 464 |