Fusion HCM: Saved Transaction With Emergency Contact Ultimately Results In Error (Doc ID 1935300.1)

Last updated on MARCH 01, 2017

Applies to:

Oracle Fusion Global Human Resources Cloud Service - Version 11.1.8.0.0 to 11.1.8.0.0 [Release 1.0]
Oracle Fusion Global Human Resources - Version 11.1.8.0.0 to 11.1.8.0.0 [Release 1.0]
Information in this document applies to any platform.

Symptoms

On : 11.1.7.0.0 version, Performance

Creating new hires and with emergency contacts (regardless of type e.g. spouse, emergency, friend...), if users complet the transaction in one shot, it works just fine.
However, if users saves for later on the assignment screen (after already adding the emergency contact), it fails, and it appears the failure is pointing to an issue with the contact not existing on the effective date.

Alos, if users create the hire, skip adding in the emergency contact, save for later and then upon resuming the transaction, add the spouse, it goes through just fine.

It appears that adding the spouse prior to saving the transaction that causes this issue.


Error

FAULT_NAME=ServiceException::FAULT_TEXT=com.oracle.bpel.client.BPELFault: faultName: {{http://xmlns.oracle.com/apps/hcm/employment/core/transactionApprovalService/}ServiceException} messageType: {{http://xmlns.oracle.com/adf/svc/errors/}ServiceException} parts: {{ ServiceErrorMessage=27023JBO-27023: Failed to validate all rows in a transaction.SEVERITY_ERROR27024JBO-27024: Failed to validate a row with key oracle.jbo.Key[300000000978123 2014-01-13 4712-12-31 ] in ContactRelationshipDEOSEVERITY_ERROR27024JBO-27024: Failed to validate a row with key oracle.jbo.Key[300000000978123 2014-01-13 4712-12-31 ] in ContactRelationshipDEOSEVERITY_RECOVERABLE_ERRORoracle.jbo.RowValExceptionContactRelationshipDEO29000JBO-29000: Unexpected exception caught: java.lang.NullPointerException, msg=Cannot invoke method getAttribute() on null objectSEVERITY_ERRORCannot invoke method getAttribute() on null objectSEVERITY_ERRORjava.lang.NullPointerExceptionoracle.jbo.JboExceptionoracle.jbo.RowValExceptionContactRelationshipDEO27024JBO-27024: Failed to validate a row with key oracle.jbo.Key[300000000978153 ] in PeriodOfServiceEOSEVERITY_ERRORPER:::PER_EMCOR_PERSON_EXIST_EFFDATEJBO-PER:::PER_EMCOR_PERSON_EXIST_EFFDATE: <MESSAGE><NUMBER>PER-1530163</NUMBER><TEXT>The person does not exist on the work relationship start date.</TEXT><CAUSE></CAUSE><ACTION></ACTION><DETAILS></DETAILS><INCIDENT></INCIDENT></MESSAGE>SEVERITY_ERRORoracle.jbo.RowValExceptionPersonId27024JBO-27024: Failed to validate a row with key oracle.jbo.Key[300000000978153 ] in PeriodOfServiceEOSEVERITY_RECOVERABLE_ERRORoracle.jbo.RowValExceptionPeriodOfServiceEOoracle.jbo.RowValExceptionPeriodOfServiceEOoracle.jbo.TxnValException} cause: {null}




Steps To Reproduce
1. Log in as HR Administrator.
2. Start New Hire Process and complete Identification and Personal Information pages.
3. Save and Close the page to resume later.
4. Resume completion of New Hire - observe on the Personal Information Page - some values entered for Emergency Contact and Phone Number Details have disappeared.
5. If the HR Administrator does not notice this then it results in the above error and failed transaction.
6. If the HR Administrator does notice it and updates, even after the update, they receive an error message of "Attribute Phone Type in Phone () is required" - however upon clicking OK, the HR Administrator is able continue and complete the transaction 



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