When sending IDOCs from SAP to the Siebel application, no communication IDOCs are sent. You may see the message in SAP "No communication IDOCs have been selected".

Verify that you have added your IDOC message type to the Distribution Model.

Add your IDOC message type to the Distribution Model under SAP transaction SALE as defined in Distributing Logical Systems.

When sending IDOCs from SAP to the Siebel application, no IDOCs are being received by the Siebel tRFC BAPI Receiver.

Verify that your tRFC BAPI Receiver is connected with SAP Transaction SM59.

Select the TCP/IP RFC destination you created in Installation and Configuration and select the Test Connection button. If this test connection errors:

• Check your saprfc.ini file "TYPE=R" entry against information for your TCP/IP RFC destination.
• Verify that the program ID in the saprfc.ini file matches the program ID name in the RFC destination.

Go to SAP Transaction WE02 or WE05 and verify that the IDOC has been created and there are no errors in its transmission.

• Errors in the status record. Specific application errors may have occurred. These must be corrected within SAP and the IDOC deleted or resent. BD87 can be used for manual resend.
• IDOC with status 30: Idoc ready for dispatch. Partner profile has been defined to collect IDOCs. A background job (RSEOUT00) needs to be scheduled to send IDOCs or they can be sent manually by transaction WE14 or BD87. If the IDOC is supposed to be sent immediately, the partner profile must be changed to indicate this processing.
• IDOC with status 29: Error in ALE service. Your Partner Profile may be missing an outbound parameter record for your message type.
• IDOC with status 03: Data passed to port OK. There may still be a problem. Execute program RBDMOIND (BD75). This program updates the status of IDOCs that were successful to 12: Dispatch OK. If there was a problem the status remains 03. If status remains 03, check the tRFC queue for entries and reprocess from there.

When sending IDOCs from SAP to the Siebel application, no IDOCs are being received by the Siebel tRFC BAPI Receiver.

If you do not see any errors at the IDOC layer, check the tRFC layer. Go to SAP transaction SM58 and look for entries here.

• A network problem occurred or the receiver was not connected at the time the IDOC was sent. Resend transaction, see Resending Transactions from the tRFC Queue.
• The transaction may be waiting to be processed or may be currently in process. These entries are removed from the tRFC queue when their processing is complete.
• Depending upon the load, some transactions may time out. Resend transaction, see Resending Transactions from the tRFC Queue.
• A termination in processing occurred. This can happen when the data cannot be saved in the Siebel application. If your receiver is executing without using the EAI Queue, this can indicate that a problem in workflow occurred. If you are using the EAI Queue these errors occur only if the insert of the data to the EAI Queue failed. Check with your database administrator to determine if a problem has arisen. These transactions can be resent, see Resending Transactions from the tRFC Queue.

IDOCs you are sending into SAP from the Siebel application are not being processed.

There may be many reasons. Start by looking for the IDOC in SAP using transaction WE02 or WE05.

• The IDOC is not there. You may not have set the Sender Partner Number for the IDOC. This is set with the SAPSenderPtnrNum component parameter or method argument.
• The IDOC is there. Check the status record for error information, see Checking the Status Record for Error Information.

Siebel Tools BAPI wizard issues error messages when working with an SAP R/3 4.0 system.

If you are working with an SAP 4.0 version, an additional configuration change is required to use the BAPI input and output wizards.

To make the configuration change, see Working with SAP R/3 Version 4.0.