none
ID Joining rule from Temp to Perm RRS feed

  • Question

  • Hi,

    I was wondering if anyone else had this Issue with FIM/MIM

    You have 2 types of Employees

    1. Temporary

    2. Permanent

    So when a temporary employee becomes Permanent their Employee number becomes 2 Holograms to us thru our HR system, instead of just 1 ID with an updated contract.

    We are also managing the Temps and Permanent thru Different MA's, as there is a different flow to each contract.

    What is the Best way to overcome this, as our employee ID is the requirement and based on the Join rule.

    Friday, January 13, 2017 7:01 AM

All replies

  • It sounds like you are in the classic scenario of your unique identifier changing based on employment type.  How you solve this is by finding unique data on the Temp HR record that the Permanent HR record would have, then making a join rule on the Permanent HR MA.  HR may have data that they are not exposing to you (like drivers license number) that you could pull in and just join on.  This usually takes sitting down with HR and finding a better business process of handling people and explaining the huge problems if it is not solved - duplicate scenario and security risk.

    Another solution is to build an advanced join (rules extension) that looks at several attributes both records would share -- last name, middle name, manager, department.  Basically try to take enough common attributes to build something that would indicate uniqueness.

    If the above are not a possibility, you could hold off on provisioning ALL Permanent employees until a manager verifies/signs off on that record not already existing as Temp or if it is, pick out the temp record.  You could push this down as an HR process.

    Best,

    Jeff Ingalls

    • Proposed as answer by Leo Erlandsson Friday, January 13, 2017 3:08 PM
    Friday, January 13, 2017 2:31 PM