Close Enrollment Gives Error: "APP-PAY-07155: THE HR OBJECT IS INVALID" (Doc ID 266929.1)

Last updated on DECEMBER 09, 2016

Applies to:

Oracle Advanced Benefits - Version 11.5.0 and later
Information in this document applies to any platform.

Symptoms

 When election is saved in the second life event or default enrollment is called during close enrollment, the process errors with a message

"APP-PAY-07155: THE HR OBJECT IS INVALID"
Cause: The HR Object which is attempted to be locked is inconsistent with the corresponding object in the HR Schema
Action: Retry the action with the correct object version number



The PYUPIP trace will show trace that it is selecting the same contact twice, indicating that one contact has two relationship types, each with the Personal Relationship flag checked:

 

Entering: ben_ELIG_CVRD_DPNT_api.update_ELIG_CVRD_DPNT 10
per in ler id 317623 9745
elig_dpnt 19945 9745
dt 9745

Entering: ben_pdp_shd.lck 5
Fail in ben_PRTT_ENRT_RESULT_api.update_ENROLLMENT at step 60 999
Error in Default_Comp_obj : ORA-20001: HR_7155_OBJECT_INVALID: 87

The following select statement will further point to the issue:

select ctr.person_id Per_ID,
ctr.contact_person_id C_Per_ID,
ctr.contact_relationship_id Rel_ID,
ctr.contact_type C_Typ,
ctr.personal_flag Pers_Flg,
ctr.date_start,
ctr.date_end
from per_contact_relationships ctr,
per_all_people_f per
where per.person_id = ctr.contact_person_id
and ctr.person_id = &person_id
/
This script may return two contact types, both with the Personal Relationship flag set to "Y".

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms