Couldn't find where to report bugs, so here I am.
This is still an issue in the latest CU6:
In the Codeunit 7304 - Whse. Jnl.-Register Batch there is a CONFIRM within the function CheckItemAvailability.

CONFIRM is evil if I call the function via SOAP or ODATA (it will simply fail, whenever it hits CONFIRM).
I kindly ask you to fix this for all objects in the next CU the same way as in Sales-Post (with ConfirmManagement.ConfirmProcess):

Kind regards
Fabian