Http,idoc adapter

if we choose the adapter type as idoc,http the channel direction defaults to receiver why?

Hi Narendra,
The plain HTTP adapter is generally  used by external systems to connect to the Integration Engine using the native HTTP interface (HTTP payload without SOAP envelope),which is why its default comm channel is receiver
Also ,a communication channel with a receiver HTTP adapter can be created automatically for business systems that are defined in the System Landscape Directory
check this http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/frameset.htm

Similar Messages

  • Why we r not Creating Sender Agreement For HTTP & IDOc Adapter at Sender .

    Hi Buddy's,
                         Why we r not Creating Sender Agreement For HTTP & IDOc Adapter at Sender .And why we create receiver agreements at receiver side bt not sender agreement at sender side.
    Wat Is GLOBAL Container ?, where it will Occur & wat is the functionality of that.

    Kumar,
    1) XI integrattion server - IS expects the messages in XML format. If you see the HTTP request you will see that we pass all the info contained in the Sender areement in the the HTTP request itself , namely - Message interface, message type and the namespace (along with login parameters). For IDOCs the the IDOC- XML are are sent to the IS (through IDOC port configuration at the source system.
    2) When send a message to XI the sender knows that XI system parameters, but when at the reciver end there could be any any system that is reciving the IDOc/HTTTp message. you specify those message through a commumication channel and this channel is associated to a receiver agreement.
    3) A Global container is like a place holder for variables. You can set a variable here and access it throughout your mapping and hence the name.
    A good example for a gloabal container is a counter to countthe number of records in te target side.
    Regards,
    Arvind ravindran

  • Sender agreement & communication channel not needed in case of IDOC adapter

    Hello everyone ,
       I am new to xi , as far as i know a communication channel cannot be created in ID when using IDOC adapter , the answer for this question is like , the idoc adapter resides on the integration server & not part of j2ee AF .
    Can some one explain me in the terms of a laymen , its not clear to me.
    Thanks & Regards,
    Reena.

    Hi ! Reena
    IDOC adapter resides on Integration server, so Integration engine takes care of the conversion format from IDOC to XML, hence there is no need for sender Adapter .Also since its residing on Integration server you can directly post the message in the Integration engine.
    well lemme explain a little bit,the main reason for sender agreement is to associate namespace with the sender adapter,now when we shoot IDOC from R/3 it already contains its standard SAP namespace so no need of sender agreement.
    now comes the sender CC,main use of sender CC is to identify the sending system and the adapter.the IDOC header contains details of all the this,so again there is no need for sender CC
    loook at this thread discuss the same
    Re: Why we r not Creating Sender Agreement For HTTP & IDOc Adapter at Sende
    Re: why HTTP & IDOC adapter do not require sender communication channel?
    Thanks!!
    Questions are welcome here!!
    Also mark helpful answers by rewarding points
    Regards
    Abhishek Agrahari

  • SP14 Multi-mapping - error in receiver idoc adapter

    Hi,
    I have a scenario where a business service should send some XML to SAP CRM. I get the file via a sender JMS adapter and try to post it to CRM via a receiver IDOC adapter.
    I have created a multimapping (1:N - 1 XML file to many Idocs) as should in the repository.
    In the configuration under Interface Determination, I have chosen 'RB_SPLIT' and selected the interface multimapping.
    It should be pointed out, that when testing both interface and message mapping i get no error. All idocs seem to be created as they should.
    When testing the setup 'real life' the message fails. The error message in the monitor says:
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
      <SAP:P1>InterfaceCollection</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to interpret IDoc interface InterfaceCollection</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Notice that the above error is when trying to send only 1 record, which in turn then should result in only 1 idoc.
    If trying to send multiple XML records, i get the following error:
    - <!--  Technical Routing
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="OUTBINDING">MMF_ENGINETYPE</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>A system error occurred in the outbound binding</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    In the monitor in the payload of 'Request message mapping' I see as many Maindocument, Submaindocument pairs as should be Idocs.
    Now i really don't know how to interpret the error messages in both cases, so I'm a little lost here...
    It should be pointed out that the idoc being used everywhere in this scenario, has not been modified - from all places it is being used (and only exists) in the 'Imported objects | Idocs' place.
    Also the Idoc is also being used as Inbound interface - so no mistakes here either.
    I really hope someone can help me here, as I'm otherwise pretty stuck in this case.
    Best regards,
    Daniel

    Hi Daniel,
    I have exactly the same type of scenario (under SPS14 and now also SPS15), sending an XML message over JMS to XI and trying a multi-mapping to many IDocs (actually a list of orders in XML is mapped to n ORDERS Idocs).
    I also face problems doing so, when I use the IDoc Adapter as outbound in the Receiver Agreement. I receive the following error:
    <i>CO_TXT_MMF_ENGINETYPE
    Messages in multi message format can be sent to one adapter engine only</i>
    However, I tested the same scenario by just changing the Receiver Agreement to a File Communication Channel and - surprise, surprise - it works. One file per IDoc is created.
    Of course, this is not what we want to accomplish, but when I checked this piece of documentation (sorry another link
    http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/content.htm
    the IDoc adapter is not listed in the list of Adapters that are supported. Does that mean, that this feature is not supported for generating IDocs? Maybe that's a question for a SAP OSS Message?
    I hope that helped you a little further - if you find out more I'd be happy to learn about it.
    regards,
    Peter

  • Problem with an Receiver Idoc adapter

    Hi.
    We have just went from XI 3.0 to PI.7.10.
    The Receiver idoc adapter is set up in the same way as it was in XI.
    The problem is when two different interfaces runs at the same time I got data into the DC40-record which not belongs too this idoc but from an another interface/idoc.
    The idocs are different messagetypes.
    In this case the field MESCOD which belongs to one of the idocs also appered in the idoc where the field MESCOD not should be used.
    Any idea whats wrong ?
    /Per-Arne

    Thanks.
    Checked sxmb_moni as you said.
    In the OutboundBinding-node I can see the right idocadapter is used
    where 'Apply Control Record Values from Payload' is enabled.
    <SAP:ChannelName>IDOC_INBOUND_U01_110</SAP:ChannelName>
    In the IdocOutbound-node I can see the message code 'EXT' which should'nt be there.
    - <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
      <SAP:MANDT>001</SAP:MANDT>
      <SAP:DOCREL>710</SAP:DOCREL>
      <SAP:DOCNUM>0000000000033474</SAP:DOCNUM>
      <SAP:DIRECT>2</SAP:DIRECT>
      <SAP:IDOCTYP>OILLDD01</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>OILLDD</SAP:MESTYP>
      <SAP:MESCOD>EXT</SAP:MESCOD>
    Too be more specific about the interface.:
    I got one file in from a file adapter and out of that file I produce two idocs into R3 whit
    two different idocs-adapters.
    I think you are right about that the configuration may be mixed up.
    Any idea of what I can do?
    It may be an PI 7.10 bug ?
    Shall I delete all config objects and so set config up from scrach again ?
    /Per-Arne

  • ** Port is missing from the IDoc control record  (Receiver IDoc adapter)

    We are using a File to IDoc scenario and in the idoc sap sender port is not coming due to this IDoc posting is failing. Could any one tell us why idoc adapter is not able to get SAP port.
    The following is the error message in SAP side.
    Status : 56
    IDoc: 0000000006188579 Status: IDoc with errors added
    EDI: Partner profile inbound not available
    Kindly help me friends.
    Thanks,
    Jagathees P.

    hi,
    >EDI: Partner profile inbound not available
    this error message means that there is not partner profile
    configuration for this IDOC (you configure it in WE20 of ERP/R/3 )
    or your XI system is configured to post to a wrong partner profile
    (if you fill your partner data in a mapping for example)
    so it's one of the other for sure - check it/change it and it will work
    for more info about IDOCs and XI you can check my book:
    www.sap-press.com/product.cfm?account=&product=H1935
    Regards,
    Michal Krawczyk
    http://mypigenie.com XI/PI FAQ

  • Http - iDoc scenario - ID

    Hi,
    HTTP - XI - iDOC  is my scenario.....
    i am facing problem in iDoc adapter...
    the error category is idoc adapter and the error id is "ATTRIBUTE_INV_SND_SERV"
    Which RFC destination and port should in mention in Communication Channel? Either the receiver or XI?
    forward your suggestions....
    Thanks,
    RPN

    hi rpn,
    check this links
    Go to Int. Directory -> Double Click on your IDoc Business System -> Menu -> Service -> Adapter Specific Identifiers
    Maintain Logical System name and System ID and Client number.
    Check the following blog.
    The specified item was not found.
    Unable to convert sender service to an ALE logical system
    ATTRIBUTE_INV_SND_SERV
    XI 3.0, Party and Service problems (IDoc inbound)
    Trouble shooting file to IDOC and IDOC to file
    Troubleshooting  File-to-IDOC Scenario in XI.
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
    see the below links
    ALE configuration for pushing idocs from SAP to XI
    Introduction to IDoc-XI-File scenario and complete walk through for starters.
    idoc settings Configuration steps required for posting idoc's(XI)
    Also
    /people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
    IDOc testing - Generate Test Case for an IDOC Scenario
    regards
    srinivas

  • Time Zones problem in IDoc Adapter

    Hello,
    we have a problem regarding time zones. We send an IDoc from an external system to the XI IDoc adapter. the external system has only one time zone which is set to CET. Our SAP XI system as well as the op system is also set to CET and the same also goes for all user properties.
    We need the value of "TIME_SENT" from the xml message header to achieve our mapping. This works out pretty good but unfortunately we find the wrong time in the xml message header, which is UTC in this case.
    Does anyone know where in the J2EE engine or in the IDoc adapter this UTC date comes from and where to configure the time zone?
    Thanks in advance
    /Michael

    hi once more:)
    maybe check you j2ee too:
    log on to
    http://server:port/sap/monitoring/SystemInfo
    then choose system properties for your server
    inside you'll find user.timezone
    check if this value is ok
    Regards,
    michal

  • Process flow of IDoc adapter in SAP PI

    Hi Experts,
    can any one pls send me about IDoc adapter in SAP PI/XI, which covers a complete info of IDoc adapter.
    i mean complete in and out about IDoc adapter.
    with rgds,
    MF

    Hi
    If you do a search, you will get lots of material.
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b2b4035c-0d01-0010-31b5-c470d3236afd
    IDOC Adapter
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/idoc%252badapter
    These links should help you out
    Thanks
    Saiyog

  • HTTP receiver Adapter configuration

    Hi All,
    I want to post an XML message using HTTP Receiver Adapter for my BPM scenario (Idoc to HTTP service)
    The receiver has Oracle gateway and it expects message in following format.
    HTTP Header
       Http–Version: HTTP/1.1
       Authorization: Digest username=”myusername”,
                             realm=”[email protected]”,
                             nonce=”dcd98b7102dd2f0e8b11d0f600bfb0c093”,
                             uri=”/dir/index.html”,
                             qop=auth,
                             nc=00000001,
                             cnonce=”0a4f113b”,
                             response=”6629fae49393a05397450978507c4ef1”,
                             opaque=”5ccc069c403ebaf9f0171e9517f40e41”
                             Content–length: 12345
                             Content–type: text/html
    HTTP Body
       TRANSPORT_PROTOCOL=OXTA
       TRANSPORT_PROTOCOL_VERSION=1.0
       REQUEST_TYPE=SEND
       MESSAGE_ID=A1234567890ZZ0987654321
       MESSAGE_TYPE=XML
       MESSAGE_STANDARD=OAG
       TRANSACTION_TYPE=PO
       TRANSACTION_SUBTYPE=PROCESS
       DOCUMENT_NUMBER=12345
       PARTYID=9999
       PARTY_SITE_ID=8888
       PROTOCOL_TYPE=HTTPS–OXTA
       PROTOCOL_ADDRESS=HTTPS://www.me.com/servlets/oracle.ecx.oxta.
       transportAgentServer
       USERNAME=myusername
       PASSWORD=myloginpassword
       ATTRIBUTE1=
       ATTRIBUTE2=
       ATTRIBUTE3=
       ATTRIBUTE4=
       ATTRIBUTE5=
       PAYLOAD=<xml ... ...>
    I think this is not a typical HTTP URL type of format, is it?
    And I am not sure how I can build the message. Where do I put the parameters like TRANSPORT_PROTOCOL, TRANSPORT_PROTOCOL_VERSION, REQUEST_TYPE etc in the HTTP adapter?
    Also is there any place where I can see the final actual XI message that is sent to HTTP service?
    Any help will be really appreciated.
    Thanks and regards,
    Rahul.

    Hi Rajeev,
    The receiver system should have the details about the content type it expects. I got that from the team who monitors our receiver system.
    The HTTP Body of HTTP adapter is made up of PrologPayloadEpilog.
    So I added the paramter list that receiver system expects as part of the Prolog. Refer to the HTTP body that I have posted in my earlier message. Out of that till ".....Payload=" is added to Prolog and XI then appends actual payload to it.
    To be precise -
    TRANSPORT_PROTOCOL=OXTA&TRANSPORT_PROTOCOL_VERSION=1.0&MESSAGE_TYPE=XML&MESSAGE_STANDARD=UNIVERSAL&TRANSACTION_TYPE=XXXE&TRANSACTION_SUBTYPE=ORDER_I&DOCUMENT_NUMBER=PO12345&PARTY_SITE_ID=ESAP_ORDER_I&USERNAME=***&PASSWORD=**&PAYLOAD=
    So in the end it worked out well.
    Cheers,
    Rahul.

  • Remove namespace alias for HTTP receiver adapter

    hello all,
    I have a scenario, IDOC->XML (HTTPS). Standard output of PI has ns0: as prefix for each xml tag (ns0 alias for namespace)
    I want to remove the namespace alias while preserving the namespace in the output. So removing namespace reference in external definition is not a option.
    Is there any way to use XMLAnonymizerBean for HTTP receiver adapter? What are other alternatives (java mapping)?
    Thanks,
    sachin

    Thanks stefan, prateek.
    Prateek: I checked this blog earlier. It talks about inbound processing. My scenario is outbound HTTP and I am not sure how I can use specific adapter service as mentioned in blog in outbound case as other scenarios are using standards adapter_plain service.
    Stefan: I will try this approach.
    regards,
    sachin

  • Java IDoc adapter in PI 7.3?

    Hi Gurus,
    As there has many new features added in PI 7.3 version,anyone advise how to test its IDoc(java) feature via some scenario?or suggest some scenario to assess the IDoc adapter based on java functionality.
    Any comment would be much appreciated.

    Hi Rajesh,
    refer below links, it gives clear picture
    http://help.sap.com/saphelp_nw73/helpdata/en/71/21dfa45a5143ae9fe115f8c62b1801/frameset.htm
    http://help.sap.com/saphelp_nw73/helpdata/en/c2/91865252c84716b3b8be394851c9c0/frameset.htm
    Regards,
    Raj

  • Message split on adapter engine for the java based IDoc adapter

    Hi Guys,
    Do you know if message split on adapter engine is available for the java based IDoc adapter on the single stack (PI 7.31)?
    I'm getting such exception when I try to post 3 IDocs
    Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: Invalid XML 1.0 character encountered within IDocXML for type <ns0:Messages>:
    state=EXPECTING_IMMEDIATE_TAG_END, charPosition=68, lineNumber=1, columnNumber=69, invalidChar=U+0078,
    sourceSnippet=...UTF-8" standalone="no"?><ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1><...
    ^
    Mapping is one to many.
    Each IDoc content has been compared manually against the xsd schema and it was fine.  
    I know that old way of modifying xsd is still possible.
    Best regards,
    Wojciech

    Did you find a solution to this? Having a similar error right now.
    Thanks and kind regards
    Jens

  • Error using IDOC adapter

    Hi All,
    I'am trying to run the following scenario:
    FILE --> XI --> IDOC (r/3).
    Data is read and mapped towards an internal format. Then a mapping from the internal format to MATMAS_BAPI01 is done.
    I disabled EDI_DC40 and did the needed mappings.
    When I execute the scenario I get the following error.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>MSGGUID CA9DC2E01F1211DA9EED000D56B9D8A6: Control record must start with tag EDI_DC40, not E1BPMATHEAD</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: MSGGUID CA9DC2E01F1211DA9EED000D56B9D8A6: Control record must start with tag EDI_DC40, not E1BPMATHEAD</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I expected that the XI system would automaticly fill in the needed info in EDI_DC40.
    Does anyone has an idea what is going wrong?
    Kind regards
    Message was edited by: Geert Wouters

    hi,
    most probably your idoc message
    has a wrong format
    when you import your new idoc to integration repository
    does it have EDI_DC40 at the beggining?
    BTW
    try without disabling the edi_dc40
    you cna also have a look at my weblog:
    /people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
    Regards,
    michal
    Message was edited by: Michal Krawczyk

  • How to configure the Http sender adapter

    Now i have look through the sap lib about the http sender adapter
    and i know the url is
    http://hostname:port/path?namespace=<...>
    &interface=<...>&service=<...>&cmd=T&loaderXML=< message object >&end=yes
    My questions are:
    1)the path in the URL is "/sap/xi/adapter_plain", if not, what is it?
    2)the message payload is right?
    any reply is appreciated
    Thank you very much

    Hi Leo,
    For a HHTP Scenario:
    DESIGN:
    1. Create DataTypes for source and Destinations. Create elements for all the text fields of your HTTP Client so that they can all be mapped into the destination file
    2. Create MessageTypes for the two datatypes.
    3. Create Message Interfaces. The One for HTTP is the sender, Asynchronous ( as no response is expected) and one for File is receiver, asynchronous.
    4. Do the mapping. It will be mostly a one to one mapping of the fields.
    5. Create the Interface Mapping.
    Configuration:
    1. Import your Business System under your Configuration Scenario.
    2. Create 2 communication channels. One for Http as a sender and one for your receiver say IDoc.
    Check these links for the configuration part.
    http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
    3. Do the Receiver Agreement for Idoc. HTTP doesn’t need a sender agreement.
    4. DO the Receiver Determination and Interface Determination.
    Weblog which talk about the same scenario:-
    /people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - although this weblog is
    aimed at explaining the sync-async bridge.. Sriram has taken http-to-file scenario as the example
    (use case) and explained it...
    Check this SDN tv demo, it has detail of HTTP adapter setup.
    https://media.sdn.sap.com/SDNTV/main.asp?mediaId=107
    Refer to this link for adapter settings.
    http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
    You should also have a HTTP client to send message to XI. In the connecting parameters to XI u have to use the URL in the pattern mentioned . U have to give all the configuration details in the URL.
    If you give me your mail id or if you can mail me at [email protected], i can send you a HTTP CLIENT.....In which you need to view the source code and change the username and password to send message to XI.
    Regards,
    Abhy

Maybe you are looking for