Message Output to Dun the Delivery Date 
Use
As already mentioned, the delivery date has been set in the past to allow you to trigger reminder print-outs for the PO item. Before you print the message, the documents to be dunned and the corresponding message records must be selected through a dunning run.
Procedure
Menu Path |
From the Purchase Order node, choose Messages ® Urging/Reminders |
Transaction Code |
ME91F; ME9F |
Field |
Data |
Document number |
Your PO number |
Purchasing organization |
1000 |
Purchasing group |
002 |
Reference date |
Today’s date |
The system lists all of the documents found for your selection. Your PO document is now displayed according to the PO number.
The system informs you that the message has been generated. The system has now selected a message record for the document.

Steps 5 to 8 are optional.
The system displays all the message records for the selected purchasing document.
The system displays the message record with message type MAHN.
Field |
Data |
Logical destination |
Name of your printer |
Number of messages |
1 |
Print immediately |
Select |
Release after print |
Select |
The system confirms with a corresponding message.

Field |
Data |
Document number |
Your PO number |
Purchasing organization |
1000 |
Purchasing group |
002 |
The system lists all of the documents found for your selection that still have messages to be processed. Your PO document is now displayed.
In the document item, you see message type MAHN. This is the message record generated in steps 1 through 9.
The system displays your print form.
Note that the form differs from the first PO form. You can define the layout of this form using the SAPScript word processing.
The
symbol appears to the left of the item to confirm the message output. The message is now printed out on the printer assigned to your workplace.
Note that the dunning form differs from the first PO form. You can define the layout of this form using the SAPScript word processing.