Validity periods identify the lifespan of an object or infotype record – or the period of time when an object or infotype record ‘exists’.
You must apply validity periods to every object and infotype you create. You do so so that your organizational plan can reflect the many changes that occur within your company. You then have a fluid or dynamic view of your company, rather than a static record.
A validity period consists of a start date and an end date. An object or infotype record ‘exists’ for the range of time specified by the two dates.
Validity periods for objects
When you create objects, the system automatically proposes either the current date as the start date, ot the last start date you used in your work session. For the end date, the system proposes your system default date – usually 31.12.9999. You may enter a different start date, but you cannot enter your own end date.
Once an object’s validity period is established, you can only change it using the delimit function.
Validity periods for infotype records
The validity period you assign to an object limits the validity period you may assign to any infotype records appended to the object. Infotype record validity periods cannot exceed the validity period applied to the object itself.
When you work with infotypes, the system automatically proposes the current date as the start date. For the end date, the system uses the end date defined for the object you are working with.
You may enter a different start date or end date, provided the:
Once you have saved the start date of an infotype record, you cannot change it. You can change the end date by using the delimit function.