[1] Question:
What is the difference between automatic forwarding and a mail system group?
Answer:
The aim of both of these procedures is the same; the R/3 user can receive and process messages in an external mail system as well. The automatic forwarding in this case is set up by each user for a certain period of time. It suits users who only very seldom look at a particular R/3 system and prefer to read their mails in another system. Furthermore, you can determine a substitute if an employee is on vacation or ill. In this case, you can specify another R/3 system and an external mail address.
As of Release 4. 6C, you can activate the mail system group system-wide. All users who select Internet Mail (STMP) as standard communication, and have maintained their home address, then automatically receive the message sent to this address. This is usually an Internet address of an external mail system. You can therefore receive all messages from different R/3 systems centrally in a mail system.
[2] Question:
Can I use forwarding and a mail system group at the same time?
Answer:
If you have maintained a home address, an additional forwarding address is no longer taken into account when the mail system group is activated. Otherwise, automatic forwarding is possible, if you do not participate in the mail system group.
[3] Question:
Who can set up automatic forwarding?
Answer:
Any user can set up automatic forwarding in transaction SO12. In this case, you can determine whether the documents should still remain in the inbox or not.
Furthermore, an office administrator can set up forwarding once using transaction SO36. This is for emergency purposes only (for example, the user suddenly falls ill) and does not act as administrative maintenance for forwarding.
As of Basis Release 6.40, you can use transaction SO16 to check and maintain forwarding or mail system group addresses by choosing 'Address check' on the 'Mail system group' tab page.
[4] Question:
How can I change or delete automatic forwarding?
Answer:
The relevant user can change or delete forwarding (transaction SO12). As of Release 6.40, an office administrator can carry out maintenance using transaction S016 (See Note 818600).
[5] Question:
Why can I not forward to my own Internet address?
Error message: The forwarder and recipient are identical.
Answer:
You cannot forward mails to Internet addresses that are maintained in the User Maintenance (transaction SU01). The user is now known internally in the R/3 system by these addresses. All the messages that are addressed to this address should be delivered to the user. Problems may occur if one of these addresses is set up as external forwarding.
If the user has several addresses, proceed as follows: Maintain internally an address that is connected to the system, and then you can forward to external addresses. For example, the addresses can appear as follows:
Internal address: firstname.surname@system-id.r3.company.country
Forward to: firstname.surname@company.com
The correction instructions in Note 957182 change the error message to a warning. You can then enter and confirm your own address for forwarding.
[6] Question:
How can I activate the mail system group?
Answer:
You activate the mail system group centrally for the system in transaction SO16. In this case, you have two options:
Mail system group in another R/3 system:
You send all the mails to another system or another client. To do this, set up a remote mail node in the SCOT with an RFC connection in the other system. If you use the 'NONE' RFC connection, the messages are created in the same system ("Bounce-back").
Mail system group at users' home addresses:
This can be set up individually for every user. Using the communication method in transaction SU01, you determine by which communication method you should send the mail; with the corresponding address for this method, you specify the individual address.
For example:
Communication method: Remote mail
Remote mail address : P01:100:username
For forwarding in another R/3 system.
Communication method: Internet Mail (SMTP)
Internet address : user.name@company.com
For forwarding to an Internet address.
[7] Question:
How must I maintain the Internet addresses of the mail system group users?
Answer:
You must have maintained at least one Internet address. This is automatically flagged with the home indicator. If you have specified several addresses, decide which address is to be flagged with the home indicator. Set the standard communication method to 'Internet Mail (SMTP)/E-Mail', so that all incoming messages are forwarded to the home address.
[8] Question:
Can the users still read their mails in the R/3 system, even though the mail system group is activated?
Answer:
Users who participate in the mail system group can no longer read their mail in the R/3 system because the messages are not copied.
However, if you want to read and process your messages in the SAP Business Workplace, you can select the 'Letter' standard communication method. This method is not a part of the mail system group, since it is not one of the mail system group's sending mediums.
[9] Question:
Who is entered as the sender, when a mail is forwarded? Which originating address is used?
Answer:
The sender of a forwarded mail remains unchanged. The following is used as the originating address:
When sending a mail internally, the sender's user name is used.
When receiving external mails, the assigned Internet address of the sender is used.
When forwarding internal mails to external addresses, the Internet address of the internal user is determined from the address data. If no Internet address exists, an address can be constructed using 'Default domain' in the SAPconnect settings. See also Note 552616.
[10] Question:
What do I take into account when I send object relationships externally?
Answer:
If you send object relationships externally, they are converted to a URL . Using this URL, you can start a SAP GUI for HTML logon. You then call the default method of the object (generally DISPLAY). To generate the URL and to logon to the system, you need to install an ITS server.
Online documentation Web Application Server (6.10/6.20)
-> mySAP Technology components
- > SAP Web Application Server
- > Basis Services/Communications interface
- > Communications interface
- > SAPconnect
- > Administration
- > Sending business objects using the Internet
On-line documentation NetWeaver 04 (as of 6.40)
-> SAP NetWeaver
- > Application Platform (SAP WAS)
- > Connectivity
- > Communications interface for mailing and telephony
- > SAPconnect
- > Administration
- > Sending business objects using the Internet