To maintain employee data effectively Oracle HCM is using a mechanism called date tracking. The main motive behind the date track mode is to maintain past,present and future data effectively.
The various update date track modes are:
CORRECTION : Over writes the data. No history will maintain.
UPDATE : Keeps the history and new change will effect as of effective date
UPDATE_CHANGE_INSERT : Inserts the record and preserves the future
UPDATE_OVERRIDE : Inserts the record and overrides the future
Action: Created Employee # 22 on 01-JAN-2012
The record in PER_ALL_PEOPLE_F is as shown below.
Effective Start Date | Effective End Date | Employee Number | Marital Status | Object Version Number |
01-JAN-2012 | 31-DEC-4712 | 24 | 2 |
Action: Updated record in CORRECTION mode
Effective Start Date | Effective End Date | Employee Number | Marital Status | Object Version Number |
01-JAN-2012 | 31-DEC-4712 | 24 | Single | 3 |
Action: Updated record in UPDATE mode effective 01-JUN-2012 and Marital Status = Married
Effective Start Date | Effective End Date | Employee Number | Marital Status | Object Version Number |
01-JAN-2012 | 31-MAY-2012 | 24 | Single | 4 |
01-JUN-2012 | 31-DEC-4712 | 24 | Married | 5 |
Action: Updated record in UPDATE mode effective 01-SEP-2012 and Marital Status = Divorced
Effective Start Date | Effective End Date | Employee Number | Marital Status | Object Version Number |
01-JAN-2012 | 31-MAY-2012 | 24 | Single | 4 |
01-JUN-2012 | 31-AUG-2012 | 24 | Married | 6 |
01-SEP-2012 | 31-DEC-4712 | 24 | Divorced | 7 |
Action: Updated record in UPDATE_CHANGE_INSERT mode effective 01-MAR-2012 and Marital Status = Living Together
Effective Start Date | Effective End Date | Employee Number | Marital Status | Object Version Number |
01-JAN-2012 | 29-FEB-2012 | 24 | Single | 8 |
01-MAR-2012 | 31-MAY-2012 | 24 | Living Together | 9 |
01-JUN-2012 | 31-AUG-2012 | 24 | Married | 6 |
01-SEP-2012 | 31-DEC-4712 | 24 | Divorced | 7 |
Action: Updated record in UPDATE_OVERRIDE mode effective 01-AUG-2012 and Marital Status = Divorced
Effective Start Date | Effective End Date | Employee Number | Marital Status | Object Version Number |
01-JAN-2012 | 29-FEB-2012 | 24 | Single | 8 |
01-MAR-2012 | 31-MAY-2012 | 24 | Living Together | 9 |
01-JUN-2012 | 31-JUL-2012 | 24 | Married | 10 |
01-AUG-2012 | 31-DEC-4712 | 24 | Divorced | 11 |
Delete Date Track Modes
The various delete date track modes are
ZAP : wipes all records
DELETE : Deletes current record
FUTURE_CHANGE : Deletes current and future changes.
DELETE_NEXT_CHANGE : Deletes next change
Element Entry records are shown below.
Effective Start Date | Effective End Date | Element Entry Id | Object Version Number |
01-JAN-2012 | 12-OCT-2012 | 129831 | 3 |
13-OCT-2012 | 19-OCT-2012 | 129831 | 5 |
20-OCT-2012 | 31-DEC-4712 | 129831 | 6 |
Action: Delete record in ZAP mode effective 14-JAN-2012
No rows
Action: Delete record in DELETE mode effective 14-OCT-2012
Effective Start Date | Effective End Date | Element Entry Id | Object Version Number |
01-JAN-2012 | 12-OCT-2012 | 129831 | 3 |
13-OCT-2012 | 14-OCT-2012 | 129831 | 6 |
Action: Delete record in FUTURE_CHANGE mode effective 14-JAN-2012
Effective Start Date | Effective End Date | Element Entry Id | Object Version Number |
01-JAN-2012 | 31-DEC-4712 | 129831 | 4 |
Action: Delete record in NEXT_CHANGE mode effective 14-JAN-2012
Effective Start Date | Effective End Date | Element Entry Id | Object Version Number |
01-JAN-2012 | 19-OCT-2012 | 129831 | 4 |
20-OCT-2012 | 31-DEC-4712 | 129831 | 6 |
No comments:
Post a Comment