Hierarchy
FINBASIS (Software Component) Fin. Basis⤷
FIN-FSCM-COL (Application Component) Collections Management⤷
UDM_STRATEGY (Package) Collection Strategy, Rule, Basic Rule
Basic Data
| Data Element | UDM_BR_DAYS_DUNNING |
| Short Description | Days Since Last Dunning Notice |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | UDM_NO_OF_DAYS | |
| Data Type | INT4 | 4-byte integer, integer number with sign |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 11 | |
| 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 | 0 | |
| Medium | 0 | |
| Long | 28 | Days Since Last Dunning |
| Heading | 0 |
Documentation
Definition
If the number of days specified has passed since the last dunning notice without the customer reacting, the condition of this rule is fulfilled.
A customer reaction can be documented, for example, by payment of the dunned amount, by a promise to pay, or by a dispute case. The system recognizes the customer reaction from the fact that the amount to be collected for the dunned invoice is zero.
Use
Dependencies
The key date for the determination of days since the last dunning notice is the date of the worklist item that is specified for the simulation of a strategy or for the generation of the worklist (as validity date).
The number of days specified here can be different to the number of tolerance days after sending the dunning notice specified in the strategy in order to scale the valuation.
Example
5 days without reaction - 2 points
10 days without reactio - Further 2 points
15 days without reaction - Further 4 points
History
| Last changed by/on | SAP | 20050520 |
| SAP Release Created in | 600 |
