Synchronous IDoc - SOAP scenario

Hi all,
Our current scenario is like this: SAP (Idoc) -> XI -> SOAP (Idoc). The receiver system will reply with an ALEAUD Idoc as in: legacy (IDoc over SOAP) -> XI -> SAP IDoc).
We have a requirement to wait with sending the next IDoc from XI to receiver Web Service on legacy side until we get an ALEAUD IDoc back for the previous IDoc sent to the Web Service.
How can we implement this?
Is BPM necessary?
As far as I know you can only set the QoS for sender adapters, and the SAP Idoc scenarios are always asynchronous. But we can implement a synchronous send step in a BPM with ALEAUD as response message. This will solve our problem, correct?
Any other way? We would like to avoid using BPM.
Any help with this is highly appreciated!
Br,
Kenneth

Thanks for your reply, Udo:)
I am currently building the BPM now.
So, you are saying that I cannot create an inbound sync MI with input message IDOC and response message ALEAUD?
We want to send ACC_GL_POSTING IDoc (or identical structure) to a Web Service and receive the ALEAUD from the legacy system through a Web Service published on XI. We want to relate these two so that the BPM finishes when it receives the ALEAUD, and can then send the next ACC_GL_POSTING IDoc.
I have created the following objects in repository:
MI_ACCGLPOSTING_ASY_ABS (in receive step in BPM)
MI_ACCGLPOSTING_ALEAUD_SYN_ABS (in send step in BPM)
MI_ACCGLPOSTING_ALEAUD_SYN_IN (used for receiver interface towards legacy SOAP adapter)
MI_ALEAUD_ASY_ABS (used for send step in BPM)
I believe no mappings are necessary since we are not doing any conversions.
Can you please confirm that this looks correct, and also provide what settings I need in Directory?
Thanks a bunch!
-Kenneth

