Comments
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
Yes, I have some multiple tickets which in the same situation. The guidance was reach to FTE but seems like the solution has to create new environment then clone through that new empty environment which is not an ideal option for most of the customers. Turn to an official feature is quite a good idea at the moment.