Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-HR (Application Component) Cross-Application Objects in HR⤷
BP (Package) Cross-Application Objects in HR
Basic Data
| Data Element | ENDDA |
| Short Description | End Date |
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 | TO_DATE | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 1 | - |
| Medium | 10 | End Date |
| Long | 15 | End Date |
| Heading | 10 | End Date |
Supplementary Documentation - ENDDA 0000
Use
You can use this field to limit the selection of records offered by the system. This applies to all valid functions except for 'Create' and 'List'. In the case of 'Create', the value is transferred to the corresponding field in the next screen.
When entries are made in one, two or no date fields on the menu screen, the system suggests records using a particular interval which is determined for each infotype in table T582A.
Supplementary Documentation - ENDDA 0001
Use
This end date is the end date of the leave year. The start and end date of the leave year define the period for which the employee is entitled to leave.
Supplementary Documentation - ENDDA 0002
Use
The end date is set automatically by the system and cannot, therefore, be changed.
The end date depends on the data stored in this infotype. The following data affects the end date:
- the pregnancy notification date
- the expected date of delivery
- the actual date of delivery
- the latest end date of a recorded absence
These functions ensure that all absences of a particular record are within the validity period of the record.
Supplementary Documentation - ENDDA 0003
Use
End date for selecting data from the "Recurring Payments and Deductions" infotype.
Supplementary Documentation - ENDDA 0004
Use
End date for selecting data from the "Once-Only Payments" infotype.
Supplementary Documentation - ENDDA 0005
Use
End date for selecting data from the "Company Insurance" infotype.
Supplementary Documentation - ENDDA 0007
Use
The end date for this infotype must always be in the same year as the start date of the record. The data record is usually valid up to December 31.
Supplementary Documentation - ENDDA 0101
Use
The cumulation rule for averages is valid until this date.
Supplementary Documentation - ENDDA 0103
Use
Validity periods are not supported at present, only key dates (T558A-BEGDA = T558A-ENDDA).
Supplementary Documentation - ENDDA 0118
Procedure
Germany only.
Supplementary Documentation - ENDDA 0119
Procedure
The amount of child allowance has to be recalculated whenever the number of eligible children changes. You can determine the correct start and end date by using function key 8 in infotype 0118. You must create records in infotype 0119 for all the periods displayed here.
Supplementary Documentation - ENDDA 0120
Use
Germany only.
Supplementary Documentation - ENDDA 0194
Definition
This field contains the end date of the garnishment document at hand.
As delivered, the standard system uses 12/31/9999 as the default date for this field. We recommend that you retain this date as the end date for all garnishment documents in your system.
Supplementary Documentation - ENDDA 0195
Definition
This field should contain the effective end date of the garnishment order. Depending upon the repayment schedule established by the court, the end date of the order may coincide with each payroll period, or it may occur on a less frequent basis.
Procedure
In this field, enter the date on which processing of the garnishment order should end. Since a distinct garnishment order should exist for each payment, the date you enter here will depend upon the date you remit payments to the vendor.
The default entry for this field is the current date.
Supplementary Documentation - ENDDA 4545
Use
The end date must come after the repayment end date for the loan. If the repayment takes longer than expected, you must adjust the end date. If you do not adjust the end date, the system cannot run the payroll for the employee correctly.
Procedure
Examples
Dependencies
After the loan has been repaid in full, you can enter the end date for the loan in this field. This shortens the payroll runtime.
Supplementary Documentation - ENDDATUM 0120
Supplementary Documentation - ENDDATUM 0220
Use
Use this field to identify when the relationship between two objects ends. (By moving objects, you are creating new relationships between objects in a structure.)
The system automatically inserts a default maximum date. However, you may overwrite it. To do so:
- type in a date
Supplementary Documentation - ENDDATUM 0510
Use
By entering a period in these fields, you select the objects with which you want to work.
All of the objects are selected that are valid at any point in time within the period that you specify.
Procedure
To specify a period,
- Enter the date yourself
or - Press F4 and then choose a date from the calendar.
NOTE: The system also uses the specified date in the current mode as a default value for the validity period.
Supplementary Documentation - ENDDATUM 0511
Use
Use the Selection period fields to choose the objects you want to work with in Quick Setup, by naming a selection period. A selection period consists of a start date and end date. All objects that are valid at ANY point during the selection period are available in Quick Setup.
Procedure
Use this field to enter an end date, for the selection period. To do so:
- type in an appropriate date
Supplementary Documentation - ENDDATUM 0520
Use
In this field, enter the date as of which the root organizational unit ceases to be valid. The system automatically enters the high date in this field.
You can only change this date by using the "Delimit" function.
Supplementary Documentation - ENDDATUM 0525
Use
Use this field to setup a default validity period for Quick Setup. The default will be applied within Quick Setup only, and you will always have the opportunity to overwrite it.
Procedure
The system automatically inserts its default maximum date. You may enter a different date. To do so:
- manually type in a date, or
- press F4 to select from a calendar (double click on the desired date)
- NOTE: If you enter a default end date that occurs sooner than the system default maximum date, your date is only applied to infotype records.
Supplementary Documentation - ENDDATUM 0535
Use
The Validity period fields enable you to specify the period for which the relationship between the job and position is valid. To specify the period,
- Enter a date yourself
or - Press F4 and choose the required date from the calendar.
Supplementary Documentation - ENDDATUM 0556
Use
In CREATE mode, use this field to identify when the relationship between two objects should end.
The system automatically inserts a default maximum date. You may enter a different date. To do so:
- manually type in a date, or
- press F4 to select from a calendar (double click on the desired date)
NOTE: The end date assigned to the relationship record cannot exceed the end date assigned to either object involved.
In CHANGE mode, use this field to delimit the relationship, so that it ends sooner than is currently stated. To do so:
- typeover the date currently shown
Supplementary Documentation - ENDDATUM 0558
Use
In this field, enter a new end date for the object or relationship you have already chosen. In order to do this,
- Enter a date yourself
or - Press F4 and choose a date from the calendar.
Supplementary Documentation - ENDDATUM 0560
Use
Use this field to identify when the relationship between a position and a holder of a position ends. The system automatically inserts the default maximum date, but you may overwrite it. To do so:
- type in a date
Supplementary Documentation - ENDDATUM 0570
Use
When objects are renamed, you use these fields to enter the date as of which the object's new code or name is valid. The system automatically enters the high date in these fields, which you can of course overwrite.
To enter data in the field,
- Enter a date yourself
or - Press F4 and choose a date from the calendar.
Supplementary Documentation - ENDDATUM 0590
Use
In CREATE mode, use this field to identify the date when the relationship between two objects ends. (A Relationship infotype record is automatically created when you establish new objects in Simple Maintenance and Graphics.)
The system automatically inserts a default maximum date. You may overwrite it. To do so either:
- manually type in a date, or
- press F4 to select from a calendar (double click on the desired date)
Supplementary Documentation - ENDDATUM 0591
Use
In CREATE mode, the system automatically inserts the maximum system date, for example, 12.31.9999. You cannot set a different end date for objects using this field. If you want to set a different end date, you must use the Delimit options.
In DISPLAY mode, the system automatically completes the field, and it may not be edited.
Supplementary Documentation - ENDDATUM 0595
Use
In CREATE mode, the system automatically inserts the system default maximum date, for example, 12.31.9999. You cannot enter a different date when working with objects. You may only change the end date using the Delimit options available.
Supplementary Documentation - ENDDATUM 0701
Use
End date up to which a position (or organisational unit) is assigned.
Procedure
Examples
Dependencies
Supplementary Documentation - ENDDATUM 0702
Use
End date up to which the Wage element is assigned to the position or job.
Procedure
Examples
Dependencies
Supplementary Documentation - ENDDATUM 1000
Use
The New delimit date field contains a date that identifies the end of the period when an object or infotype is valid. The field is defaulted to the default maximum date set for your system (often 31.12.9999).
Procedure
Use this field to identify the new end date for the objects/infotypes you are working with. To do so:
- manually type in an appropriate date or
- press F4 to select from a calendar (double click on the appropriate date)
Supplementary Documentation - ENDDATUM 2000
Use
In CREATE mode:
The system automatically inserts the default maximum date. You cannot edit this date.
In CHANGE mode:
You cannot edit this date.
NOTE: To terminate an object before the end date shown, use the delimit options. (See Windows help.)
Supplementary Documentation - ENDDATUM 2001
Use
In CREATE mode:
Use this field to identify the date when an infotype record ceases to be valid. The system automatically inserts a default maximum date, but you may overwrite it.
To complete the field either:
- manually type in a date, or
- press F4 to select from a calendar (double click on the appropriate date)
In CHANGE mode:
You cannot edit this date.
NOTE: To terminate an infotype record before the end date shown, use the delimit options. (See Windows help.)
Supplementary Documentation - ENDDATUM 5100
Use
In CHANGE, DISPLAY, LIST and DELETE modes:
Use the field to select the objects or infotype records you want to work with, by naming a timeframe.
Objects or infotypes that are valid at any point in the stated period are selected.
NOTE: The system also considers the plan version, object abbreviation, object name, and infotype status, when records are selected.
In CREATE mode:
The validity period shown here does NOT determine the validity period applied to new objects or infotype records. You apply validity periods to objects and infotypes in the respective infotype windows.
Supplementary Documentation - ENDDATUM 7001
Use
End date for search for room.
The end date of the period in which the system searches for a vacant and/or booked room. An entry is not obligatory if you only want the system to search for an individual day (-> Start date).
Procedure
Please use the correct date format.
Examples
24.09.2015
Dependencies
Supplementary Documentation - ENDDATUM 7002
Use
Enter the end date of the period relevant to the search for a room or business event. You can leave the field empty if it is a one-day event.
If business event data is displayed, this will be the date of the business event.
Supplementary Documentation - ENDDATUM 7003
Use
End of event
When rebooking and copying events, the new end date in the search for the period of the rebooked or copied event is entered here.
If you do not enter an end date, the search is only conducted on the start date.
Supplementary Documentation - ENDDATUM 7004
Use
End of selection period for events.
Procedure
Examples
24.09.2015
Dependencies
Supplementary Documentation - ENDDATUM 7005
Use
Date up to which the equipment must be available.
Procedure
Examples
Dependencies
Supplementary Documentation - ENDDATUM 7006
Use
Deletion of Room Reservations Planning object can be made in two ways. On the one hand, an object can be deleted completely from the database, for example, because it was only created for testing purposes or incorrectly. The second possibility is to limit the validity period of an object, for example, if a room is no longer available because of reconstructions as of a certain date. In the first case the Delete field must be marked on the screen, in the second case, the last validity day must be entered in this field.
When deleting Room Reservations Planning data, the object which is to be deleted must be specified. It is possible to enter the first letters of the object text via RP-Plan matchcodes so that the system displays all objects for selection whose designation starts with these letters. The object ID of the object can also be entered directly.
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 19980909 |
| SAP Release Created in |
