Ideas for Adding a Quick Print Button to VA01 Overview Screen

Question

Problem Statement:
Our users would like a "quick print" button on the VA01/VA02 application toolbar that immediately spools the Order Confirmation output to the printer.  Our users want to print the output on demand, i.e., they do not want the output to automatically be printed when the order is created because a printout is not always needed.  We already have condition records created with Dispatch Time set to 3 - Send with application own transaction.  However, it takes 7 or more clicks to print the output on demand by navigating the menu (Extras > Output > Edit...Further Data...etc.) and changing the Dispatch Time to 4 - Send immediately when saving.  This is a big ergonomic issue and a time killer.
Although the number of clicks to print are less when printing the output from the VA02 initial screen (via menu Sales document > Issue Output To), this is not acceptable when creating new orders.  Really need an on-demand, quick print button on the VA01 screen.  As an aside, we have a totally custom transaction for preparing sales order data (shopping cart-like way of finding materials and entering required data) that then calls VA01 and fills in all of the information.  When saving in VA01, the user is returned to our Z-transaction so asking the user to subsequently run VA02 to print is not practical.
Current Output Determination:
We have custom output type ZBS0 (copy of BS0).  Condition records for print medium are set to Dispatch Time = 3.
Questions:
1.  Searching these forums, it appears custom code (extension or user exit?) can be written to call RSNAST00, or something similar, to automatically send output having a Dispatch Time = 3.  Where can I find more information on exactly how to do this?
2.  Do transactions VA01 and VA02 (Overview screens) have extensions that allow a print button to be added to the application toolbar?  We would want to call the custom printing code from the button to send the output.
Any feedback on how others have solved this problem would be greatly appreciated.
Warm Regards,
Rob
P.S.  Using GuiXT is not an option for us.

Answer 1

HI
We had similar issues with printing packing list and picking list by the warehouse people.
We created a new ztransaction with input fields of delivery number, output type, number of copies and a check box for repeat output(in case if the output was already printed).
You can also create a new Z-transaction with input fields of Sales order number(mandatory field), output type (Default it with value of ZBS0), number of copies (default it with 1) and a check box. On executing the transaction You can provide a message if the output was already printed so that the user can select the check box to repeat the output and execute. You can also print multiple SO by giving a range value if required.
If you do not want the user to enter the new ztransaction every time, try providing a menu path to the new z-transaction from the existing z-transaction which you are using for order entry.
Hope this helps you.
Thanks,
Arun.S