Deleting a Loan From The Servicing Director Loan Setup Application Does Not Cascade Delete The Employer Table Record And Leaves Orphaned Database Records

Deleting a Loan From The Servicing Director Loan Setup Application Does Not Cascade Delete The Employer Table Record And Leaves Orphaned Database Records

In the Servicing Director Loan Setup application, a user has the ability to permanently delete a pending loan from the system.
When you do so, the records should cascade delete and permanently remove that pending loan record from all of the related SQL tables in the Service database.
You may, however, find that the loan detail record is not removed from the Employer table, and an orphaned record remains.

Environment:

Servicing Director Employer table

Workaround:

When a pending loan is deleted in this manner, most of the SQL tables involved in this process have the corresponding record deleted by means of a delete trigger on the Loan table.
This results in the cascade delete.
However, the Employer table, as is the case with some other newer tables, do not make use of the delete trigger, but instead, referential integrity is enforced with a foreign key.

The Employer table has a foreign key relationship with the Loan Table.
It is called FK_Employer_Loan.
If this foreign key is missing for any reason, records in the Employer table will not get deleted when the loan is deleted from Loan Setup.

In SQL Management Studio, please check that this foreign key exists on the Employer table.
If it does not, please open a support case in Case Management to report this issue.

ArticleNumber:

000071246