cancel
Showing results for 
Search instead for 
Did you mean: 

Sender CC

Former Member
0 Kudos

Why sender CC is not required for IDOC n HTTP adapters ?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Idoc and HTTP adapters are in the ABAP stack. These two are directly goes to the Integration

server, thats why no need to crete the sender Aggrement and sender communication channel.

Based on the sender name, sender interface and namespace the Integration server identifies

the corresponding routing and the receiver system.

IDoc is a predefined structure thats why we don't create the Data type and message type.

We are creting the partner profiles, port and RFC destination, based on these things the

Integration server knows the destination system for the corresponding sender system.

IDoc, HTTP and XI adapters are inbuilt at Integration server, so the data converted to

XML at Integration server.

Answers (2)

Answers (2)

agasthuri_doss
Active Contributor
0 Kudos

Hi,

In Nutshell

IDOC and HTTP adapters reside on ABAP stack hence no need CC in Sender Side.

Regards

Sangeetha

Former Member
0 Kudos

Just think that IDOC adapter as a sender, that means, you are getting source file (IDOC) from R/3 (SAP) system definitely. And XI is also and SAP system. As both are SAP systems, we already have a way of establishing the connection between SAP systems, which is ALE configuration. Using which, you can easily transfer IDOC from R/3 to XI.

Also, you might know that IDOC and HTTP adapters reside on ABAP stack. When the R/3 and XI configuration settings are done, XI can receive the IDOC sent by R/3, directly to Integration Engine instead of Adapter Engine. If the file initially reaches to Adapter Engine, then the details about sender application are necessary, that means the Sender Agreement. But in this case, you don't even need the Sender Agreement.