cancel
Showing results for 
Search instead for 
Did you mean: 

Stop Invoice Reprints

Former Member
0 Kudos

Hi all,

We have recently started emailing invoices. To do this we are using a communication strategy we developed. If an email is maintained on the customer master an email is sent otherwise the invoice is printed. This is all working fine and the solution has gone live. This is output condition ZPMA and a batch job is set up to print/email these invoices.

For Re-Prints we have a second output condition that only allows printing of the invoice. This is output condition ZPRE.

The issue is that some users are going into VF03 => Issue Output To and instead of using output condition ZPRE to reprint the invoice, some have accidentally used ZPMA. If an email is maintained on the customer master an email will be sent to the customer automatically, so multiple emails could be sent to the customers when we only ever want one email sent out. This is a major issue, does anyone know of a solution?

Kind regards,

Elaine

Accepted Solutions (1)

Accepted Solutions (1)

former_member184555
Active Contributor
0 Kudos

Hi

Configuring the condition type for not eligible for 'Multiple Issuing' and it will not allow the system to issue output more than once. We can also control the triggering of output condition by attaching a requirement routine against the condition table/access in the access sequence of this output condition type.

Thanks,

Ravi Sankar

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Check with your define output type , where there is a tick mark for multiple issuing , which means it ll send multiple times of the same output. so put off the tick mark . it won't send multiple times again.

Hope it ll help you.

Regards

Pitabash

Bangalore

moazzam_ali
Active Contributor
0 Kudos

Dear Elaine

Please below two links and test with your BASIS guy. I did not test this but I am looking for some authorization object for output condition type. If there is some standard then you can use it but if there is no standard object then you can create your own and add in user's roles for output condition types.

http://help.sap.com/saphelp_nw70ehp2/helpdata/en/c7/58c905e5bf11d18e2b0000e83dd9fc/content.htm

http://help.sap.com/saphelp_nw70ehp2/helpdata/en/c7/58c902e5bf11d18e2b0000e83dd9fc/content.htm

Thank$