Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from PhilAvelar on Apr 19 at 10:32 AM R. N. Wilhite,
To clarify the print program is configurable per output type not document type and typically the same print program is used for all outputs except the form called might be different. Anyways wont try and change your mind about that. As far as structure actually similar to what you mentioned in your posting, when we did this knowing the standard sent the email to the primary the BADI user a class to send to all non primary addresses, technically you are only using one output so NAST is irrelevant except to know whether the send is to be triggered.
Easy Breezy but obviously not a perfect solution but might be what you were looking for.
@Pierre yes sadly SAP did not develop a very robust solution but using a group email address would avoid any custom development but as Whihite mentions not easy to manage since the group would need to exist at the enterprise level, a user would not more then likley have access to update the group, thus you are involving a email admin everytime a vendor / customer group needs to be changed. Having done this several times I would not recommend any approach other then updating the print program.
Phil
| | | ---------------Original Message---------------
From: R. N. Wilhite
Sent: Wednesday, April 17, 2013 11:42 AM
Subject: PO EMail Exit
I need to be able to add additional email addresses to a PO email. I have seen numerous posts about copying the print program so that it can be changed. This would not be acceptable. My requirement is to do so on a more fundamental level, so that every PO is evaluated.
In invoice (VF01) I was able to do a very similar thing with an implicit enhancement in FM SBCOMS_SEND_REQUEST_CREATE. [Anyone who is interested is welcome to email me directly. You will find my Email address on my profile in my Bio. Please do not ask further about it here.] I'm not able to see PO going through that FM however. The obvious difference is that Invoice is a SmartForm and PO is a SAPScript...
So, does anyone have any suggestions on where else I might look, or perhaps some oversight I might be making?
Neal |
| Reply to this email to post your response. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today.   _.____.__ |
