+4This is happening on a client and I cannot find the reason why the generated cost transaction has a different branch to the labour transaction, so it is causing incorrect GL entries.
The data is all entered on the correct branch, so any ideas why the system generated cost transaction would have another branch to the source?
Best answer by lbarker
So I established it is definitely the user who adds the transaction.
The user had no default branch on them as its the API user.
For now I have updated the API user to have a default branch, and luckily the only branch that does manufacturing on this tenant, but its clearly wrong when the labour entry is one branch but the generated cost transaction is another so I have raised a ticket.
+6
A few screenshots may be helpful as well. Thanks!
+4So I established it is definitely the user who adds the transaction.
The user had no default branch on them as its the API user.
For now I have updated the API user to have a default branch, and luckily the only branch that does manufacturing on this tenant, but its clearly wrong when the labour entry is one branch but the generated cost transaction is another so I have raised a ticket.
+3
Thanks for opening a ticket on this, but my suspiscion is that support will not consider this to be a functional bug, but part of the overall design.
From a practical perspective, it’s not uncommon for some companies to have super users processing transactions for multiple companies. The creation of moves do not typically require a branch/company selection, so the user will often prefer to work from their “default” branch when pushing production transactions through the system.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
