There are "message control" (old module) and PPF (Post Processing Framework = new module) in SAP R/3 system. Many SAP R/3 standard applications use message control or PPF.

Under message control, you can define the "output medium" (Create message), e.g.

1 = printer and printing respectively or

2 = facsimile (Fax) etc.

There are more, e.g. Telex, EDI (per Edifact), external sending, SAP Office (to send via SAP Office), ALE (dispersal, mailing list), special functions.

Thereafter, you can determine the "terms" in your message control, which output medium shall be active for which address. If 1 and 2 for output medium are defined you can select, that distributor A always gets the orders via fax whereas orders for distributor B are printed. This is practical for automatic workflow, such as dunning runs. Or / and the accounting clerk can decide for special orders, whether he wants to send them by fax or print them.

Many SAP R/3 standard applications use "Forms"(keyword: form component, SAP-Script (old module), Smart forms (new module) for output, in order to get their own layout-design.

"Reports", so-called ABAP Print outs ("Sequence of write commands") at first are only designated for printing and therefore to find at the print spooler. If you view that on your screen, you can decide whether you want to send them "manually" by fax with "Report send to"-option and your fax number. You can also send it manually from your spool, with the send to option ("send to .... type in fax number). If you want to send you orders automatically by fax with the ABAP-Print outs, you have to make changes to the application (call of communicating gateway). You can find a description of how to send reports by fax in SAP OSS hint subpara. 190669.

Information of fax transmission / delivery report

The delivery report of your facsimile delivery-status and facsimile delivery are coming from your ixi-UMS Server and delivered to the SAP R/3 System under "transaction SOST" (SAP Office Status). There you can sort for e.g. for all "non delivered facsimile". To each one the origin document will be referenced (the sender will be searched in the database) and can be resend from there. This is about the permission, who can access this (This are not SAP Office e-mail box!), for example you can give the permission to a group of persons, who are responsible for completing the fax delivery. Besides the SAP-System is generating a error message for non delivered facsimile and sends it to the senders SAP Office inbox. The user gets a notice (pop-up), if he receive a new message at his SAP Office inbox. This mail is only a information to the sender, that the delivery has not been successful and the sender should make a retry. For e.g. at the transaction SOST Area. Also look at SAP transaction S001 (=SAP Office inbox). If the user does not want to use SAP office, he should configure a message forwarding to an external e-mail address (e.g. to his Outlook inbox).

It is possible on part of ixi-UMS Enterprise System to configure a additional non delivery message, which can contain the original facsimile (as attachment), send to the users SAP Office inbox. At this way the user can take care about a retry for the facsimile sending.

If the ixi-UMS Enterprise System also connected to an messaging-system like Microsoft Exchange, Lotus Notes Domino or an other SMTP-based mail system, you have the possibility to configure the facsimile feedback to an Exchange-, Outlook, Notes or other inbox of the senders address. On this way the user can take care about a retry or further action of the facsimile document.

Comment for Administrator:

·Transaction SOST for the administrator from SAP-System is found under connect Administration SCOT.

·Facsimile deliver reports are depending on SAP-COM interface, what is obsolete by SAP. In future SAP R/3 Release-Versions 5.x,6.x there is no deliver reports over the SAP-Com interface possible. The SAP-COM interface is not included there any more.