When we configure purchase requisition permissions to allow a user to prepare a purchase requisition on behalf of another user, the system permits the preparer to edit and adjust the PR, and the authorization is passed. However, these authorizations are not considered when using standard data entities like Purchase requisition header and lines and Purchase requisition V2. If the user attempts to edit from the data entity, an error is encountered: 'Write failed for table row of type 'PurchaseRequisitionLineV2Entity'. Infolog: Warning: Current user is not authorized to request on behalf of requester with personnel number XX; Error: validateWrite failed on data source 'PurchReqLine'.'

This error occurs despite the purchase requisition permissions being configured. The expected behavior is that the user should be able to edit the PR as they are authorized and have already done so through the UI.