How to trigger output message determination for already created sales documents
we may face a situation where for already created sales documents, we need to determine and print messages that, for whatever reason, were not determined when creating the documents (for example, a failure in output determination, missing records) or there’s a new output type now in use that we need to print.
How to trigger output in those cases?
Once the process for output determination is completed in customizing & functional, we will need to open documents for modification and save them to trigger output determination.
If number of documents is really small, we can think of manually open and close them (for example, VA02, VA05N for sales orders) but if number is big, we’ll need another approach: we can use MASS transaction or develop an abap program that opens sales documents for change and saves them.
MASS transaction. Let’s see how-to with an example for sales orders.
First we need to find a field we don’t use in our sales orders. Let’s say purchase order field.
Then we run MASS transaction and select object code type BUS2032 and execute. Then in tab TABLES, we select table MASSSDHEAD_S, and in tab FIELDS, we select field MASSSDHEAD_S-BSTKD (purchase order). Now we select our sales orders and execute. In the following screen we set a value, for example, a dot (.) in new values and click on icon carry out a mass change.
This will copy a dot (.) to our sales documents in purchase order field. When saving, system will update sales orders in background, triggering output determination. Now we can open a new session to check the results in our sales orders. If dispatch time is set to 4 for the output message, output should start immediately.
Now we come back to MASS transaction session, to undo the changes. We remove values from New values, click on icon carry out a mass change to remove the dot (.) from our sales orders and save. If dispatch time is set to 3, we can print the sales orders with report SD70AV1A.