Multiple Absence Actions Sharing the Same Object ID

when an employee submits an absence request and the status is Pending Approval, the employee can still edit or withdraw that request. The expected behavior in the database is that each action (submission, edit, withdrawal) should be stored as a separate transaction. However, the actual behavior is that these actions share the same object ID. We need to identify a seeded function that can return each transaction individually.

Here is how the transaction looks before the employee make withdraw

Here is how the transaction looks after the employee make withdraw, it creates new request with new transaction id

And this is how it looks in the table you mentionedFND_BPM_TASK_B,the details of the pending transaction are not available