InboundRA properties for IDoc->SOAP scenario on AAE. Really PI IDOC DEFAULT DEST??

[former_member560382]

Hi guys,

I need to configure an IDoc->SOAP scenario on PI7.4 using AAE, so I have to use IDoc_AAE adapter. That means using inboundRA adapter. I read a couple of blogs, but all of them say that the destination in inboundRA adapter should point to PI. But does it really make sense?? I assume this connection is used by the adapter to retreive IDoc metadata. If this assumption is correct , it maybe will work for standard IDocs, if PI holds their metadata, but definetely can not work for custom IDocs. Therefore I assume the destination in inbound resource adapter should hold the connection to ERP from which the IDoc comes. Is that correct(1)?

2. So potentially, if I use 2 different ECC backends with custom IDocs, I have to create 2 different resource adapters inboundRA_SID (1) and inboundRA_SID (2) which then would be used in my sender IDoc_AAE channel. Is it correct?

Thanks, Peter

[former_member190293 · Accepted solution]

Hi Peter!

Destinations point to respective SAP back-ends, not to PI. So, if you're connecting any SAP system to PI - you should have destination in PI, pointing to that system. If you haven't one - default destination is used.

Regards, Evgeniy.

[former_member560382]

Hi,

but if you develop Z Idoc in ERP ABAP, how can these metadata be loaded? If I am not wrong, when the InboundRA is called, it uses the destination to load the IDoc metadata. If you'd use default destination to PI, of course it can not find Z IDoc metadata as it has not been developed on PI, it has been developed on ECC, so the destination should point to ECC. Am I wrong?

[former_member190293]

Hi Peter!

1. If we're talking about "Destination Name" parameter in resource adapter's properties - it's the name of RFC destination pointing to SAP system.

2. No, it's not mandatory. Additional resource adapters are often used to connect different clients of the same SAP system to PI. Otherwise, you can use the same resource adapter for different systems maintaining fall-back destinations XI_IDOC_DEFAULT_DESTINATION_<SID> accordingly for each connected back-end system in your PI system.

Regards, Evgeniy.

[former_member560382]

Hi Evgeniy,

but the default PI default destination can not work if sending custom Z IDoc from SAP ERP, right? How would the PI then otherwise know the IDoc metadata?

So the default destination can work if using standards which are also held in PI ABAP. But not for custom.. Is this correct?

[former_member190293]

Hi Peter!

Why not? As far as I understand, default destination is used when no specific destination for back-end system could be found. And there's no difference between standard and Z-IDocs metadata to be loaded.

Regards, Evgeniy.