Comments
We currently have an environment on Installed product version : 10.0.42 (10.0.2095.51) and this is still an issue. Please fix this as it is an annoyance and leads users to believe there was a problem with the bank account created, the vendor record, or that the bank account change did not take place.
The problem here is that the PO 'Orderer' is set to the Employee of the F&O User that created the Purchase order.When the Purchase order is created from a Purchase requisition, it is quite common for the Purchase order to be created by a batch job, in which case, the F&O User is the system account which is running the batch job.In Purchase requisition scenarios, it would make much more sense for the default PO Orderer to be the Preparer of the Purchase requisition (from the Purchase requisition header).This problem also causes an issue in PunchOut (External catalog) scenarios.In the cXML which is sent to the Vendor (Request XML), there is a section for the 'Buyers' name and contact details. The Buyers name and contact details come from the Orderer on the Purchase order header. This makes complete sense, but unfortunately in many PunchOut scenarios the Orderer is blank or an Admin employee, because the Purchase orders are created by a batch job.
Had this issue recently in a clone of our go live environment in Business Central and could not figure out why the error was coming up. It was happening for multiple users with different levels of permissions. When entering a purchase order or going into a purchase order you could not see any of the Purchase order lines at all. The only thing you saw where the lines were supposed to be was the Sustainability Setup does not exist. I tried a few things but what fixed it for me was..Navigate to Users inside of Business CentralClick on the user you know if having the errorAdd these 3 permission sets to the specific user and saveSUSTAINABILITY ADMINSUSTAINABILITY EDITSUSTAINABILITY READAfter I added those the user refreshed the page and the error was gone and the purchase order lines were there and they were able to add info into the fields as usual. I believe since its a new feature this is a bug that microsoft will fix in a minor release but adding these permission sets to the users that are getting the error fixed it for us for now as a workaround. Hope this helps!