Error "Could not make header information transportation &1, strategy &2" (/SCWM/ERPINTEGRATION012) is ever added to the log, erstwhile the EWM transportation can't beryllium created. This is simply a wide mistake message. The different connection is much specific, similar successful supra question (of people determination are different messages to bespeak circumstantial scenarios).
Check the discourse of the delivery. If the transportation was created by mishap and not request to beryllium processed successful EWM, it tin beryllium rejected via Warehouse Monitor.
If the transportation is inactive required, cheque if the missing customizing tin beryllium created, oregon if the transportation needs to beryllium created with antithetic parameters. In this case, you whitethorn besides request to cull the stuck transportation to make a caller 1 from scratch.
Rejection from SMQ2 (on EWM side) is documented successful SAP Knowledge Base Article 3384239 - Delivery papers cannot beryllium created successful EWM, stuck successful SMQ2 queue.
KBA 3384239.