Error sending IDoc from ERP to PI 7.4 Java Only (stuck in SM58)

[Former Member]

Hi specialists

I'm trying to send an IDoc to our new PI 7.4 Java Only.

Because of some authorization issues I changed the RFC Destination <blabla> on PI (nwa) pointing to the ERP system.

Now the IDoc is stuck in SM58 (tRFC queue) and I get this error message:

The IDoc Destination <blabla> was changed. Refresh the destination instance with

Meldungsnr. SR053

Anyone able to tell me where to do this refresh? I'm new to PI 7.4 Java Only and could not find useful answers on SCN and other internet sources.

Thanks a lot in advance for any hints.

Renaud

[Former Member · Accepted solution]

Finally succeeded...

Simply deactivate and reactivate the communication channel. This somehow helped to refresh the RFC destination instance. IDocs can now be sent out of ERP to PI.

[JaySchwendemann]

Hi Naveen,

might be an authorization issue. PI reaches back to ECC / ERP in order to get the metadata (implicetely when sending IDocs for the first time from ECC, explicitely when preloading metada)

See here for necessary authorizations:

http://scn.sap.com/docs/DOC-31398

Cheers

Jens

[Former Member]

Hi Jens

Thanks for your suggestion as well.

I can confirm that the user specified in the RFC destination (the one defined in NWA and pointing to ERP system) has definitely sufficient authorizations. It really seems that the RFC destination mentioned in the SM58 error message is somehow cached and not refreshed automatically after applying some changes in it. In my case the user was wrong and had to be replaced with the correct one - with sufficient authorizations.

Other ideas how and where to refresh those RFC destinations or how to possibly invalidate this kind of cache?

Best regards

Renaud

[JaySchwendemann]

Hi Renoud,

ok I hopefully understood your problem.

1.

First I'd like to point out that merely using connection test on the destinations does not necessarily mean that actual communication will also be without error.

--> I would set up ST01 authorization check in ECC for user that connects from PI to ECC

--> I would look at the developer trace + security / authorization logs in PI nwa/logs. Maybe increase tracing level to globally "warning" temporarly

2.

Taking a long shot here but you may try to register the queues in EEC using SXMB_ADM --> Manage Queues --> Register Queues

Cheers

Jens

[naveen_chichili]

Hi Renaud,

Suggestion is to check the RFC destination for your scenario and also refresh metadata for your IDOC.

Regards,

Naveen    

[Former Member]

Hi Naveen

Thanks for your suggestion!

However, RFC destinations work fine (both ways, I mean the one from PI -> ERP and vice versa from ERP -> PI)... connection tests are all successful.

A meta data refresh doesn't change anything... see my first reply above regarding this:

Sending IDoc from ERP -> PI however fails, see above posted error message from SM58. So the IDoc doesn't leave the ERP system at all.

Best regards

Renaud

[iaki_vila]

Hi Renaud,

Try to refresh the IDOC metadata. Check this thread

Regards.

[Former Member]

Hi Iñaki

Thanks for the quick reply! Unfortunately there is no IDoc Metadata to refresh yet.

Any other ideas?

Regards

Renaud

[iaki_vila]

Hi Renaud,

Have you check the first point in this document(CONFIGURATION REQUIRED FOR SENDER CHANNEL WITH IDOC_AAE ADAPTER TYPE) http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5050119d-9c47-3110-eab0-d90ebd211... ?

Regards

[Former Member]

Hi Iñaki

Great document btw... didn't stumble uppon this before. Thanks.

I carefully went through it but nothing I tried helped.

The RFC destination (PI -> ERP) is working fine.

The resource adapter (inboundRA) is configured correctly. I can confirm, that the connection test of the RFC-Destination inside ERP (ERP -> PI) is successful.

BUT still: sending an IDoc from ERP to PI fails with this message in SM58:

The IDoc Destination <destinationName> was changed. Refresh the destination instance with

Meldungsnr. SR053

This seems to happen every time after one changes some settings in the destination specified in the inboundRA property "destinationName".

So my question still is: how / where do I refresh this destination instance on a PI 7.4 Java Stack Only??? I mean without having to restart the whole PI instance...

Best regards

Renaud