Hi Rafik,

Try checking out this table (I think it was introduced in one of the later releases, I am on 21A), PER_EMPL_OFFER_HR_TRACK. This table stores the value of the offer assignment id along with the action's performed on this table and the resultant assignment id's generated due to the action. Also, on the IRC_OFFERS there is a ASSIGNMENT_OFFER_ID which can be joined with the per_all_assignments_m table to capture the assignment details. Depending on how your data is being stored and processed, you can potentially get the subsequent assignment (pending worker) by using the DISTINCT ROW_NUMBER () OVER(Partition By) function or RANK. Once you have all the joined data you will be able to see the full lifecycle of an employees service from Candidate > Offer > Pending > Employee. I haven't looked too deep into the PER_EMPL_OFFER_HR_TRACK table but it does pull up results and captures the data you are looking for.

Hope this helps in some way, not really a full blown solution but some sort of workaround. If you have SQL knowledge and know the tables well you should be able to get what you need with these few tables. I've built out something here on my end with these tables based on business need, so I'm sure you'll be able to get something out of it.

p.s - If you've implemented ORC and are utilizing the module, the PER_ALL_ASSIGNMENTS_M table and PERIOD_OF_SERVICE_TABLE will have new types starting with "O" for Offer.

Thanks!

Sergio

Hi Folks,

Regarding Above PER_EMPL_OFFER_HR_TRACK Still gives Duplicate Records?