Issue in 3.1i to SOAP scenario in PI

Hi,
I have a scenario where a BAPI is sending some information in the form of <TLine> to PI. PI is then sending this information to SOAP where all the sent <TLine>'s are concatenated and rendered as a PDF.
The issue which I am facing is:
When I see the output of the BAPI in 3.1i system it contains ## to depict a new line. When this payload reaches PI all ## are converted into a single space. Hence this is jeopardizing the whole PDF rendering.
Any help will be highly appreciated.
Warm Regards,
Anshul

Hi Experts,
Any pointers to this issue?
Warm Regards,
Anshul

Similar Messages

  • 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

  • HTTP 500 Internal Server Error with Large Attachment in SOAP Scenario

    Hi,
    we have implemented SOAP - XI - SOAP Scenario in our landscape (Sap Neatweaver Process Integration 7.1) .
    One of the functionality of this scenario is the Upload of Documents to External Web Service through standard SOAP Attachment.
    If we try to upload a small file (smaller than 20MB), task works fine and the document is correctly uploaded.
    If we try to upload a larger file, we encountered in this generic error:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
         at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1161)
    We tried to increase timeout parameters (in communication channel and in ICM Value) but the response is the same.
    We verify also if icm/HTTP/max_request_size_KB parameter was set to a value smaller than our file size limit (20MB) but is set to default value (100MB).
    The problem isn't on External Web Service Layer because if we try to upload the same documents directly to that web service upload works fine, and in External Web Service's Log there aren''t any indications of this error.
    So I ask you: are there any System Parameters to verify to solve this issue?
    For additional, in ICM Monitor LOG we can read this WARNING when we call our service:
    WARNING => IcmReadFromConn(id=53/454390): temporarily out of MPI buffers -> roll out [icxxthrio_mt 2646]
    This warning may be related to the problem? If yes, how can we solve it?
    Thanks a lot,
    Marcello Ricci

    Hi ,
      Please answer my following questiosn.
    1)  which PI version are you using?
    2) How many J2EE nodes you have.
    please be reminded that SOAP is not for the heavy messages. Then you need to increase your timeout parameters from BASIS.
    Rgds
    Veeru
    Edited by: viru srivastava on Dec 14, 2010 10:18 PM

  • Jco.webas.ignore_jdsr_error=1 in the sender side RFC adapter of RFC to SOAP scenario

    Hello Team,
    I am doing RFC to SOAP scenario after configuring the scenario i have checked the sender side communication channel it is not throughing any errors and it shows the status as green but it is displaying a short message
    it is the short log displayed while checking the sender side RFC communication channel it shows that "jco.webas.ignore_jdsr_error=1" can please any one suggest me how we can solve the issue.
    Regards,
    Avinash.

    Hi Avinash - I don't think that is an error instead it just displays your  system configuration.
    your RFC adapter should work i believe..
    Are you facing any issues?
    (I think the parameter is nothing but the value @ nwa/java system properties/XPI Adapter:RFC -> ignoreJrfcJdsrError(true/false))

  • 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 SOAP Scenario : Connection Refused

    Hi Everybody,
    I am working on Idoc to SOAP Asynchronous scenario.
    I have an issue with the connection from SOAP to the websystem at the receiver.
    Around 60% of the messages are processed successfully and the rest of the messages throws up errors at the receiver Adapter.
    Below is the log from Communication channel for the unsuccessful messages.
    Message processing started
    request entering
    SOAP: call failed: java.io.EOFException: Connection closed by remote host.
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Connection closed by remote host.: java.io.EOFException: Connection closed by remote host.
    Is there any setting we need to make for the SOAP adapter to reduce these failures?
    Or is it a problem with the receiver websystem?
    Can somebody help me out on this?
    Thanks & Regards,
    Zabiulla

    Hi,
    For some reason the client (from the server's point of view - it might be some other device between the actual client and the server) is closing connection during the SSL handshake. As we can't get more info from the standard J2EE Dispatcher log files, we need more detailed info.
    Please check
    1. Execute network router trace utility (tracert for Windows systems or traceroute for UNIX flavours) to the J2EE Engine's host. It will show the active and non stealth routers between the client and the server:
    c:\> tracert [J2EE_host]   (windows)
    $ traceroute [J2EE_host]   (UNIX)
    2. Activated low level SSL tracing
    regards
    Aashish Sinha

  • 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

  • Multiple clients for a RFC sender to SOAP scenario

    All,
    We have a RFC to SOAP scenario in our Development server and is working.
    The problem we are having is - we only have one XI server available. But there are different clients in Dev that want to use this scenario now. Though we create the new BS for each of these clients, the issue i see is in the RFC sender communication channel. it needs to have the program id.
    Right now we are creating a new program id for each of the clients(which translates to different RFC destination names on the ABAP side)... but that is causing a problem on the ABAP side - since the calling function is the same and they need some logic to change the RFC destination based on the client..
    Are we missing something or is there a simpler way to this?
    Thanks.

    we created the exact same way you told... just add another business system. complete the receiver determination, interface determination and sender agreement.
    It works every other time. When we checked the communcation channel monitoring - it will go to the client 210 once, and it would work. when we call the next time - it will error with a short dump in ABAP - but the error will appear on the communication channel for 250 (though we are calling from 210).
    Error in processing caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: alternativeServiceIdentifier: party/service from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier (CPA party/service/channel ''/'UD1CLNT250'/'RFC_UD1CLNT250', lookup of alternativeServiceIdentifier for party '', schema 'TechnicalSystem' with 'UD1#210' returned party/service of ''/'UD1CLNT210')
    Any thoughts?

  • Fault message in sender SOAP scenario

    Hi mates,
    I've a o/b synch MI which is exposed as a web service. I've specified the fault message with faultcode, faultstring, faultactor and detail. I've a BPM as the receiver for this synch infterface. This BPM implements synch-asynch bridge.
    Now the question is...How can I specify that a particular fault message needs to be returned to the SOAP caller. I can send the response for the SOAP caller using the send step with mode 'Closes S/A bridge'.
    I appreciate you inputs.
    thx in adv
    praveen

    Moorthy,
    I've the FM in my BPM. But...how can I append this to Response message as these have two different MTs?
    Do you mean to say my response message should have a node for fault message data?
    I'm trying to implement sth like in this blog <a href="/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client">Propagation of meaningful error information to SOAP Client</a>
    To achieve FM in SOAP scenario, should I be using <b>only</b> a non-BPM receiver like a R/3 system using FM with exception as the receiver? Can this be not possible if I use BPM as receiver?
    thx in adv
    praveen

  • Error handling in File - XI - SOAP scenario without BPM

    Hello!
    We have a File -> XI -> SOAP scenario without BPM. The problem is that if the Web Service sends back an error XI tries to reprocess the same message again and again instead of taking the next one.
    We do not want set the retry interval to NULL because most error cases are temporary connection problems and then also those messages would not automatically be reprocessed any more.
    We also have to use BE instead of EO, otherwise the Web Service will not return a response. But we need the response to be sure that the processing was successful. The message volume in this scenario is quite high and we do not want to use BPM only for the error handling.
    I know that from SP19 some additional adapter modules are available for async - sync scenarios without BPM. I tried to configure it like described in File - RFC - File without a BPM - Possible from SP 19. but it did not solve the problem. Does anybody have any other ideas? Thanks.
    Regards, Tanja

    Hi Tanja,
    >>>The volume is 3000 messages/day on business days and 700 messages/day during weekends but the traffic will increase in the future
    I think, you should check that out. It is assumedly only 2 days work to build a scenario:
    IDoc -> BP
    BP <-> SOAP/HTTP
    BP -> IDoc (Acknowledgement)
    In the process you need a condition branch, where you decide success or not. You need 2 Interface Mappings for filling the ALEAUD.
    Just send 1000 IDocs to the Test-XI and look to performance monitoring at Runtime Workbench, to find out, how many message will be processed in one hour. Assumedly 3000 and more per day should be possible. The advantage would be to reduce number of systems (no file system) and messages (better monitoring) and using the standard (better maintenance).
    >>>So you are suggesting I should use HTTP adapter and then add the SOAP header manually in a mapping?
    Yes, build the SOAP envelop during the mapping. Most easy is to use XSL or, if your mapping is ready, an additionsal XSL. You can put the error into the Acknowledgement to see it in ERP transaction WE02.
    Filling of ALEAUD fields:
    E1ADHDR/MESTYP: original message type
    E1ADHDR/E1STATE/DOCNUM: original IDoc number
    E1ADHDR/E1STATE/STATUS: 68 in case of error, 53 in case of success
    E1ADHDR/E1STATE/STATXT: Short description for R/3 user what has happend
    I ve done such a scenario several times. That works without any problems.
    Regards,
    Udo

  • File to SOAP Scenario Using BPM

    Hi,
    I am doing File to SOAP scenario using BPM.
    while doing Integration Process in IR, i got the following error message
    "Expression of simple type xsd:string expected"
    But i have given xsd:string in the correlation element as well as in Data types.
    I dont know why it is getting the error.
    could you anyone please help me to sort out?
    Regards,
    Sai Ch.

    Hey,
    Check in the correlation editor, where you define the condition.
    Whether the data type of the XPath is string and whether it matches with the data type of the messages that you have selected.also make sure the type of the correlation variable is string.
    regards,
       Milan

  • File name to be read in mapping - File to SOAP Scenario

    Hi all,
    its a  file to soap scenario. i need to send the file name also to target system. how can i get the file name in the mapping? is there a way to read the header information in mapping?
    Regards,
    Rashmi

    You need to check for Adapeter specific Message Attributes of your File adapter.Then write user defined function to set Dynamic_configuration. So that you can get the file name in the header(u can chk this in SXMB_MONI after implementing the UDF, it will create one section for dynamic_configuration.)
    Manisha

  • HTTP to SOAP scenario

    Hi guys,
    We have developed an HTTP to SOAP scenario, where XI acts as the WS client in order to call an already published WS.
    When we are testing the scenario through RWB's interface (Component Monitoring --> Integration Server --> Integration Engine --> Self-Test Tab), we get error in SXMB_MONI.
    The error is found in receiver SOAP adapter.
    In Communication Channel Monitoring, we get the error "request entering", "call failed". The Message Id does not have a link in order to see the Audit Log.
    In SXMB_MONI, the error in SOAP header is the following :
    <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: java.net.NoRouteToHostException: No route to host: connect</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
    Our network does not use a proxy server, the Web Service hostname responds when we ping it from CMD.
    Also, the WS works fine when testing it from Web.
    We tried to play around with "Target URL" and "SOAP Action" parameters in receiver SOAP Com. Channel, but error remains the same.
    Any ideas ??
    Evaggelos

    When I am testing the url : http://fmgralxi01:50000/XISOAPAdapter/MessageServlet?channel=:StockQuoteService:Sender_SOAP
    I get :
    Message Servlet is in Status OK
    Status information:
    Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#16 $) bound to /MessageServlet
    Classname ModuleProcessor: null
    Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
    Lookupname for remoteModuleProcessorLookupName: null
    ModuleProcessorClass not instantiated
    ModuleProcessorLocal is Instance of com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0
    ModuleProcessorRemote not instantiated
    As username: xiappluser

  • 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

  • SOAP Scenario-Sender and receiver having same structure- Mapping Required?

    Hi,
    We are having a SOAP to SOAP scenario. In that the sender and receiver are having same structure. Is it possible to by-pass mapping and just do the configuration from ID
    Thanks and regards,
    Siji Anup

    Hi Siji,
    AFAIK you can skip ESR development. Check the example in this blog When and how to create an scenario in SAP PI without mapping objects.
    Regards.

Maybe you are looking for