Entries in SM58 client is not avilable

[abhay_aggarwal]

Hi All,

I am working on IDOC to File scenario using 7.31 single stack .

I am facing issue while sending a IDOC from ECC side all idocs in 03 status but getting stuck in sm58 saying client 110 is not available in the system QE1.

however I am sending these IDOCs from 130 client.

I did some comparison in Dev box for RFC connection in PI side and found that 110 client specific RFC is not there in Quality.

Is this client specific RFC issue . Do we need to create all the client specific RFC in quality also. or this is something else.

Regards,

[former_member184720 · Accepted solution]

Hi Abhay - You don't need to create RFC connection to ECC system in ECC system.

I hope you have created the RFC destination of type T which points to the PI system..

and maintained the logical system for PI as <<SID>><<Client#>> eg:PID100 in your ECC system.

Follow the below blog and compare your ECC configuration..

[abhay_aggarwal · Accepted solution]

Hi All,

I have removed the RFC which was pointing from PI to ECC 110 client and resolved the issue.

Thanks Everyone for there valuable inputs.

Regards,

[Harish · Accepted solution]

Hi Abhay,

Good to hear that, please close the discussion.

regards,

Harish

[Former Member]

Hi ,

Go to SM59-->ABAP connections and check the rfc that is connecting to PI system -->click on connection test.

Now go to partner profiles and see whether you are using above RFC or not .

If above two are fine then resent the message from sm58.

Regards

Venkat

[abhay_aggarwal]

Hi Venkat,

I am using single stack for PI. so there are no ABAP connections we are using.

[abhay_aggarwal]

I have checked for the client . we have deleted the client 110 for which I am getting the error.

is there some more configuration i need to remove

[Harish]

Hi Abhay,

QE1 is your ECC system or PI system?

Please also check the client in BS in PI.

[abhay_aggarwal]

Hi Harish,

it's QE1 ECC system . I checked in Communication channel monitoring and it's showing

Ack Destination unavailable .