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 | LAUFD_KK |
| Short Description | 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 | Date ID |
| Medium | 15 | Date ID |
| Long | 20 | Date ID |
| Heading | 10 | Date |
Documentation
Use
Date on which program is scheduled to start.
Use
The additional identification and the run date together form a key by which the program run is identified.
Note
Entering run date does not actually start the run on this date. Instead, the date is used only to identify the run.
Once you have entered the parameters for a run, you can start the run. by choosing Program run -> Schedule and entering a start date.
Dependencies
The date ID is transferred to the created table entries for certain mass runs. You should be able to read the age of the table entry from it.
The date ID is used by some archiving reports. For example, if you specify an older date ID than the current date, the created table entries are entered earlier by archiving.
Supplementary Documentation - LAUFD_KK 0001
Use
The run date is a key that identifies the dunning run (together with the additional identificaton).
Supplementary Documentation - LAUFD_KK 0003
Use
The run date and the additional identification together form the key that identifies a correspondence run.
Note
The run date you enter is used only for identification purposes, and does not start the correspondence run on this date.
Once you have entered the parameters for a correspondence run, you can start the run by choosing Correspondence creation -> Schedule.. and entering a start date.
Supplementary Documentation - LAUFD_KK 0004
Definition
Date on which the program is due to run.
Use
The run date and additional identification together form a key with which the print run is identified.
Note
The run date is used only for identification purposes - it does not start the print run on this date.
Once you have entered the parameters for a print run, you can start the print run by choosing Correspondence -> Print... and entering a start date.
Supplementary Documentation - LAUFD_KK 0005
Use
The run date and additional identification together form a key identifying the clearing run.
Note
The run date is used only for identification purposes - it does not start the clearing run on this date.
Once you have entered the parameters for a clearing run, you can start it by choosing Schedule and entering a start date.
Supplementary Documentation - LAUFD_KK 2300
Use
The date of execution, together with the additional ID, forms a key for identifying a payment run.
Note
Specifying the date does not automatically start the payment run on this date; it is only for the purposes of identification.
If you have entered parameters for a payment run, you can start it by choosing Payment run -> Schedule and then enter a start date.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
