How does the System know which IDoc communication Channel to use?

[Former Member]

It is possible to define many IDoc communication channel Adapters for one system. Given that is the case, and that there is no need to create a sender agreement when using IDoc Sender Communication Channels, How do I know which IDoc Adapter is actually going to be used with ay particular message?

BR,

Tony.

[justin_santhanam]

Anthony,

> there is no need to create a sender agreement when using IDoc Sender Communication Channels

First of all there is no need to create Sender Communication CHannel itself.

raj.

[Former Member]

Hi,

You don't need a sender agreement/communication channel. The IDoc name decides which Receiver determination it has to go to

Just create the PORT and RFC destination pointing to XI

Regards

vijaya

[Former Member]

So if one communication channel has a different set of identifiers to another, which one is used?

[Former Member]

Hi Antony,

If your sender system is SAP, i.e. if you are sending idocs to XI, then you dont need any sender agreement or sender communication channel for any idocs out of SAP system. you only need receiver agreement, receiver cc, interface det and recv agreement.

Hence there is no question of creating many idoc adaptor channels. The RFC and port your created in your R/3 automatically identifies the sender idoc channel. you need not worry about it. this is because IDOC adaptor lies in the ABAP stack.

Hope this explain your doubt.

Regards,

Yash

[Former Member]

Hi Antony,

There is no need of Sender Agreement and hence sender communication channel. Sender Agreement identifies three things,

Namespace, Software component version and Outbound Interface. In Idoc communcation there is no need of Sender agreement as we can identify above things without Sender Agreement itself like namespace - Idocs have standard namespace and can be accessed across the sofwatware component versionsn and the idoc type it self specifies the interface name.

You cannot define a sender IDOC channel in Integration Directory due to fact dat IDOC adapter does not run in J2EE AF but is an 'built in" adapter.

Thanks,

Vijay Kumar T.