Hierarchy
INSURANCE (Software Component) SAP Insurance⤷
FS-CD (Application Component) Collections/Disbursements⤷
VINTEG (Package) Integration of Insurance Solution
Basic Data
| Data Element | CREATE_LAUFD_VI |
| Short Description | Date ID for Creation 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 ID |
| Medium | 15 | Date ID |
| Long | 20 | Date ID |
| Heading | 10 | Date |
Documentation
Definition
Specifies the date for which the program run is planned.
Use
Together with the additional ID, the execution date forms a unique key to identify the program run.
Note
Specifying the execution date does not start the mass run for this date, but is used exclusively for identification purposes.
After the parameters have been entered for a mass run, you can start this by selecting Program Run -> Schedule from the menu, and determining a start date.
Dependencies
For specific mass runs, the date ID is transferred to the created table entries. You can use this ID to read the age of the table entry.
The date ID is also used by some archiving reports. For example, if you specify a date ID that is older than the current one, the created table entries are entered earlier from archiving.
Example
History
| Last changed by/on | SAP | 20050411 |
| SAP Release Created in | 600 |
