Skip to Content
avatar image
Former Member

Regarding CC

Hi

Why sender CC is not required for IDoc and HTTP ?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Best Answer
    avatar image
    Former Member
    May 11, 2008 at 02:40 PM

    Hi

    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.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 11, 2008 at 08:31 AM

    Hi Satya,

    Try to use IDOC and HTTP Adapter as a sender you will get the ansewer to your question .You need not to enter any parameter when you use these adapter as sender unlike file or any other adapter (In layman term) .

    Techinically IDOC and Http Adapter Resides on ABAP Stack so they can communicate with each other when any one of these adapter are to be used as sender .

    MOreover for IDOC as a sender we create RFC port through which it sends data to XI .

    Reward points if Helpful

    Thanks

    Sunil Singh

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 12, 2008 at 09:18 AM

    HI

    Idoc adapter resides on the ABAP engine and the Idoc is sent directly to the Integration Engine of XI from the R3 system hence no sender idoc adapter and no sender agreement for the idoc adapter. The IDOC Adapter is implemented in ABAP and reside directly on the Integration Server (ABAP Stack).Hence cannot define a sender IDOC channel in directory due to the fact that the IDOC adapter does not run in J2EE Adapter Framework but is an "built in" adapter same for the HTTP adapter also.

    The IDOC Adapter is implemented in ABAP and reside directly on the Integration Server (ABAP Stack).You cannot define a sender IDOC channel in directory due to the fact that the IDOC adapter does not run in J2EE Adapter Framework but is a "built in" adapter.

    .Idoc adapter resides on the ABAP engine and the Idoc is sent directly to the Integration Engine of XI from the R3 system and so , no sender idoc adapter and no sender agreement for the idoc adapter.

    cheers

    reward points if found useful

    Edited by: vemuganti naga phalguna on May 12, 2008 11:18 AM

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 10, 2008 at 06:31 PM

    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.

    Add comment
    10|10000 characters needed characters exceeded

  • May 11, 2008 at 01:43 PM

    Hi,

    In Nutshell

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

    Regards

    Sangeetha

    Add comment
    10|10000 characters needed characters exceeded