RELATION_NOT_FOUND error

[saurabhkumbhare]

We are in the process of migrating our interfaces from the dual stack

system to the single stack system :

We are triggering 2 types of messages from the ECC system:

IDoc 1 :

Message Type : ZCNOSE_DESADV

Basic Type : DELVRY03

Extension : ZDELVRY08

Release : 46A

IDoc 2 :

Message Type : ZCSE_DESADV_GRP

Basic Type : ZDELGRP

Extension : ZDELVRY08

Release : 46A

When these IDocs are triggered and sent to the dual stack SAP PO system, the

interfaces work normally.

However, when the "IDoc 2" is triggered to the single stack SAP PO system we

get a "RELATION_NOT_FOUND" error in SM58 on DSACLNT211.

Can you please provide a guidance on how this error can be resolved.

[asharma9876]

Hi All,

we have been able to resolve this issue. This is not a PI issue. The issue was on the ECC side. From ECC they were sending IDOC along with an enhancement type and they had put a lot many restrictions in the coding for generating the IDoc. We triggered one IDoc without extension and PI received it successfully. This leads us to a conclusion that the extension type was creating the problem. So we decided to create a new extension type and linked it to Message type and Basic type. We did few changes in the code as well. And it finally worked.

If you face this issue then please check IDoc extension type.

Thanks,

Abhishek Sharma

[former_member765649]

Hi Abhishek,

Thank you for your inputs. I got the same problem. All idocs were flowing smoothly except for ASN_OUT and ZPICRQ. Scenario is in the Rollout boxes, these 2 certain idocs stuck in sm58 error message as "RELATION_NOT_FOUND".

What exactly are the steps that ECC needs to do?

Thank you.

Ramon Pajes

[OwenLiu]

Thanks for coming to SAP Community for answers. Please post your question as a new question here:

https://answers.sap.com/questions/ask.htmlSince you're new in asking questions here, check out our tutorial about asking and answering questions (if you haven't already), as it provides tips for preparing questions more effectively, that draw responses from our members. Please note, that your post here won't be answered.

[saurabhkumbhare]

Hi Lalit,

Can you tell me why all the Idocs are reaching the SAP PO system but have issues with only IDoc 2 mentioned above.

Thanks

Saurabh

[Former Member]

Initially you mentioned that idocs are reaching to dual stack po system and not reaching sjngle stck po system., so i am now confused on your question?

[asharma9876]

Hi Saurabh,

I am also facing the same issue. we have two IDOCs one is MATMAS05 and other is BATMAS03. Both the IDOCs are generated through same ECC system and we are using same RC destination, same partner profile, same port on the ECC side. On the PO side we are using same IDOC_AAE sender channel. ICOs are also configured correctly but MATMAS05 IDOC is working fine whereas BATMAS03 IDOC is getting stuck in SM58 in ECC with error message as "RELATION_NOT_FOUND".

Below are the logs in NWA Logviewer:

JRA] serverExceptionOccurred. Server XI_IDOC_DEFAULT_XID, Managed_Application_Thread_47, connectionId=7-122.20.37.40|sapgw01|XI_IDOC_DEFAULT_XID, Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: RELATION_NOT_FOUND (raised by system [u0bsappod001|a_rfc])

What could be the issue here? Do you remember what you did to resolve this issue at that time?

Thanks,

Abhishek Sharma

[saurabhkumbhare]

Hi Lalit,

Can you please tell where I can exactly check.

Thanks

Saurabh

[Former Member]

Can you please check in the partner profile for both IDOCs - which ports are configured & port refers to which RFC destination.

Do you have two separate PO systems or you have configured your scenarios in different way?

Thanks,

Lalit Mohan Gupta.

[Former Member]

You need to do the IDOC connection settings for single stack PI system.

[Former Member]

When connecting to Single stack system the connections are different than the connections for dual stack...

So you have to maintain connections and partner profile accordingly.

[former_member182455]

Hi,

please cross check the RFC destination and Transactional RFC whether the connection is estsbleshed or not.

RFC destination : SM59

Transactional rfc :SM58 trcodes

Regards

Srinivas