GL Journal approval Reassign functionlity behaviour

Summary:

Client is leveraging to use the reassign feature on the approval workflow notifications across the financials approval workstream. I have tested a POC on the requisition approval notifications in which the requestor - Line Manager/Supervisor hierarchy is able to do a reassign his approval workflow notifications to a user in a multi-org business unit. Based on the job level approval limit assigned to the reassigned person reassign WF notification moves up the reassigned person supervisor hierarchy until its journal approval limit of supervisor which is standard expected behaviour of reassigned functionality. 

Say A is the requestor A1, A2, A3 are the list of line of approver chain of BU01. A1 who is the first line manager of requestor initiates reassign to an Approver (B1) in the another BU02 . In this Case Say B1-->B2-->B3. If B1 approver doesn't have required approval limit, reassigned approval notification moves up the supervisor chain of B1 till required approval limit of the supervisor has identified, Say B3 is the final approver and he approves it. But on the GL journal approval reassignment notification the behavior of the reassignment is totally different.