Application Update WS- Primary Replaced Issue And Application Details WS Response Issue (Doc ID 2903524.1)

Last updated on OCTOBER 25, 2022

Applies to:

Symptoms

Application Update WS- Primary Replaced Issue and Application Details WS Response Issue

Issue : When another applicant (e.g secondary/spouse ) is added to the application via Application update WS and same SSN is provided (same as Primary applicant ) then Update WS is updating "Primary" applicant record to "Spouse/Secondary"

Hence when such application is queried by using "Application Details" WS, it is simply throwing "500 Internal server error".

Expected result:
----------------------
In UI flow, whenever an applicant is added to application, an application cannot exist without "Primary " relationship. Same constraint/ validation should be available via WS also. WS should not replace existing Relationship details when adding another applicant Relationship.

Application Details WS should not throw "500 Internal Server error" and display appropriate response


ERROR
-----------------------
 "500 Internal Server error"

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create an application
2. Add another applicant (e.g secondary/spouse ) to the application via Application update WS by passing the same SSN number as of Primary customer
3. Verify that existing Primary customer is updated with the newly added customer
4. Fetch the application details through Get Application details WS
5. Getting "500 Internal Server error" message.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users having issue WS response.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.