Hi Dinesh,
Something has to give - either the admins have to set up the printers without front-end printing method too, which you can then use to print in background (preferable, because if the printing fails for some reason, hopefully it can be restarted via workflow), or you have to find another way to couple the printing to MIGO LUW, in dialog processing...
Maybe you could try to integrate printing via a CL_SYSTEM_TRANSACTION_STATE=>TRANSACTION_FINISHED event handler. That way your printing logic would kick in after MIGO posting COMMIT WORK is finished and hopefully not cause dump. You could control that printing is not executed for posting in background, and the challenge would be to wait for possible update tasks (are there any?) to finish. But the 100$ question still is - who and how will process the possible exceptions during printing..? You'd have to offer reprint functionality somewhere in the system, and somehow notify user, I guess.
cheers
Janis