Would have been 'nice to have ’ the option in site configuration as well as a global site default… then if specific part need a specific buyer… then PartPlant.BuyerID would be used…
If you’re doing site-specific buying then you might not have a choice. I checked Site Config and Warehouse…not there. Only other table I found it in so far is in Part Class…
Hmph…if it’s coming up without even selecting a Supplier then we’re back to square one.
EDIT - just thought of something…the PartPlant.BuyerID (and PartClass.BuyerID) likely come into play with PO suggestions that you’d convert to POs…but I can’t explain the manual PO entry side.
Well GetDefaultBuyer I have just put a message to show and nothing showed.
I saw a method used where LT is the buyer shown as default (again I do not know from which config this happens…)
Erp.Proxy.BO.PurAgentImpl
GetByID
https:the server
Erp.BO.PurAgentDataSet
2025-01-16 09:17:19:9498811 AM
1
84c34de4-d421-4ea0-bf58-4c60b0c1130a
0
But was not successfull using that.
What I end up doing is on the Post of GetNewPOHeader, I grab the current userid, go get the PerCon record of that user, and then grab the PerConID and go get the record in PurAgent having this PerConID.
This gives me a valid Buyer
Then I force the BuyerID and BuyerName with the info from PurAgent table.
That worked!
I still need to tests different scenarios such as using POsuggestions etc… I will keep you posted!