on 09-06-2015 7:15 AM
Hi All,
Could you please help me to understand why their is no sender communication channel required when we are communication with ECC.
Hi Bharath,
To simplify this, the 'Integration Engine' in PI can understand only 'XI-XML' msgs. It is the corresponding adapter which converts native msgs to XI-XML (ie, File adapter converts File based msgs to XML, Mail adapter converts emails to XML etc...).
Now coming back to Idoc adapter; Idocs are sending from R3 systems which already has ABAP Application sever (consists of local integration engine). Now the resultant msgs are already in a format which is understandable by the Integration engine of PI. Or in other way it is the 'local IE' of R3 system which communicates to the IE of PI. Hence no sender communication channel required for these kind of communications.
Same is the case of XI adapter as well.
Thanks & Regards,
Aby
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
We use 3 kind of communication to connect ECC (i.e. IDOC,RFC,Proxy). Can someone help me what the difference between them and which scenario we use those adapter ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bharath,
IDOC
We can go for IDOC when there is a asynchronous communication. IDOCs come with rich logging, error handling and workflow integration in the back end R/3 system.
Proxy
When there is a requirement for synchronous communication and entire solution needs to be implemented from scratch we can go for proxies instead of IDOC.
we can use Proxies only if the WAS version is >= 6.20.
RFC
best suited for synchronous communication from SAP R/3. by using RFC we can send the data to remote systems as well.
Note:
if the standard IDOC/ RFC is already available which will fulfil your requirement then you can go for IDOC/ RFC based on your requirement [Asynch / Synch].
If there is no standard IDOC / RFC is available all needs to be implemented from scratch then we can go for proxy instead of Z IDOC/ RFC.
Please refer the below link for your reference.
Regards
Bhargava Krishna
Bharath,
An adapter/communication channel performs the protocol conversion from or to the native PI protocol which is XI 3.0(say for ex: Sender -> FTP to XI 3.0 or Receiver -> XI 3.0 to FTP).
When ECC send a message to PI, it is using XI 3.0 protocol which is the native protocol in PI.
So no communication channel is required.
Also for dual stack for IDOCs also channel is not required at sender as both are abap and data is exchanged with tRFC and function modules handles the format conversions.
regards,
Arun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.