Similar Messages

  • Synchronous Proxy - SOAP Scenario (Error 500 in Response).

    Hi
    I've built a few Synchronous Proxy -> SOAP Scenarios,
    with 'Do Not Use SOAP Envelope' option.
    For two of them, I'm facing a common error.
    The error is: ADAPTER.HTTP_EXCEPTION (HTTP 500 Internal Server Error).
    When I paste the EXACTLY SAME payload picked up from XI, into the SOAP client, it works giving valid response.
    Trying to figure out the issue.
    R/3 System:
    WAS 620 (Level 0041)
    XI System:
    PI 7.0 (Level 0007)
    SOAP System:
    BizRights (Approva) 3.0
    Any help is appreciated.
    Rajendra.

    Hi,
    Following SAP notes may help you-  804124, 807000
    Regards,
    Moorthy

  • IDOC - SOAP scenario

    Hi Guys,
    I have configured the IDOC-SOAP scenario and i am sending to the target business partner with the soap receiver adapter.
    I did not get any wsdl from the business partner instead i got the xml structure, target url and soap action. I have created a xsd for the given xml and send the data to the business partner.
    The data is reacing the target system but the xml document has error saying "invalid at the top level of the document" and no xml is seen. I also get an acknowldegment error in sxmb_moni as
    OUTBINDING  CO_TXT_Routing_Back_Error
    Error occured during back routing, error in communication channel
    any help would be appreciated
    Thanks,
    Raj

    I think this comes because XI requests Acknowledgement-IDocs by default. In many cases nobody processes these IDocs and so you get this error. Have a look at OSS-note 777175:
    You are using Exchange Infrastructure 3.0 and receive IDocs using the IDoc
    adapter. You want to be able to request acknowledgments separately in the
    XI for each sending system and interface. In the IDXNOALE exception table,
    you can deactivate acknowledgments for certain systems or interfaces.
    Previously, you could only maintain the table with transaction SE16.
    Report IDX_NOALE is delivered with Support Package 10. With the report, you
    can add, delete and display table entries.
    Report IDX_NOALE is extended with additional functionality as of Support
    Package 11. This allows a sender system to request or deny acknowledgements
    for all message types centrally. You can set exceptions to this central
    setting by message type. Generic exceptions (for example, message type
    'ORD*') are not supported. Entries that are already present in the table
    are unchanged.
    To perform these activities, you need the authorization to maintain IDoc
    metadata (Object 'S_IDOCMETA' ID 'ACTVT' FIELD '02').
    Hope this helps.

  • Synchronous RFC -- SOAP Scenario: problem with SOAP Response/Fault Mapping

    Hi,
    I've a synchronous RFC --> PI --> SOAP Scenario. The problem is that the message structure of the sending RFC doesn't match the Webservice Structure.
    The (SAP standard) RFC has just a Request / Response message structure. Part of the Response Message structure is a exception structure.
    The Webservice has a Request / Response message structure and in case of an error I get a SOAP:Fault.
    Problem now is that I cannot configure that scenario without usage of BPM as I will have to map SOAP:Response or SOAP:Fault to the RFC Response structure.
    Has anybody another idea to do that synchronous scenario (with usage of message mapping) without BPM?
    BR
    Holger

    1)
    you maus define 3 mapping.
    1)request
    2)response
    3)Fault
    in Interface mapping define at response boths (2-3) mapping. its clear??
    2)
    otherwise sometjhing is not clear, why do you want fault?? why dont you  get only response message. we implement this kind of response:
    <response_MT>
    <ID> (error ID)
    <system> (target system) 
    <error> (Error Description)
    </response>
    by this way fault message is not needed. but if you must have it just follow the top of message else, propose second.
    Thanks
    Rodrigo
    Thanks
    Rodrigo
    Edited by: Rodrigo Pertierra on Feb 25, 2008 11:52 AM

  • Synchronous File- Soap scenario with fault message

    Hi!
    I have a File to Soap synchronous scenario.
    All is right when no exception is returned by the web service.
    I want to use fault messages to catch thoses exceptions, so I have added fault message in message interfaces and in the mapping program in the interface mapping.
    Now, when the web service return an exception like :
    <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
       <soap-env:Body>
          <soap-env:Fault>
             <faultcode>soap-env:Client</faultcode>
             <faultstring xml:lang="en">NOT_CREATED</faultstring>
             <detail>
                <n0:Z_WS_CREATE_WAGON.Exception xmlns:n0="urn:sap-com:document:sap:rfc:functions">
                   <Name>NOT_CREATED</Name>
                   <Text> does not have packaging material type and is therefore not a pack.mat.</Text>
                   <Message>
                      <ID>HUSELECT</ID>
                      <Number>041</Number>
                   </Message>
                </n0:Z_WS_CREATE_WAGON.Exception>
             </detail>
          </soap-env:Fault>
       </soap-env:Body>
    </soap-env:Envelope>
    I get the following error :
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
       <SAP:Category>XIServer</SAP:Category>
       <SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
       <SAP:P1>http://www.arcelormittal.com/radis/rad IM_RAD_to_ZWsCreateWagon</SAP:P1>
       <SAP:P2 />
       <SAP:P3 />
       <SAP:P4 />
       <SAP:AdditionalText />
       <SAP:ApplicationFaultMessage namespace="" />
       <SAP:Stack>Interface mapping http://www.arcelormittal.com/radis/rad IM_RAD_to_ZWsCreateWagon does not exist in runtime cache</SAP:Stack>
       <SAP:Retry>N</SAP:Retry>
    </SAP:Error>
    My mapping program for fault message is well defined (I tested it with the exception message received from the web service).
    I have also refresh caches, but without success...
    Can anyone help me ?
    Thanks in advance,
    Laurence

    Hey Laurence,
    A File adapter is aysnchronous u cant use for synchrous because it cant acknwlodge the response it gets or itt sends.
    regarding two asynchoronus
    1. file to SOAP asychn.
    2. triggger the second one if SOAP has exception then pass the error from SOAP to New File.
    using BPM we have to use Transportion level acknowledgments
    please reward points if it helps
    Regards
    Sreeram.G.Reddy

  • Timeout Error in a Synchronous XI - SOAP scenario

    Hi All,
    I have developed a Synchronous ABAP proxy to SOAP web service scenario.
    ECC sends an ABAP proxy request to PI, PI forwards the request to the target system as SOAP message.
    I have checked the interface via SOAP UI and it works fine but when we run the end-to-end flow it always ends with a Synchronous timeout error.
    The Target system confirms that the response is sent from there side but in PI we are not receiving any response and the system throws a  timeout error.
    As both PI and the Target system are in same Landscape there is no firewall in between.
    Please suggest what can be the possible reasons and the approach to resolve the same?
    Thanks in advance,
    Shashank

    Hi,
    "The target system needed credentials for one  inbound interface, so for this synchronous scenario(PI<->Target) should the target system maintain credentials some where when the response is sent back to PI as the SOAP channel is on Java Stack?"
    Generally for receiver channel we get the user name and password from target system ie web service.
    How did you test in SOAPUI? did you test it with providing username and password or not?
    even if web service requires user/pwd then it will throw 401 unauthorized error.
    check this
    can you go to RWB-->component monitoring-->adapter Engine-->communication channel monitoring-->your channel
    check if the channel has any errors/exceptions logs.
    Regards,
    Muni.

  • Problem in IDOC to SOAP Scenario

    Hi All,
    we have an IDOC to SOAP scenario in which we have got WSDL from the client for the targets.. Please let us know the WSDL would be the message type and we need to create interface for it . Also the SOAP header is not appearing in the target  xml.
    Thanks

    Hi ,
    This means when the data is sent to the webservice it will contain the SOAP header just that we cannot see it in Moni . Also
    What about the acknowledgement . Our message is successfull but with message that awaiting acknowledgement.
    What we basically need a synchronous scenario of IDOC to SOAP but the response not going back to SAP-R3 . We recieve the response only in SAP-PI. Saw some blogs but the message is going back to SAP-R3. Please help us on this
    Thanks
    Edited by: vishal  gadkari on Aug 22, 2009 4:15 PM

  • Error in SOAP receiver channel in Synchronous Proxy to SOAP scenario

    Hi all,
    We are experiencing an issue with a synchronous Proxy to SOAP scenario. Getting below error message in the SOAP receiver communication channel for the response message.
    SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
    Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: Could not determine mapping steps for message 1364b76e-ecbf-11e4-85f4-000023acfde6.
    We are running PI 7.4.
    Any help is appreciated.
    Thanks,
    Pushpa

    Hi,
    Seems the Receiver Webservice is not reachable. Did you try to test it using SOAP UI tool.
    1. Test a fresh message from local SOAP UI tool.
    2. Pick 3rd party WSDL file and Import in SOAP UI tool.
    3. Put some dummy data for mandatory fields
    4. Trigger it msg and ckh if you get successful / response msg.
    5. Check if firewall is open and that URL is not blocked.
    Hope it helps
    Regards,
    Azhar

  • Soap -- XI -- IDOC/RFC scenario

    Hello,
    I have a jsp page that working in tomcat server.
    I want to send values from jsp page to xi to r/3. I think it will have
    soap-- xi -- IDOC/RFC scenario
    Pls send me pdf /doc to implemet it
    Regards

    Hi,
    Please Refer the Following Links
    /people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
    /people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
    /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi - Invoke Webservices using SAPXI
    /people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
    Regards
    Khanna

  • IDoc to SOAP scenario is showing error

    Dear Experts,
    We were trying a scenario which is IDoc-XI 3.0->SOAP and where the WebService is situated outside our office network. Our network team have bypassed proxy for accessing that WebService URL and the same is accessible from our XI3.0 application server from browser. We have configured the scenario and when we have tested the scenario from RWB->Component M onitoring->Integration Engine->Test and this has worked fine. But when we have tested the scenario by triggering IDoc from the R/3 system, it is throwing the below mentioned error in both at the comm chanel and at the SXMB_MONI acknowledgement.
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 403 Service Error
    points to be noted here:
    1. Business Service has been configured correctly for triggering ALEAUD messages and ALEAUD messages are reaching R/3 successfully.
    2. We have chosen option Keep Headers and Do not use SOAP header options.
    3. We are passing some values to the SOAP Header from SOAP channel.
    Please could somebody help us on the root cause of the error message.
    We have run report IDX_NOALE for that particular IDoc so that it doesn't return any acknowledgement back to the R/3 system.
    Thanks and regards,
    Sugata
    Edited by: Sugata Basu on Nov 19, 2011 12:40 PM

    Dear,
    IDoc to Soap scenario we have to import wsdl at receiver end and map the field from the mapping document but some times receiver end some changes may happen. if it is correct only your mapping we have to conclude from the below points.
    1. Check the mapping in Message Mapping and Operation Mapping Test and conclude.
    2. you should check url from receiver that is correct or wrong.
    3. ask the wsdl from receiver end.
    the given ED and receiver side application is same this type of error will not come.
    Please check at receiver application or else what ever new fields are added in reciver may be miss mach of ED.
    Regards,
    Kiran Polani

  • Error in synchronous( abap proxy to soap)scenario

    Hi experts,
    My scenario is synchronous abap proxy to sysnchronous soap. for proxy I am using business system name as ERDCLNT220 and soap business system name as BS_HRS_DEV
    configuration steps are
    1. only client proxy to soap scenario I have done.
    communication channels: only receiver soap adapter. no proxy sender communication channel for client proxy.
    Already we have RFC destination connection and connection type H for proxy to xi.
    1.Is it required RFC destination connection for xi to server proxy.
    2.Is it required receiver proxy communication channel for server proxy?.
    i HAVE TESTED THIS INTERFACE. I am able to send the request. But I am not able to receive the response from soap webservice message .
    error is:
    SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
    exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
    Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
    Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson. Setting message to status failed.
    Kindly help me.
    advance thanks
    thanks and regards
    elton
    Edited by: eltonsaranya on May 9, 2011 10:27 AM

    Your exception message shows problem at the webservice side.
    Check the following:
    a) you need two mappings one for proxy req to soap request and other soap response to proxy response
    b) You need to create service interfaces both sender and receiver synchronous .
    c) communication channel  QOS is best effort for both sender and receiver
    d) I dont see problem in soap configuration. Bcuz you are able to ping and while getting response from the method getPerson it fails.
    f) See your SOAP response structure matches with WSDL provided.
    g) You can also test outside PI.. I meant testing via soap client tool like SOAPUI  for that web service. So that you know whether problem exists on the target system or not.
    Hope that helps.

  • Idoc to soap scenario - soap response error

    hi
    i am using pi 731 single stack.
    the scenario is idoc to soap. the message mapping is working fine and output is generated successfully.
    the message is failing in mesage monitor and communication channel monitor. error is -
    Exception caught by adapter framework: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: VEN-OMI-1007:
    This scenario is async scenario. How to soap remove this response message error.
    rgds

    Dear,
    IDoc to Soap scenario we have to import wsdl at receiver end and map the field from the mapping document but some times receiver end some changes may happen. if it is correct only your mapping we have to conclude from the below points.
    1. Check the mapping in Message Mapping and Operation Mapping Test and conclude.
    2. you should check url from receiver that is correct or wrong.
    3. ask the wsdl from receiver end.
    the given ED and receiver side application is same this type of error will not come.
    Please check at receiver application or else what ever new fields are added in reciver may be miss mach of ED.
    Regards,
    Kiran Polani

  • IDOC to XML SOAP Scenario

    Hi All,
    I want to implement IDOC to XML SOAP scenario for 3 different IDOC types.
    Should i implement it under same namespace or use different namespace for each IDOC to XML scenario.
    Thanks,
    Vishal

    Hi,
    depends on your requirement and your XML SOAP receiver
    there are no general rules
    Regards,
    Michal Krawczyk

  • Explain about Idoc to soap scenario

    Hi All,
    I am beginner to sap pi can anybody help me out, How to perform Idoc to soap scenario...

    Dear Gaffar,
    Please use the search functionality to learn.
    Redirecting...
    http://www.google.com/cse?cx=013447253335410278659%3Ak8ob9ipscwg&ie=UTF-8&q=idoc+to+soap+scenario&siteurl=www.google.com…
    try out the scenario,create the thread if you face any issues.

  • IDOC to websevice (SOAP) scenario

    Hi Experts
    I have a IDOC to SOAP scenario, i have searched for the step to step guide in SDN, but could not find it
    Please let me know the step to step process for a IDOC to (webservice) SOAP scenario, like DT, MT etc.. and further steps
    Regards
    Lara

    Hi Vijay
    Thanks for the info shared.
    below are the points observed from the links
    My Scenario:
    Source : IDOC
    Target : SOAP
    mode : Asynchronous
    1. Import the IDOC which will be used in the message mapping at the source side
    2. Create SOAP Datatype, Message Type, Service Interface.
    3. Imoport the IDOC in message mapping and the SOAP message type that we have created in the above step
    4. Operations Mapping and activate the scenario (same as normal idoc to file scenario)
    5. Create Integration Scenario, SOAP Receiver Communication channel, Receiver Agreement, Receiver Determination, Interface Determination
    Please let me know if anything else am I missing in this scenario
    Regards
    Lara

Maybe you are looking for