Error while triggering IDoc in PI7.4

[former_member333459]

Hi Experts,

My scenario is IDoc to File. The Sender IDoc adapter is working fine. Also when IDoc is triggered from ECC it is executed with status 03. But the IDoc has been stucked in SM58 with the following error:

No Endpoints registered for XI_IDOC_DEFAULT_PID on

system PI

where XI_IDOC_DEFAULT_PID is the program ID. I have done with the configurations in NWA for resource adapter,Destination too.

I have also used registered server program in RFC destination.

Can anyone let me know how to resolve this issue.

Cheers,

Neethu

[former_member333459]

Hi All,

The issue is resolved now. I have changed the binding key property in resource adapter as PI_AAE_IDOC. It is used to associate the inboundRA  resource adapter with the IDoc_AAE adapter and hence it should not be changed. It should be the default value always.

Cheers,

Neethu.

[vicky20691]

Yes Neethu,

That is given in the blogs and documents. For example this document says Binding Key must have the constant default value

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5050119d-9c47-3110-eab0-d90ebd211...

Regards,

Vikas

[JaySchwendemann]

You may also check if in PI NWA JCo Monitoring there are entries for your Program ID.

If they are missing, please check if ACL is enforced. If so, you'll need to either switch ACL off (not recommended for production environments) or edit the ACL file according to your needs.

SAP Gateway Security Files secinfo and reginfo - Security Settings in the SAP Gateway - SAP Library

HTH

Cheers

Jens

[former_member333459]

Hi Jens,

I have tried all the workarounds and still facing the same error.

Cheers,

Neethu

[nipun_shedhani4]

Hello Neethu,

Is your SM59 TCP/IP RFC Working, That will confirm you if you JCO RFC server program has been correctly registered or not.

Also let me know which ECC system are you using, is it Above 7.20 or below. That will induce another SAP Note to apply.

Thanks.

Regards,

Nipun

[former_member333459]

Hi Nipun,

It is  SAP ECC 6.0.

The SM59 connectivity is ok.Though while triggering IDoc the status is 03, the message in SM58 is error message  as Endpoints not reigstered.

Cheers,

Neethu

[vicky20691]

HI Neethu,

Can you paste the screen shot of the channel here?

and also just delete your ICO and create again and give it a try.

It worked for me a month back. Please try and revert back

Regards,

Vikas

[abhijitbolakhe]

Hi Neethu

Please check if your TCP/IP RFC Connection is working.

The Program ID provided in TCP/IP connection should also be mentioned in Resource Adapter.

Regards

Abhijit

[vicky20691]

Please follow the blogs given by Jannus Botha.

Please follow this discussion it might help you. The sender channel holds the key.

If error persists after you follow blogs and configure just keep the sender channel in manual mode and give the ECC system's parameters in the channel.

PS-

1-No need to make the JCO RFC Provider

2- checl SMGW

3- No need to give any gateway host and service in SM59 in ECC.

4- Check the Unicode option in SM59 as told.

5- And still if SM58 persists make channel as Manual configuration and give the ECC sysem details.

Things to to do with InboundRA

1- Destination - the destination you created (XI_IDOC_DEFAULT_DESTINATION)

(I hope destination is created correctly with ECC details)

2- MaxThreadCount- 5 or 10

3- Local = true

4- Program id- use same here and sm59

5- in gateway host and service use PI's host and service

Please let us know the results

Thanks and Regards,

Vikas

[former_member186851]

Hello Neethu,

Go to SM59 and in the TCP destination you maintained enable the unicode option.

hope it will work

[Former Member]

Hi Neethu,

I had this issue on our system.

Please trigger a message in SAP ECC and then go to SAP PI Nwa to your logs.

It will be under Logs Overview. Go to View and Select Developer Traces.

Might just be that it cannot find a receiver on the integrated config.

It will then give you more detail about the error that you get.

Please also following the blog below on how to setup the inBoundRA etc.

Regards,

Jannus Botha

[Former Member]

Hi Neethu,

Please see the screenshot attached. We were missing these attributes in our InBoundRA resource adapter and it caused this issue.

Please just add them if they are missing in yours.

Is under Message Listerner.

Regards,

Jannus Botha

[former_member333459]

Hi Jannus,

Thanks for your response.

The logs are showing returned  destination XI_IDOC_DEFAULT_DESTINATION_PID.

Could you please help here.

Cheers,

Neethu

[Former Member]

Hi Neethu,

Can you please provide me with all the error logs when you trigger an IDoc?

Regards,

Jannus Botha