SAP ABAP Data Element MLAUFD_KK (Dunning Date ID)
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
⤷ FI-CA (Application Component) Contract Accounts Receivable and Payable
⤷ FKKB (Package) Contract A/R & A/P: Central Objects
Basic Data
Data Element | MLAUFD_KK |
Short Description | Dunning Date ID |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DATUM | |
Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | DUNN_RUN_DATE | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Dun. Date |
Medium | 15 | Dunning Date ID |
Long | 20 | Dunning Date ID |
Heading | 10 | Dun. Date |
Documentation
Definition
Date of program run.
If some customers have not replied to a balance notification, you can start a dunning run for the run with which the balance notifications were created. This dunning run triggers the sending of the balance notifications again. To do this, you have to create a selection of contract accounts in transaction FPBN and perform a correspondence run for this selection of contract accounts only (transaction FPCO0026). On printing, the run date and run ID of the dunning run for the original items is entered in the table of the balance notifications created (FPBN).
Use
Together with the additional ID, the run date forms a key for identifying the program run.
Dependencies
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 473 |