Hi
If your SD output configuration is set up correctly, an e-mail from SAP using medium 5 should go through just fine via SAPconnect (transaction SCOT). When it works, the external recipient should receive an e-mail with a PDF attachment containing the form image, regardless of whether it has been created via SAPscript or Smart Forms. Depending on your output determination settings, this even can happen in the background, without any interaction with the SAP front end (e.g. for invoices created automatically by a batch job).
Typically, a failed send will be flagged in the message control table (NAST), and this table should be monitored closely. However, there are many reasons why a document hasn't gone through, and this can be the case with both outgoing faxes and e-mails from SAP. The solution to both is the same: After identifying the failed document, re-send it manually by going inside it in change mode and repeating the appropriate output. If an obsolete customer e-mail address was the culprit, a customer master change would also be required, along with an audit of any docs recently created for this customer.
If any underlying data has changed since initial issuance, a re-sent document may not appear identical to the (failed) original. Sometimes, as when address info has been corrected, this can be a good thing. After all, the new document is more accurate than the old one.
In other cases, such as when pricing info has changed, it might be a cause for serious concern. There are several ways to deal with this concern:
1) Limit the types of changes allowed on certain docs after creation
2) Set up a doc image archive via ArchiveLink and re-issue output from there instead of from the current doc; or
3) For highly sensitive docs, consider a more secure delivery method.
<b>sending smart form</b>
You didn't specify the nature of the form or print program, but I suspect we are discussing application-driven output.
In any case, I suggest you take a close look at the print program. If it is a standard one provided by SAP, it is quite possible that hooks already exist to send your Smart Form output via e-mail as a PDF attachment.
See for example the call to function 'LF_FM_NAME' in standard print program RLB_INVOICE. Notice the preceding call to function WFMC_PREPARE_SMART_FORM? This function does the heavy lifting for you; here, no additional work is needed in either the form or the print program. To generate e-mail output, the remaining work essentially is:
1) SD output configuration (e.g. mapping the relevant billing output type to transmission medium 5 - 'External send' - via the IMG)
2) SAPconnect configuration (txn SCOT -- there are several notes in the SAP Service Marketplace discussing this component, such as 152474 and 312690).
3) Setting up the sender and recipient e-mail addresses (e.g. sender = txn SU3 data; recipient = bill-to party's txn XD02 data).
Hopefully, the print program at issue has the hooks you need. If not, you may need to explore the possibility of (a) changing it, (b) cloning it and changing the cloned version, or (c) manipulating the values directly within the form itself via field-symbols (which may or may not work). Whichever approach you take, I wish you luck.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.