Outbound IDoc not Sent to Correct Recipient

[dchawla]

I am able to establish a stable connection between (SAP Server)and the External system (GIS) but am facing trouble in exchanging the data between them.

For an overview, we are trying to receive an outbound IDoc. We have followed all the steps to complete this outbound configuration which include:
1. Creating RFC destination (TCP/IP)

2. Creating PORT (transactional)

3. Creating a partner profile

4. Configuring output settings at tcode NACE.

After creating a purchase order (PO) using the outbound-enabled partner, we expected to receive an outbound message. We have confirmed that the message generation is successful, as evidenced by the attached screenshots.

However, IDoc is not being received by the intended external system. Upon investigating the output processing analysis for the created PO, we discovered that the IDoc is being sent to another SAP system instead.

Based on our configuration, it should logically send the IDoc to the external system, not to another SAP system, as no SAP system is configured or set as a Target.

Please have a look into this and suggest the steps to be followed to resolve this.

Thanks in advance
Dhruv

[Ryan-Crosby]

Hi Dhruv,

You will want to check the IDoc port recorded on IDoc 3524767 and then review the RFC destination settings associated with the port (SM59). The IDoc port details will exist in transaction WE21, and the related partner details for vendor 9999 will be accessible in WE20. Reviewing the information in those three transactions will provide you with the necessary information to make the appropriate updates to avoid the problem in the future.

Regards,

Ryan Crosby

[Ulrich_Schmidt]

This is more an ALE question than an RFC question, so I have also added the tag for ALE.

I am not an ALE expert, but I think there must be something wrong with the Partner Profile (or the Distribution Model, if you use any here? It isn't explicitly mentioned in your question.) Therefore you should display the IDoc in transaction WE02/WE05 and compare the values of the IDoc Control Record precisely with those you customized in the Partner Profile. Perhaps there is some difference here?!

And the following documentation might be helpful. It was written originally for the SAP Business Connector as receiver of IDocs, but it applies just the same to every IDoc scenario, where the receiver is an external Program, registered at a Type "T" RFC destination. See the chapter "Sending IDocs with ALE from an SAP System to SAP BC" in the PDF document "SAP BC SAPAdapterGuide" available at https://support.sap.com/en/product/connectors/bc/details.html?anchorId=section_295234589

It has many useful information on how to customize the ALE settings (Logical System, Port, Partner Profile, Distribution Model), when trying to send IDocs to a Type "T" destination.