Benutzen sie die linke oder die rechte Maustaste, um zur jeweils vorherigen bzw. nachfolgenden Änderung zu gelangen.
erste | letzte ![]() |
| Änderungen von: | |
| bis: | |
| Typ: | |
erste | letzte ![]() |
In HR-Expert, an employee's entries can be historically stored saved in a historized manner in a timeline. However, there are a few basic things to keep in mind must be observed so that no data records are accidentally overwritten. HR-Expert offers the administrator some a good deal of automatic support, but does not always question the accuracy correctness of the data entered. The principle isapplies: "The administrator is (almost) always right.". I
Rule Nrno. 1:
It is always recommended to always create a new record by clicking on "New" instead of rather than editing an existing one.
Rule Nrno. 2:
The data "Valid from" and "Valid tountil" dates are essential decisive for the storage of a dataset record such as group assignment, salary entries, bank accounts, primary residential home address, employment entries, etc.
If HR-Expert has to make a delimitation due to delineation because of a time overlap (conflict), the last data most recently entered record entered is always preferredgiven preference. For a better understanding, the following graphic describes the priority principle.
This graphic shows how entries with different validity periods relate to each otherone another.
Important! Absolutely nothing can be saved before the start of validity of the employee filerecord, defined in the date "Valid from" in date on the master Master data tab. Each Every entry with an earlier start of validity is automatically corrected to this date (entry D in the graphic).
State 1: Entry Entry A begins, for examplee.g., with the "Valid from" of the master data.
State 2: The The HR admin creates B with a "Valid from" during the validity period of A. A and B both have a "Valid tountil" of infinity.
When you savesaving, the system now automatically breaks down resolves the time overlaps between of the two data records. In accordance with According to the principle of prioritizing giving priority to newer data records, the original entry A is thus shortened in time so that it ends with at the start beginning of B. The system then saves the new data records automatically.
State 3: Displays Shows the result after the automatic correction by the system.
State 4: The The HR admin creates C with a validity before that of B. B and C both have a "Valid tountil" of infinity.
Again, Again there are temporal time overlaps that , which are not allowed permitted and are automatically resolved by the system when you save saving according to the principle of prioritizing new data giving priority to newer records.
State 5: Displays Shows the result after saving. The system has corrected the "valid toValid until" from of A to one day before the "valid Valid from" from of C. Entry C is valid until further notice ("Valid tountil" infiniteinfinity).
State 6: The HR admin creates entry D with a date before the validity date of the employee master record.
In In addition to the time overlap with all previous entries, this also results in the error situation that the validity begins before the validity of the employee's validity. The system corrects the situation when saving as follows when saving:
The result is a single entry D that , which extends over the entire validity period and deletes erases all previous entries.
| Mime Type | text/xml | ![]() | text/xml |
| Datei-name | ![]() | ||
| Größe (in Bytes) | 4374 | ![]() | 4312 |
|
Version 3 von Inge Lederhofer
am 11.12.18 12:59:28 Name: Time limitation and Historisation Variante: main - en Status: Veröffentlichung | ![]() |
Version 4 von Gabriel Gruber
am 17.10.26 18:16:23 Name: Time Limitation and Historization Variante: main - en Status: Veröffentlichung |