SAP Mail Transactions
SAPconnect & Transmitting Trailers – Status: SAP ERP 6.0 EHP8 SP15
|SCOT SAPconnect – Administration||Transaction code SCOT is a SAPconnect management tool that provides a standard external communication interface that supports sending via telecommunications services such as FAX, text messages (pager/SMS), Internet mail, and X.400, as well as sending to printers and between different SAP systems. This allows external communication components to be connected to the SAP system. SAPconnect connects directly to the Internet through the SAP Web Application Server SMTP plug-in. This allows you to send and receive Internet e-mails, faxes, and sms (pagers/SMS) directly without having to use additional external communication systems.|
|SOIN Incoming Send Orders (SMTP)||The incoming send request overview (transaction SOIN or SOADM = > Administration > = Incoming Send Requests) displays all messages received by SAPconnect. Depending on the selection criteria selected, the program displays send requests received from SAPconnect.|
In transaction SOIN, it is also possible to view the MIME version. This shows how an e-mail is received by the SAP system.
|SO50 Rules for distributing incoming e-mail||You can edit the processing of incoming messages yourself. to do this you must enter an inbound processing rule (transaction SO50) and create a class that has implemented the IF_INBOUND_EXIT_BCS interface (exit for inbound processing)|
|SODIS Mandatory information management||You want to enable mandatory information management through the system settings. For e-mails and fax documents sent via SAPconnect and the SMTP plugin, the mandatory information for corporate communication is maintained here.|
|SBCS_REORG Reorganization of documents and broadcast orders||Reorganization of the document or send order data generated by Business Communication Services (BCS). Depending on the settings in “Reorganization Mode”, the transaction deletes documents with send orders or documents that do not belong to any send order.|
Documents or send jobs that are still in use are not deleted.
|SBWP SAP Business Workplace|
|SOSB Overview Send Jobs (Users)||Transaction SOSB can be used for a user to view their own send requests. Note 836463 – Transactions SOSB and SOSG: Displaying and Hiding Functions – describes the parameters that can be used to restrict certain functions of SOSG and add them to SOSB.|
|SOSG Overview Send Orders (Groups)||The SOSG transaction can be used for a user to select send requests from specific users or groups. This transaction is similar to SOST, but there are additional permissions checks that are controlled by the permission object S_OC_SOSG. See note 603382.|
|SOSA SAPconnect Send Orders||Overview of send jobs that allows you to view and manage all messages sent through SAPconnect.|
|SOST SAPconnect Send Orders||Overview of send jobs that allows you to view and manage all messages sent through SAPconnect.|
|SOSV SAPconnect Send Orders||To access the SOST and SOSV transactions, a user must have admin authorization in the authorization object S_OC_ROLE. See note 124025.|