|Have you tried OracleappsHub in ipad/iphone/smart Phone? Don't wait. try it today|
Irrespective of installation , whether it's full or shared, it is important to understand the "date tracking" concept that oracle utilizing in HRMS.
Date Tracking is a means of maintaining a history of changes to personnel records. It applies to the following parts of a person's record in Oracle HR: People, Assignments. Each of the areas that are date tracked within a record are date tracked independently.
We can 'date track' by setting an Effective Date. An effective date is the date at a particular point in time when a person's record is effective. When you set an effective date for your work, DateTrack ensures that only information effective on that day is used for any processing,
validation, enquiries and reporting you carry out.
Lets understand this in this simple diagram , which is consider as timeline of a personal record.
It shows how the person's Status has changed over time to reflect their changing circumstances. As the changes are made in Oracle, the system keeps a record of each change. These records can be thought of as different slices - or different pages in a file that show each change. Date tracking allows you to visit each slice or page at any time. If you set the effective date to 17 July 2001.. for example, the record would show that this individual is Married. Reset back to today and the marital status would show as divorced.
Take a another example for employee Assignment
In this example the assignment record shows how this person's Position changes over time.
When this person originally started in company , their position was Programmer 1. Over time their position get changed and Oracle keep maintaining the history of this. In addition, this individual has been told that they have a new position which will take effect as of the 01 Jan 2008. Using date tracking you can record that this position change will take effect in advance of it happening - simply by setting the Effective Date to 01 Jan 2008 and making the change. Until that date actually arrives, the position will still show as the current one.
If there are future dated entries in the system (as in the assignment example above), and you wish to record a new change that will occur prior to the forthcoming change then Oracle will prompt you to Insert the record as part of the update. In this scenario, Oracle will insert a new 'slice' of history up to the date of the future change only.
In above diagram example, a future dated change was entered to record that this individual's position is changing from Programmer Level 3 to Analyst on 1 Jan 2007. However, subsequent to this change being entered and saved in Oracle, this person will have a new supervisor from July 1st - i.e. before taking up the new position. If you now record the new supervisor change, Oracle will prompt you to 'insert' it. As such, a further slice of history will exist from 1 July 2007 to 1 Jan 2008.
Which columns in Oracle hold these values
To control these date tracking rows, every DateTracked table must include these columns:
- EFFECTIVE_START_DATE DATE NOT NULL
- EFFECTIVE_END_DATE DATE NOT NULL