Records are not normally deleted from HR. We will use a SQL minus to detect missing records. See also [YNR:HR Delete Connector]
Select HR_ID, 'Y' from OIMuser where source_of_identity = 'HR' and deleted_in_hr != true
minus
Select HR_ID, 'Y' from HR view
This query will return all rows in OIM having an HR_ID that is not present in HR.
What should happen to OIM records when deleted_in_hr = Y
It is may be that a record deleted in HR should be deleted from OIM too. We need to create an [error report of records where deleted_in_hr] = Y. The cases to consider are
OIM record is linked to a valid student record and source_of_identity = SIS. This case should never occur. It is wrong for HR to delete a student. The student provisioning connector will rewrite any changes to a student record. If the record is deleted the student provisioning connector will run the pl/sql procedure that creates or updates student information to correct the HR record. If a new HR record is created the rewrite function should update the OIM HR_person_id to reflect the new link. Records with Source of identity = SIS will not get the deleted_in_hr flag set.
OIM record has source_of_identity = HR or UNK. The user should always use the Magic Tool to merge duplicates. Recommendation is for functional area to remove the delete functionality from the Oracle HR system which would require the user to use the Magic Tool to merge duplicate records. The majority of duplicate records that are discovered are for Contact records. Magic Tool must delete the record from the HR system in order for
Scenarios for Deleting Records from HR:
Duplicate Records - as we thought this would be the most common reason to delete HR records. The majority of duplicates created are for Contacts which will be part of the OIM database since they have UPI's and HR_People_ID's. Contacts do not have NETID's.
Person Terminates Before Starting - the only other circumstance is if a user was in the process of entering a record and staffing advised that the person is no longer coming. Users could simply delete the record. Business process will be changed to support OIM by advising users that they must complete the entry transaction and then terminate the person.
OIM Magic Tool - during the merging of duplicates through the tool, the OIM Magic tool will delete the duplicate record on the source system. If Magic tool does the deletes AND contacts will be in OIM, Chuck suggested that perhaps he could remove the users ability to delete records via Oracle (possibly controlled by the Responsibility level within Oracle (Chuck will research). Obviously the report would still be a requirement to ensure that all deletes are occurring correctly.
SIS / Banner
See SIS Connectorsfor details. Once the OIM user is updated by the SIS delete connector the access policy will trigger the REVOKE event on the the student resource to HR. The GTC will do nothing. The HR system will continue to use the legacy 'ALUMNI' view to trigger changes to the person type.
The provisioned HR Keys resource instance is unaffected.
Netid and Email Alias Trusted Source Connectors
In phase 1, netids and email aliases will be provided by trusted source reconciliation.
The netid system will continue to be authoritative as to the association of netid to UPI. The reconciliation will be based on SQL that will return a null if a netid has been removed from a UPI. When does that happen?
The current online directory system will continue to be authoritative as to the association of primary email alias to UPI. The reconciliation will be based on SQL that will return a null if an email alias has been removed from a UPI. When does that happen?
