I need some suggestions on how data representation in HR can me modelled in an acceptable way to the business

The scenario is that decision is made to take assignment history from a given date say '01-JAN-2006'

For eg : Employee "SMITH" would have joined the organisation on 01-Jan-2003 on a particular grade, org , job, loc etc.

When "SMITH" is created in Oracle HRMS , he has a default assignment created from 01-Jan-2003

When migrating the assignment details, I would either have to do a

1. Datetrack correction - This would reflect that the person was on the grade, loc , org right from the day he joined which will not be true in majority of the cases

2. Datetrack Update - This would reflect the exact date the current grade, loc, org was attained by the employee as opposed to the hire date. But what will happen is , there will be a skeletal assignment record in the system from "01-Jan-2003"(hire date).
This could have an impact on reporting later on.

Please let me know your thoughts on how historical representation of data can be agreed in Oracle HRMS

Thanks
Vin

Vin,

It really depends on how much historical Work Structure information they want to set up, how relevant it is to anything current etc.

We have done it here at the well known group of Hotels by:-

1. The current assignment has all the data populated correctly with the start date being when they went into the current job/org.

2. We have migrated all the historical assignment records (going back to when the employee started) but we have created a dummy org and job called 'Historical Assignment' which is what we link all these to. We then put the Job and Org which were the historical ones as an EIT hanging off the assignment (then there is no validation on them). This way we don't have to define all the historical orgs/jobs etc. but we maintain the data in the assignment records.

Vin,

I've certainly done what the venerable CB has done in the past and got away with it. These days however, a measure of caution is needed as to what things are or are not needed at specified dates. Particularly where Payroll, or God forbid, the dreaded OAB <img src="/ubbthreads/images/graemlins/buttcheeks.gif" alt="" /> rears its hideous mis-shapen head.

If there are life events that get triggered on certain changes happening within the assignment, then it is as well to find out what items on the assignment are needed in order for OAB to come up with the goods.

I would also add a cautionary tale as a PS... down here in WD, we have had no end of grief as a direct result of a decision to define all payroll calendars as starting from 01-APR-2004. Let us not confuse this with the payroll effective start date, by the way - which is 01-JAN-1951, as per the accepted wisdom. We were doing fine with loading assignments, very little historical info appart from some descriptive flexfield bits and pieces (ie all the real gubbins in the current or latest assignment entry) - then we tried to load balances. All hell broke loose because it tried to use a date for _ASG_ITD balance dimensions that equated to the earliest date at which the assignment had the payroll. in some cases that was earlier than 01-APR-2004 - before the calendars started - UH-OH! <img src="/ubbthreads/images/graemlins/suicide.gif" alt="" /> Not only that, but some types of payment were meant to be 'generated' by OAB life events - where the 'life-event occurred date' was earlier than 01-APR-2004... UH-OH! again... <img src="/ubbthreads/images/graemlins/suicide.gif" alt="" /> <img src="/ubbthreads/images/graemlins/suicide.gif" alt="" /> where the latest assignment entry fell before 01-APR-2004 we had to 'engineer' an extra historical entry for the assignment, as though the payroll had been set on 01-APR-2004. We also had to 'massage' the life-event occurred dates to be beyond 01-APR-2004 as well. If we didn't, then the BENMANGLE process would fall on its digital derriere after the traditional 20 failure limit has been exceeded.

Good luck anyway - if you get any other issues, remember to post 'em here so's we can have a good laugh!

CT

I fell upon your same problem 2 or 3 years ago when I tried to load historical absences with start dates before the first payment date of the payroll calendar. Where absence types are associated with elements and the link criteria wants a payroll then UH-OH indeed. I too had to 'manufacture' some payroll periods in PER_TIME_PERIODS to get them in.

In answer to Vin's question, I would look at what would require history to be there and be accurate, and weigh that up against how much effort it would take to put there. I would imagine in most cases the client would see sense if the costs were so high to migrate assignment/people history and the supporting reference data that it became unjustifiabe.

Rob