Administration of IDoc Communication

IDoc communication is predicated on transactional Remote call (tRFC).

You can optimize the performance of ALE processing by using the subsequent settings and procedures.

Suppressing Background Processing
If tRFC errors occurs in the standard SAP system, , a background job is generated to re-establish the connection. In certain circumstances this might end in an outsized number of background jobs being started that completely block backgrounding .

Note:
Use program RSARFCEX to restart tRFC to cancel a background job if tRFC errors occur .

Select a connection to change in ALE Customizing (transaction SALE), 

Communication

Create RFC Connections (SM59)

Choose Destination ® tRFC Options and select the option Suppress Background Job at Comm. Error.

Setting Dispatch Status to OK
When an IDoc is passed to the communication layer, it's assigned a globally unique transaction identifier (TID). If the IDoc has been successfully dispatched, this information isn't automatically passed to the ALE communication layer. So that ALE processing sets the IDoc status to Dispatch OK, you ought to compare the TID numbers within the communication layer and therefore the ALE layer.

The SAP program RBDMOIND checks that the IDocs passed to the tRFC have already been sent to the receiving SAP system. If they need been sent, the IDoc status is modified to "12" - Dispatch OK

Note:
To set the IDoc dispatch status, run the program RBDOIND after the IDocs are passed to the communication layer.

Checking the tRFC Status

Use
Transactional RFC calls which transfer IDocs use the function module IDOC_INBOUND_ASYNCHRONOUS at reception (before release 4.0: INBOUND_IDOC_PROCESS).

If an IDoc in the sending system has been passed to tRFC (IDoc status "03"), but has not yet been input in the receiving system, this means that the tRFC call has not yet been executed.

Activities
To check the status of the tRFC calls, select Tools -> IDoc Interface/ALE -> Administration -> Monitoring -> Troubleshooting -> RFC Queue (SM58) and setout any additional selection criteria.

The program RSARFCEX restarts unsuccessful tRFC calls.

Note:
You cannot choose the choice is being executed in backgrounding .

Correcting the CALL_FUNCTION_SECSTORE_ERROR short dump

This information is for troubleshooting the short dump CALL_FUNCTION_SECSTORE_ERROR.

The system cannot read the password of the required RFC connection from the secure storage, or the password doesn't exist within the secure storage.

Use transaction SECSTORE to see the status of the secure storage.

If this seems correct, select the application "RFC Destinations" and search for the destination /RFC/.

The destination entry should have a green indicator.
If it doesn't , the message text column displays information about the error.

You can use the question mark within the end column to get an in depth description of the error and notes fix it.

If the destination /RFC/ is not listed in the secure storage, the password is lost.

If this happens, you'll use transaction SM59 "Configuration of RFC Connections" to reenter that password.

Once we save the destination, the status of the password (PW-Status) should be set to "saved" and a corresponding entry should be available in transaction "secstore".

Configuring the Unix SAP Internet Mail Gateway

Configuring SAP 4.6x Internet mail Gateway

We can confidure email communication setup in SAP system to send and receive mails from different sources.This article helps us understand the way to integrate SAPOffice with an external email-system. it is essentail that Internet email configuration is in place and running succesfully before this configuration. External email system receives e-mail from SAP.

You can configure inbound and outbound forwarding. Outbound flow forwards SAP message (eg: update termination) via UNIX sendmail to the intended recepient. Inbound accepts a message from sendmail and places it within the users SAPOffice inbox. Many companies prefer to configure outbound only.

Configuring outbound forwarding

SAP configuration

1. Using transaction SM59, create an RFC destination for outbound email 

 RFC Destination : SAP_INTERNET_GATEWAY

 Connection Type : T

 Description : SAP internet mail gateway

  If ondemand gateway daemon invocation is required, click on 'Explicit Host'.

 Program : /sapmnt/SID/exe/mlunxsnd

 Target Host : provide hostname details of the central instance.

 Click 'Test Connection' and you should see successful message.

2. Shared Office Settings select appropriate option : transaction SO16-> Send -> Settings or

 directly via transaction SCOT- SAPconnect Administration

 Nodes - Create

 Node : IMAIL

 Description : SAP internet mail gateway

 RFC Destination : SAP_INTERNET_GATEWAY

 Tick : Internet

 Address Area : *

 Tick : All formats

 Dev. type : Choose an appropriate Printer Device

 Set further address type : N

 Maximum waiting time for repeat send attempt procedure : Blank or as per the requirement

 Tick : Node is ready for use

 Setting

 - Default Domain : .com

 - Conversion rule : Needed if the communication device only support single format.

 e.g. if your email system only support RAW (ASCII text format) format 

 Format To Format Ranking Function module

 ALI RAW 1 SX_OBJECT_CONVERT_ALI_RAW (convert APAP List)

 Refer SNote 171698 for details.

UNIX configuration

1 .. cd /sapmnt/SID/exe

2 ..csh

 ..mlsomadm mailgw.ini

 System Name [C11] :

 Client [000] :

 Username : MAILADM

 Password : MAILADM

 Language : E

 Load Balancing :

 Hostname : 

 System number : 

 Gateway hostname: 

 Gateway Service : 

 Use SAP Router :

 Trace level :

 Sendmail Command [/usr/lib/sendmail -i -f]:

 Codepage [ISO-8859-1] :

 Trace Level (Outbound) [0] :

 Update file sapmailsid.cfg? [Y]

Testing whether your configuration is successful

1. Logon to SAP

2. Execute transaction SO01

3. Write a message and send it to 

4. If mail is not received in your internet mailbox, go back and review steps 1-12

Schedule the SAP Internet Mail Gateway Jobs to start out every 5 minutes

1. Create

2. Position your cursor at INT

3. choose schedule and provide the date and time

4. choose Schedule periodically and tick Minutes and enter 5

5. choose Create and you are done

6. Click Show Scheduling to check

Problems that you might encounter :-

If you have created a node in SCOT and it tests out well but receive the reply.

"cannot process message in node, parameters can't be converted".

Make sure the RFC connection is functioning , which SapConnect has been installed on the Unix Server or the Microsoft Exchange Server. Originally, I had a similar error, and located that nothing had been installed on Unix or Exchange, to support SapConnect.

In SCOT (View -> System Status), the mail persist in the Intransit column.

Check you sendmail.cf files (e.g.Sun Solaris /etc/mail/sendmail.cf). Try with sendmail command to send a test file at the OS level. You must be ready to send mail at theUnix level before you'll send mail at the SAP level.

Another way of connecting to the SAPOffice without setting up the SAPconnect is to use the