Below is the process for pay update:

1. Backup database
2. Perform FMIS integration
3. Begin Transaction
   1. Execute procedure LT_PAY_ClosePay
   2. Loop starts with employee list
      1. Loop for each pay detail line
         1. Move line into pay history
         2. Update deduction 
         3. update allowances and benefit
      2. Loop end
      3. Move PR_EMP_TIMESHEET into history
      4. delete PR_EMP_TIMESHEET
      5. delete all pay detail lines
      6. delete pay header record
      7. Update employee profile
   3. Loop End
   4. Update pay control table with status as updated
   5. Update next pay number 
   6. execute procedure lbs_pr_contract_exp_sp
   7. execute procedure lbs_pr_leave_accr_sp
   8. Update allowances/benefits records where it has reached expiry date. change status to closed
   9. Update deduction records where it has reached expiry date. change status to closed
   10. execute procedure LT_PAY_CalcSuperGuarantee
   11. delete pr_cur_pay_det for this pay 
4. commit transaction

1. We have refactored the PB code 
2. Created a new procedure LT_PAY_UpdateByEmployee that handles data that was in the PB loop as well as employee specific processing.
3. Refactored notification messages
4. Reviewed possible causes of data loss. We were not able to reproduce the issue, however, the current refactored code is a lot clearer and does not show any potential issues

We have not been able to identify the case, however, a significant amount of effort has been put in tpo clarify and restructure code to prevent this from happening.

Regards
Sanjay