Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-BK (Application Component) Bank⤷
BF (Package) FI Cross-application Objects
Basic Data
| Data Element | LAUFD |
| Short Description | Date on Which the Program Is to Be Run |
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 | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Date |
| Medium | 15 | Run On |
| Long | 20 | Run Date |
| Heading | 10 | Run On |
Documentation
Definition
The run date is used for identifying the parameters. It is the date on which the program is to be carried out as planned. However, a program run at an earlier or later date is also possible.
Supplementary Documentation - LAUFD 0030
Use
The following entries are possible in Switzerland:
0 - output in TemSe file (diskette format)
2 - output in the file system (diskette format)
Supplementary Documentation - LAUFD_EXEC_SC0001
Use
Together with the additional ID, the execution date forms a key for identifying the dunning run.
Supplementary Documentation - LAUFD_EXEC_SC0003
Use
Toegther with the additional ID, the execution date forms a key for identifying the correspondence run.
Note
Specifying the execution date does not cause the system to start the correspondence run on this date, and it is used exclusively for idenfitication.
After you have entered the parameters for a correspondence run, you can start it by selecting Correspondence Creation -> Schedule and determining a start date.
Supplementary Documentation - LAUFD_EXEC_SC0004
Definition
Date on which the program run is scheduled.
Use
Together with the additional ID, the execution date forms a key for identifying the print run.
Note
Specifying the execution date does not mean that the system starts the print run on this date, and it is used exclusively for identification.
After you have entered the parameters for a print run, you can start it by selecting Correspondence -> Print and determining a start date.
Supplementary Documentation - LAUFD_EXEC_SC0005
Use
Togther with the additional ID, the execution date forms a key for identifying the clearing run.
Note
Specifying the execution date does not cause the system to start the clearing run on this date, and it is used exclusively for identification.
After you have entered the parameters for a clearing run, you can start it by selecting Schedule and determining a start date.
Supplementary Documentation - LAUFD_EXEC_SC2300
Use
Together with the additional ID, the day of execution forms a key for identifying the payment run.
Note
Specifying the day does not mean that the system starts the payment run on this day, and it is used exclusively for identification.
If you have entered parameters in a payment run, you can start it by selecting Payment Run -> Schedzle and determining a start date.
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.
Supplementary Documentation - LAUFD_M 0001
Use
With the started report payment medium runs are compiled. The run date can be specified as follows:
- If the parameter remains empty, the current system date is used.
- If a date is predefined then this is used (this option is not recommended in variants).
- Using the selection variants in variant maintenance the run date can be calculated dynamically.
Supplementary Documentation - LAUFD_REVE_SC0001
Use
Toegther with the additional ID, the execution date forms a key for identifying the dunning run.
Supplementary Documentation - LAUFD_REVE_SC0003
Use
Together with the additional ID, the execution date forms a key for identifying the correspondence run.
Note
Specifying the execute date does not mean that the system starts the correspondence run on this date, and it is used exclusively for identification.
After you have entered the parameters for a correspondence run, you can start it by selecting Correspondence Creation -> Schedule and determining a start date.
Supplementary Documentation - LAUFD_REVE_SC0004
Definition
Date on which the program run is scheduled.
Use
Together with the additional ID, the execution date forms a key for identifying the print run.
Note
Specifying the execution date does not mean that the system starts the print run on this date, and it is used exclusively for identification.
After you have entered the parameters for a print run, you can start it by selecting Correspondence -> Print and determining a start date.
Supplementary Documentation - LAUFD_REVE_SC0005
Use
Together with the additional ID, the execution date forms a key for identifying the clearing run.
Note
Specifying the execution date does not mean that the system starts the clearing run on this date, and it is used exclusively for identification.
After you have entered the parameters for a clearing run, you can start it by selecting Schedule and determining a start date.
Supplementary Documentation - LAUFD_REVE_SC2300
Use
Toegther with the additional ID, the day of execution forms a key for identifying the payment run.
Note
Specifying the day does not mean that the system starts the payment run on this day, and it used exclusively for identification.
If you have entered parameters for a payment run, you can start it by selecting Payment Run -> Schedule and determining a start date.
History
| Last changed by/on | SAP | 19980909 |
| SAP Release Created in |
