Comments
I agree completely. We are just implementing a secondary vendor and neither order planning or the purchase order will look to see if there is an item reference based on the vendor on the PO. So it defaults to what is on the item card - leaving it to the buyer to manually add an item reference so it can change the purchasing unit of measure. This seems like a big oversight. We are going to have an extension created by our partners because BC does not do this automatically.
The batch job that is failing for empty statements is: "Post transactional statements in batch"Menu: Retail and Commerce > Retail and Commerce IT > POS Posting > Post transactional statements in batchClass: RetailEodStatementTransactionalPostBatchScheduler A typical error message would be:"Batch task failed: While processing the Controlled state, a generic exception was encountered in retail statement xxxx-xxxxxx in the controller: Found no statement lines. Posting was aborted."
The current behavior is understandable because reservation logic originated from Inventory Management, while warehouse execution was introduced later through WMS capabilities. However, modern high-volume distribution centers require a closer alignment between inventory reservation and warehouse execution availability