Solution : https://service.sap.com/sap/support/notes/17194 (SAP Service marketplace login required)
Summary :
SAP systems can manage fax communications primarily through SAPconnect, which integrates fax services alongside email, paging, and more through SMTP and RFC protocols. From SAP release 3.1, SAPconnect has facilitated direct fax transmission from SAP systems without additional components, accessible directly on SAP platforms post-3.1 release. Configuration and administration Guides and certifications for third-party services compatible with SAPconnect are available in the SAP online help and on SAP’s partner directories. Also noted, SAPcomm, which operated as an external communications server, has been unsupported post-release 5.0a, along with the dependent SAPLPD + SAPFAX methods as per Note 306509. SAP Exchange Connector remains an available bridge for connecting SAP with Microsoft Exchange Server systems for enhanced communication capabilities.
Key words :
sap library --> basis --> basis services/communication interfaces --> communication interface --> bc - sap communication serverthe actual telecommunication, sap library --> bc - basis, basis -> sap web application server, telecommunication services telefax, windows fax product winfax pro, communication services fax, sap netweaver -> application platform, sap defined integration scenarios, mysap software partner program, lower throughput status tracking
Related Notes :
| 455140 | Configuration of e-mail, fax, paging or SMS using SMTP |
| 455127 | E-mail (SMTP) in different SAP releases |
| 376099 | How to send dunning notices by Fax from R3 system |
| 306509 | End of SAPcomm, SAPfax and telex support |
| 122657 | SXC: Version overview and history |
| 63480 | R/3 and MS Exchange linking |
| 19584 | SAPcomm: getting the new version from SAPSERVx |
| 19302 | Configuring R/3 for Telefax with SAPcomm |
| 9119 | Configuration: SAPLPD - SAPFAX - WINFAX |