HRMS Mutating Custom Trigger Error

Question

Hi Gurus! In Oracle 10.7 SC HRMS, the column PERSON_TYPE_ID in table PER_ALL_PEOPLE_F was used to populate the actual person type. In releases 11+, this column was redesigned to hold just the default user_person_type for a given system_person_type. It is not maintained to reflect the true user person type. Only the table person_type_usages_f will give you the true user_person_type. (Note: column PERSON_TYPE_ID in table PER_ALL_PEOPLE_F is ONLY used by non-HR areas, such as Purchasing)
This link explains this:
http://www.aboutoracleapps.com/2008/07/difference-between-perallpeoplefpersont.html
My issue- our client upgraded from 10.7 to R12. The issue is that their custom code (a lot of it) looks at the column PERSON_TYPE_ID in table PER_ALL_PEOPLE_F to determine the actual person type.
Since my client doesnt use Purchasing (or any other modules), and they have LOTS of custom code that looks at the PERSON_TYPE_ID column, it was decided that we would just populate that column with the correct person type.
We created a trigger on the PER_PERSON_TYPE_USAGES_F table. Basically, any time a person type changes, the PERSON_TYPE_ID column is updated in the PER_ALL_PEOPLE_F table. Simple update.
The problem is, we get a mutating table error. Does anyone see why? Or how my logic is not sound? Thank you.
Trigger:
BEFORE INSERT OR UPDATE ON "APPS"."PER_PERSON_TYPE_USAGES_F" FOR EACH ROW
BEGIN
     UPDATE PER_ALL_PEOPLE_F
     SET PERSON_TYPE_ID = :new.person_type_id
     WHERE person_id = :NEW.person_id
     AND sysdate BETWEEN effective_start_date AND effective_end_date;
EXCEPTION
WHEN OTHERS THEN
RAISE_APPLICATION_ERROR(-20005, 'Trigger UPDATE_PERSON_TYPE_ID: '||SQLERRM);
END;
Application Error:
ORA-20005: Trigger UPDATE_PERSON_TYPE_ID: ORA-04091: table HR.PER_PERSON_TYPE_USAGES_F is mutating, trigger/function may not see it
ORA-06512: at "APPS.PER_ALL_PEOPLE_F_ARIU", line 228
ORA-04088: error during execution of trigger 'APPS.PER_ALL_PEOPLE_F_ARIU'
ORA-04088: error during execution of trigger 'XXMIL.UPDATE_PERSON_TYPE_ID'
ORA-06512: at "APPS.PER_PTU_SHD", line 398
ORA-06512: at "APPS.PER_PTU_UPD", line 256
ORA-06512: at "APPS.PER_PTU_UPD", line 338
ORA-06512: at "APPS.PER_PTU_UPD", line 781
ORA-06512: at "APPS.PER_PTU_UPD", line 915
ORA-06512: at "APPS.HR_PER_TYPE_USAGE_INTERNAL", line 357
ORA-06512: at "APPS.HR_PER_TYPE_USAGE_INTERNAL", line 757
ORA-06512: at "APPS.HR_PER_PEOPLE12_PKG", line 1311

Answer 1

Jason,
you should push to change your custom code.
Direct update over seeded tables is not supported by Oracle.
per_people_f updates are allowed only through front end or API, and I doubt there is an API to update the person_Type_id.
Furthermore it's way a bloody road to have the trigger, maintain it over upgrades and patches, have it firing at the right time (order in which they fire is not predictable), have data the consistent if you eventually upgrade to iREc o Benefits (when the person type could become ex-Employee.Applicant....).
I believe triggers on per_people_f are not recommendable (except for auditing). You should create your custom function and substitute any person_type_id occurrence with your custom function (or use the hr_person_type_usage_info.get_user_person_type or another if suit you well).
If you are upgrading from 10.7 to 12i, a lot of rework should be envisaged, so there should be room to create a business case to stick to oracle standard and adjust your custom code. Indeed you should check wth Oracle if what proposed is actually supported by them, this would eventually make your recomendation accepted.
my 2c.
Giuseppe
Edited by: Giuseppe on 07-Jun-2012 10:27