ERROR IN FTP TO RFC SCENARIO.

Hi,
I am new to xi.I am trying to post data in R/3 system.
I have one client configured as business system.I am loading xml file on ftp server.Sender channel is haveing file adapter . I have one reciever channel using RFC adapter.I am getting the following error :
<SAP:Category>XIServer</SAP:Category>
  <SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
  <SAP:P1>af.exi.bomw076a</SAP:P1>
  <SAP:P2 />
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText>3: No service user name found for Integration Server is.00.bomw076a</SAP:AdditionalText>
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.exi.bomw076a</SAP:Stack>
Kindly tell me steps I should take to resolve the issue.

Hi,
AS far as BPM is considered.I have already tried the following scenario with all the container elements in place for the BPM but in that case It said that there is a step missing in the BPM.
Scenario:
Here the input parameter for the RFC is sent through a file and the response from the RFC comes into XI which is then written into a file. The diagram of the following is shown below:
Fig1. File to RFC Synchronous Scenario
Design Steps:
·  Import the RFC (BAPI_COMPANY_GETDETAIL) which is available in SAP systems.
·  Create two Data Types FileRequest_DT and FileResponse_DT as shown below
Fig2.Input File Data Type
Fig3.Output File Data Type
·  Create Message Type FileRequest_MT and FileResponse_MT for both the data types as shown below
Fig4.Input File Message Type
Fig5.Output File Message Type
·  Create Message Interface for the message types as shown below
Fig6.Message Interface of Input File
Fig7.Abstract Interface of Input File
Fig8.Message Interface of Output File
Fig9.Abstract Interface of Output File
Fig10.Abstract Interface of RFC
·  Create Message Mappings Request_MM(File to RFC) and Response_MM(RFC to File )as shown below
Fig11.Request Message Mapping
Fig12.Response Message Mapping
·  Create the Interface Mapping File_RFC_IM as shown below
Fig13.Request Interface Mapping
Fig14.Response Interface Mapping
·  Create BPM File_RFC_BPM as shown below
Fig15.BPM
     In the following BPM the first block receives the file and hence triggers the BPM.The second block is a synchronous send block which triggers the call to RFC, takes the output and sends it further to the Asynchronous send step. The third step finally sends data to a file.
Configuration Steps:
·  Create an Integration Process File_RFC_BP for the BPM which we have created in Design.
·  Create three Communication Channel FileRFC_Send, RFC_Reciever and FileRFC_Recieve as shown below-
Fig15.File Sender Channel
Fig16.RFC Receiver Channel
Fig17.File Receiver Channel
·  Create a Sender Agreement for sending file
Fig24.Sender Agreement
·  Create three Receiver Determination as shown below
Fig18.Receiver Determination for File ->Integration Process
Fig19.Receiver Determination for Integration Process->R/3
Fig20.Receiver Determination for Integration Process ->File
·  Create three Interface Determination as shown below
Fig21.Interface Determination b/w File Service and Business Process
Fig22.Interface Determination b/w Business Process and R/3
Fig23.Interface Determination b/w Business Process and File Service
·  Create two Receiver Agreement one for the RFC and other for file as shown below
Fig25.Receiver Agreement for RFC
Fig26.Receiver Agreement for File
Input:
The xml content which we are sending in the Info.xml file
The Info.xml file placed in the Input folder will be picked and deleted since the processing mode is delete.
Output:
The xml content which will receive in the Detail.xml file as output.
The Detail.xml is created in the output folder.
Arpit Seth is a core team member of Satyam SAP Netweaver team.
Post all the Questions in XI forum.
Comment on this weblog
Showing messages 1 through 7 of 7.
Titles Only      Main Topics      Oldest First
·     Nice demo
2005-07-11 23:36:33 Karthik Sunil Business Card
·     Good Illustration
2005-06-27 07:13:28 Sridhar Rajan Natarajan Business Card
Hi Arpith,
Good blog...
I don't think backslash ("") is a part of URN character set.
Regards,
Sridhar
o     Good Illustration
2005-06-27 07:57:25 Sudhir Porumamilla Business Card
Sri we can even use "" while defining namespaces in SWCV
Cheers
Sudhir
§     Good Illustration
2005-06-27 12:26:43 Sridhar Rajan Natarajan Business Card
Hi Sudhir,
Are you sure that is the "right" way of naming a URN? Please let me know
It may be allowing you to do so because i think its automatically % encoded on using a excluded character ""
The general syntax for naming a URN is:
Regards,
Sridhar
§     Good Illustration
2005-06-27 21:01:14 Sudhir Porumamilla Business Card
>>Right way
Well sri...:-) ...if u r talkin abt right way...then even i won't prefer "".
But i thot u were askin whether namespaces are allowed using this character"" in a technical error sense
Cheers
·     Nice blog dude !!
2005-06-27 06:58:36 Sudhir Porumamilla Business Card
Cheers
o     Nice blog dude !!
2005-06-29 05:11:53 siva maranani Business Card
Real cakewalk for newbies...
Cheers,
Siva Maranani

Similar Messages

  • Error in 'WEBSERVICE TO RFC' SCENARIO

    Hi experts,
      i am facing a problem in 'WEB SERVICE-RFC' scenario,here we are using soap sender communication cheannel & rfc receiver communication channel.while processing the message from 'portal'(through web service in 'SXI_MONI' we are gettin 1 request & 2 response(error) message.
    (in sxi_moni)
    1st error message:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="RFC_ADAPTER">APPLICATION_ERROR</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="urn:sap-com:document:sap:rfc:functions">ZBAPI_QUOTATION.Exception</SAP:ApplicationFaultMessage>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    [note: here we are using 'ZBAPI_QUOTATION' IN sap r/3)
    2nd response:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <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>Object ID 08490A2EBE1A301E9D13373FF379B9BE Software Component 9776FD71CBAE11DF8942F5910A010C19</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Interface mapping Object ID 08490A2EBE1A301E9D13373FF379B9BE Software Component 9776FD71CBAE11DF8942F5910A010C19 does not exist in runtime cache</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    please help me to solve this issue.

    For the mapping error >>>  Please check whether  you have created a response mapping and properly  referenced it in your operation mapping
    For the RFC exception error >> Please check if you have any new fields added in RFC , re Import the RFC definition in PI
    refresh the cache SXI_Cache
    Please check below similar threads
    file rfc file
    RFC_ADAPTER "APPLICATION_ERROR"
    Re: Webservice to RFC  testing
    Hope this helps
    Regards
    Ninad

  • FTP TO RFC scenario

    In this scenario i am sending companyid from ftp and want to receive company details in response,
    I have designed the scenario the output file is generated in response but the data is not getting retrived so can anyone help me out in this scenario

    BTW
    have you seen this weblog:
    /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
    it shows exactly your scenario,
    unless you're calling the RFC in an async call:
    file - RFC
    then
    RFC -file
    then you don't need BPM
    Regards,
    michal

  • Error in File to RFC scenario: ATTRIBUTE_WRONG_INTF

    Hello,
    My scenario is going from File to RFC which is simply writing to an SAP table.
    My mapping seems OK and tests OK but in SXMB_MONI I get red flag and error below:
    <?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_WRONG_INTF</SAP:Code>
      <SAP:P1>ZDWM_POS_UPDATE</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to interpret IDoc interface ZDWM_POS_UPDATE</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    The posts I see in the forums with this text have to do with an external deffinition being incorrect. I don't have an ED, it is mapping right to our custom RFC interface ZDWM_POS_UPDATE.
    Does anyone have any ideas or pointers for troubleshooting this?
    Many thanks,
    Aaron

    Hi Aron,
    You should not create any message interfaces refering to RFC.Infact RFC acts both like Message type and Messge interface.
    In interface determination choose ALL radio button and choose Idoc itself instead of interface.
    Also the interface mapping should be b/w Fileinterface<-->RFC directly (no need of interface)
    Hope this helps.
    Regards,
    Divya

  • ERROR  IN  FILE--XI--RFC SCENARIO.  BAPI  did not UPDATE the DATABASE TABLE

    Hi
    I have created a scenario  FILE -XI- RFC
    File is picked by file adapter  - Its working fine
    I have used BPM
    In RFC side  i used BAPI_INCOMINGINVOICE_CREATE
    Its working fine and return an Invoice Number and Fisical year .
    When i Check this in the R/3 System , in Invoice no Does not Exist .
    Message mapping is ok
    SXMB_MONI all are ok
    Receiver file i got the invoice no and fisical year .
    The Problem is " DATABASE TABLE DID NOT UPDATED "
    So  should i do BAPI_COMMIT seperately ........
    Any solution ................
    VERY VERY URGENT .....
    thanks in advance
    B.Jude

    hi jude,
    Commit Control for Single BAPI Calls
    If you want to use this communication channel to call BAPIs as remote-enabled function modules that change data in the database, set the indicator.
    If executed successfully, the transaction is written to the database by calling the function module BAPI_TRANSACTION_COMMIT explicitly. If an error occurs, the transaction is rolled back by BAPI_TRANSACTION_ROLLBACK.
    The result is determined by the value of the field TYPE in parameter RETURN. If successful, the tables are empty and the values “”, “S”, “I”, and “W” are displayed. All other values are regarded as errors.
    To change this setting, set the indicator BAPI Advanced Mode.
    <b>In the Successful RETURN-TYPE Values table, enter the values that should lead to a successful execution.</b>
    Regards,
    Mandeep Virk

  • Error in file to rfc scenario

    Hi
    I am trying to execute a synchronous scenario of file to RFC. Actualy it worked in XI 7.0. I am trying to do the same thing in PI 7.1
    I have done all the configurations, yet it shows the error.
    Worst part is, it is not shown in sxmb_moni. The status is not displayed.
    Where could the problem be? Did i miss somewhere either in installing or configuring?
    Kindly let me know.
    Regards,
    Kevin

    Hi
    Hey but u said its a file to RFC???
    in the module name  write : localejbs/AF_Modules/MessageTransformBean
    (see that it is the first module in the chain )select type as localejbs,
    in the module key just add a simple name (it is the variable which depends on u e.g var)
    This variable will be used ahead (see below in cc in module configuration part in ur channel )
    now in the column module key below choose the key "var" from drop down
    In Parameter Name add Transform.Class and the value as com.sap.aii.messaging.adapter.Conversion
    second row  add parameter  Transform.ContentType
    and value text/xml;charset=utf-8
    for the same module key
    Edited by: Progirl Progirl on Jul 18, 2008 12:53 PM

  • Error Handelling File-XI-RFC Scenario.

    Hi Experts,
    I am making a scenario File to XI to RFC,
    File - XI - R/3 System
    If the record is already available at R/3 System, how I can check that the same is available at R/3 and how I can stop saving the same?
    I will write a code in our RFC Function Module at R/3 or XI will handle the same ?
    & how ?
    Where I will create the Error ?
    Regards,
    Study Sap

    If it will stop at R/3 side, at XI in sxmb_moni it will show a successful message or error message ?
    If the message clears the XI pipeline , you wont seen an error in sxmb_moni but that doesnt mean your IDOC was received at the r/3 side
    as suggested by prateek, you can check sxmb_moni at the r/3 side to know the status
    regards
    krishna

  • Error in soap to rfc scenario

    while checking the result  in altovaxmlspy i m getting the following error "(122) JCO_ERROR_CONVERSION: Date '12/20/2002' has a wrong format at field FLIGHTDATE: Unparseable date: "12/20/2002"" . The BAPI being used is SXIDEMO_AIRL_FLIGHT_CHECKAVAIL.
    The date format  visible in fldate field of SFLIGHT table is MM/DD/YYYY  and while mapping in IR  the source date format is dd/mm/yyyy and target format taken is mm/dd/yyyy.
    pl help how to rectify the error in order to see the proper result

    Hi Prateek
    Date conversion while mapping has been done using std function " Date Trans" only.
    " But the target date u mentioned is mm/dd/yyyy. Make sure that the RFC accepts the date in this format."
    The crux of the matter is that i m unable to make sure the above quoted  point . Pl help how to ensure whether the RFC accepts the date in this format .
    Rgds
    Edited by: shazia seemin on Jan 22, 2008 7:44 AM

  • Error while calling RFC adapter(FILE-XI-RFC scenario)

    Hi,
    I am trying for FILE-XI-RFC scenario. I am getting the following error. I have checked in message monitoring. The error is coming while calling the RFC adapter. Can any body tell what problem is this?
    Regards,
    Dhana
      <?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>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
      <SAP:P1>af.f23.sofd00001530a</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>2: Unable to find URL for Adapter Engine af.u7a.us4296</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.f23.sofd00001530a</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

    Hi,
    I did SLD check.
    The status says 'Summary: Connection to SLD works correctly'.
    But it fails while checking the access to XI profile.
    Here is the status
    Summary: Connection to SLD works correctly
    Now checking access to the XI Profile
    Properties of RFC destination LCRSAPRFC
      RFC host:
    %%RFCSERVER%%
      program id:      LCRSAPRFC_DZ1
      gateway host:
      gateway service:
    Testing the RFC connection to the SLD java client...
    RFC ping returned exception with message:
    / CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679#Transaction program not registere

  • XI to RFC Scenario: Runtime error during RFC Call

    Hi,
    I am testing a XI-to-RFC scenario involving BPM. The RFC works perfectly from SE37; but I get 'ICM_HTTP_TIMEOUT, Error code 402' when I invoke it from XI. On digging through the problem, it appeared that the calling program produced a short dump at the ABAP end. The code is as follows:
    <b>module %_rfcdia_start output.
        "Do not display screen !
        call 'DY_INVISIBLE_SCREEN'.
        perform remote_function_diastart.
    endmodule.
    module %_rfcdia_call output.
        "Do not display screen !
        call 'DY_INVISIBLE_SCREEN'.
        perform remote_function_diacall.
    endmodule.
    module %_cpic_start.
      if sy-xprog(4) = '%RFC'.
        perform remote_function_call using rfctype_external_cpic.
      else.
        call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
        perform cpic_call using convid.
      endif.
    endmodule.
    form cpic_call using convid type c.
      communication send id convid buffer header.
      if sy-subrc eq 0.
        perform (sy-xform) in program (sy-xprog).
      else.
        message a800.
      endif.
    endform.
    form remote_function_call using value(type).
      data rc type i value 0.
      do.
    ********This is the line where error occurs************
        <i>call 'RfcImport' id 'Type' field type.</i>
        if sy-xprog = 'JAVA'.
          system-call plugin
                      id 'JAVA' value 'FORW_JAVA'
                      id 'RC'   value rc.
      if there is no rollout on the JAVA side which
      rolls both, JAVA and ABAP, we return to the
      C-Stack and reach this point
      in case there was an rollout, the ABAP-C stack is lost
      and we jump direkt to this point
      here we trigger the rollout on this Abap side with
      the following statement
          system-call plugin
                      id 'JAVA' value 'ROLL_OUT'
                      id 'RC'   value rc.
        else.
          perform (sy-xform) in program (sy-xprog).
          rsyn >scont sysc 00011111 0.
        endif.</b>
    Anybody has any idea why it is happening? Is it a network issue? The dump in ST22 says that 'The program "SAPMSYS1" was terminated manually'. How it is possible to manually abort an automatic call?
    Awaiting reply.
    Regards.

    Hi,
    Probably because of timeout, it is unable to execute the request ..so it is aborted.
    btw, is it a synchronous call ? what is the message size ? the given data to RFC is correct and valid structure ? check the mapping .for this use the data from SXMB_MONI and test it
    Check this blog for timeout errors-
    /people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
    Regards,
    moorthy

  • Mapping error in file(FCC) to rfc scenario

    Hi,
    i am trying to implement mapping in file (fcc) to rfc scenario. the source file is getting picked up, but the problem is arising during mapping. i am unable to generate the target structure. i am attaching mapping structure as follows
    Source Structure                           Target Structure: RFC
    storesales                                     -POSDW-CREATE_TRANSACTIONS_EXT
         recordset                                      it_transaction
           gmd_site_101                                 item
          gmd_site_102
          gmd_site_103
          gmd_site_104
    here the recorset is mapped to item, and fields of subnode gmd_site_101 is mapped to fields of subnode item. similarly, for the other subnodes. but when testing with xml file, the target field is not getting generated. in FCC parameters, ignorerecordset name is set to "true".
    any help would be very helpful..thanks in advance.
    warm regards,
    kartz

    hi
    You can test the data using payload from SXMB_MONI in message mapping test tool so as you can get to know the reason of failure.
    It would be better if you paste the error you are getting over there.
    Check if you have maintained the namespace in CC or not. it should be same maintained if you have kept namespace in message type.
    Also check in FCC parameters you must have used ignoreRecordsetName = true
    Regards
    Raj

  • Soap to rfc scenario error

    Hi PI Experts,
          For the first time i was doing soap to rfc scenario. I have created all the objects in the ID and in the IR and also created a web service from ID an then i have saved the wsdl in my system. I have uploaded the wsdl in altova xml spy and tested it but i got an error like 'no channel specified'. and also got an error 'unable to post the file'.
    so kindly please help me to solve this scenario.
    Thanks & Regards,
    B.Srinivas Prasad.

    I have uploaded the wsdl in altova xml spy and tested it but i got an error like 'no channel specified'. and also got an error 'unable to post the file'.
    Make sure that its in the below format :
    From SAP help :
    http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
    Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel
    and check Sender Soap Channel Status is it activated/not and check Cache Status

  • SOAP to RFC Scenario - Error at Sender Communication channel !!

    Hi Experts ,
    I am trying to execute a SOAP to RFC scenario . At SOAP sender channel level I am getting the error in RWB .
    My findings :-
    1. Error at RWB  9/24/09 4:24:10 PM   error occured
                             9/24/09 4:24:06 PM   request received
    2. At SOAP UI client tool :
       <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP:Body>
          <SOAP:Fault>
             <faultcode>SOAP:Server</faultcode>
             <faultstring>Server Error</faultstring>
             <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                   <context>XIAdapter</context>
                   <code>ADAPTER.JAVA_EXCEPTION</code>
                   <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:UPDATE:HTTP status code401 Unauthorized
         at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
         at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
         at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:917)
         at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:207)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</text>
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    3.  At SOAP UI level - "requires authentication with the realm 'XISOAPApps'"
    1. I don't see any issue in authorization as i am having SAP_ALL .
    2. URL string seems to be O.K :
        http://ABC:50000//XISOAPAdapter/MessageServlet?channel=:BSer_SOAP:CC_SOAP_Sender&version=3.0&Sender.Service=BSer_SOAP&Interface=urn:ABC.com:%5EMI_CustomerInfo
    Kindly advice !!!
    Regards ,

    1. Check PI id and password is working fine.
    Check if the user you are using has SAP_XI_APPL_SERV_USER role.
    Another way is to pass id and pwd in URL
    Try to pass the User ID and Password in the URL( the URL which is given to the webservice).
    Example: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel &sap-user=xxxx&sap-password=xxxx
    2.Provide SOAP URL like -
    http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel

  • NO_RECEIVER_CASE_BE error in a SOAP - XI - RFC scenario

    Hi gurus:
    I'm configuring a SOAP -> XI -> RFC scenario and I'm getting a "NO_RECEIVER_CASE_BE" error when I send a test message using the SOAP adapter.
    I have another interfaces using the SOAP adapter of the same XI server and no problems with it. So I think my problem is not into the SOAP adapter.
    Thanks to all in advance,
    Alejandro Gomez.
    Edited by: Alejandro Gómez on May 27, 2008 10:24 AM

    Hi:
    The entire XML result from MONI is next:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Inbound Message --> <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30"><SOAP:Header><SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7"><SAP:MessageClass>ApplicationMessage</SAP:MessageClass><SAP:ProcessingMode>synchronous</SAP:ProcessingMode><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:TimeSent>2008-05-27T09:10:24Z</SAP:TimeSent><SAP:Sender><SAP:Service>Openlab_Desarrollo</SAP:Service><SAP:Interface namespace="http://www.huc.es/xmlns/openlab">ServicioObtencionDatosPaciente</SAP:Interface></SAP:Sender><SAP:Interface namespace="http://www.huc.es/xmlns/openlab">ServicioObtencionDatosPaciente</SAP:Interface></SAP:Main><SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:QualityOfService>BestEffort</SAP:QualityOfService></SAP:ReliableMessaging><SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Hop timeStamp="2008-05-27T09:10:24Z" wasRead="false"><SAP:Engine type="AE">af.xi2.xidserver</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:Info/></SAP:Hop><SAP:Hop timeStamp="2008-05-27T09:10:24Z" wasRead="false"><SAP:Engine type="IS">is.00.xidserver</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:Info>3.0</SAP:Info></SAP:Hop></SAP:HopList><SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SAP:Date>20080527</SAP:Date><SAP:Time>101024</SAP:Time><SAP:Host>xidserver</SAP:Host><SAP:SystemId>XI2</SAP:SystemId><SAP:SystemNr>00</SAP:SystemNr><SAP:OS>Windows NT</SAP:OS><SAP:DB>ORACLE</SAP:DB><SAP:Language/><SAP:ProcStatus>023</SAP:ProcStatus><SAP:AdapterStatus>000</SAP:AdapterStatus><SAP:User>XIAFUSER</SAP:User><SAP:TraceLevel>3</SAP:TraceLevel><SAP:Logging>1</SAP:Logging><SAP:LogSeqNbr>001</SAP:LogSeqNbr><SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr><SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal><SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal><SAP:PipelineElementId>5BC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId><SAP:PipelineService>PLSRV_RECEIVER_DETERMINATION</SAP:PipelineService><SAP:QIdInternal/><SAP:CommitActor>X</SAP:CommitActor><SAP:SplitNumber>0</SAP:SplitNumber><SAP:NumberOfRetries>0</SAP:NumberOfRetries><SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries><SAP:TypeOfEngine client="100">CENTRAL</SAP:TypeOfEngine><SAP:PlsrvExceptionCode/><SAP:EOReferenceRuntime type="TID"/><SAP:EOReferenceInbound type="TID"/><SAP:EOReferenceOutbound type="TID"/><SAP:MessageSizePayload>508</SAP:MessageSizePayload><SAP:MessageSizeTotal>2985</SAP:MessageSizeTotal><SAP:PayloadSizeRequest>508</SAP:PayloadSizeRequest><SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap><SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse><SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap><SAP:Reorganization>INI</SAP:Reorganization><SAP:AdapterInbound>AENGINE</SAP:AdapterInbound><SAP:InterfaceAction>INIT</SAP:InterfaceAction><SAP:RandomNumber>00</SAP:RandomNumber><SAP:AckStatus>000</SAP:AckStatus><SAP:SkipReceiverDetermination/></SAP:RunTime><SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30"><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="end" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="end" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.616</SAP:Timestamp></SAP:RunTimeItem></SAP:PerformanceHeader><SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:TraceLevel>Fatal</SAP:TraceLevel><SAP:Logging>Off</SAP:Logging></SAP:Diagnostic><SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">Party normalization: sender </Trace>
    <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
    <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
    <Trace level="1" type="T">Sender party external = </Trace>
    <Trace level="1" type="T">Sender party normalized = </Trace>
    <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
    <Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
    <Trace level="2" type="T">Host = xidserver:8000</Trace>
    <Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
    <Trace level="2" type="T">Remote address = 10.137.73.104</Trace>
    <Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
    <Trace level="3" type="T">Getting type of XMB... </Trace>
    <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
    </Trace>
    <Trace level="2" type="T">XMB kind = CENTRAL</Trace>
    <Trace level="3" type="T">Start pipeline found </Trace>
    <Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
    <Trace level="3" type="T">No triggers found. OK. </Trace>
    </Trace>
    <Trace level="1" type="T">**************************************************** </Trace>
    <Trace level="1" type="T">*                                                  * </Trace>
    <Trace level="1" type="T">*                                                  * </Trace>
    <Trace level="1" type="T">XMB entry processing </Trace>
    <Trace level="3" type="T">system-ID = XI2</Trace>
    <Trace level="3" type="T">client = 100</Trace>
    <Trace level="3" type="T">language = S</Trace>
    <Trace level="3" type="T">user = XIAFUSER</Trace>
    <Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET  </Trace>
    <Trace level="1" type="T">*                                                  * </Trace>
    <Trace level="1" type="T">*                                                  * </Trace>
    <Trace level="1" type="T">**************************************************** </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">Message-GUID = BD9B57A12BCC11DDC738001B7899027A</Trace>
    <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
    <Trace level="1" type="T">QOS = BE</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
    <Trace level="3" type="T">External PLID = CENTRAL</Trace>
    <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline attributes </Trace>
    <Trace level="3" type="T">PID        = SAP_CENTRAL</Trace>
    <Trace level="3" type="T">ENABLE     = 1</Trace>
    <Trace level="3" type="T">TRACELEVEL = 0</Trace>
    <Trace level="3" type="T">EXEMODE    = A</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline elements </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0001</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0002</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_INTERFACE_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0003</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0004</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_REQUEST</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0007</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_OUTBOUND_BINDING</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0008</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = =SWITCH=</Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0009</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_RESPONSE</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="2" type="T">Persisting original message </Trace>
    <Trace level="3" type="T">Message-Version = 000</Trace>
    <Trace level="3" type="T">Message version 000</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION"></Trace><!-- ************************************ -->
    <Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">ADRESSMOD  = LOCAL</Trace>
    <Trace level="3" type="T">P_CLASS    = CL_RD_PLSRV</Trace>
    <Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG     = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
    <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace>
    <Trace level="1" type="T"> Cache Content is up to date </Trace>
    <Trace level="2" type="T">Start without given receiver </Trace>
    <Trace level="1" type="T">No Relation found - accept given Receivers. </Trace>
    <Trace level="2" type="T">Classic Receiver Determination via Rules. </Trace>
    <Trace level="2" type="T">No Receiver found behaviour: 0  </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">Persisting message Status = 023</Trace>
    <Trace level="3" type="T">Message version 001</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </SAP:Trace></SOAP:Header><SOAP:Body><SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7"><SAP:Payload xlink:href="cid:payload-bd9b57a22bcc11dd95bc001b7899027a#sap.com"><SAP:Name>MainDocument</SAP:Name><SAP:Description>Main XML document</SAP:Description><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest></SOAP:Body></SOAP:Envelope>
    Thanks,
    Alejandro Gomez.

  • RFC to RFC scenario fails with error

    Hello Guys,
    In our XI support we found errors for RFC to RFC scenario.
    Some messages failed with the below error :
    SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
      <SAP:P1>503</SAP:P1>
      <SAP:P2>Service Unavailable</SAP:P2>
      <SAP:P3 />
    Latter the new RFC messages were having this error :
      <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: Object not found in lookup of RfcAFBean.</SAP:AdditionalText>
    Now all the messages are getting processed.
    Can you please tell me the cause this happens every now and then.
    What is the solution.

    Hi Rajeev,
    See these threads:
    Re: HTTP_RESP_STATUS_CODE_NOT_OK - Error in ABAP proxy
    Re: 503 Error -  HTTP_RESP_STATUS_CODE_NOT_OK
    XIServer error raised: 503 Service Unavailable with SOAP Adapter
    http://www.saptechies.com/http-errors-in-xi/
    HTTP_RESP_STATUS_CODE_NOT_OK 503
    I hope these will solve your problem. Rewards with points if helpful.
    BR,
    Alok

Maybe you are looking for

  • Safari 7.0.4 will not allow Acrobat to open PDF files, Works ok with Chrome?

    I cannot open PDF files with Acrobat using Safari 7.0.4 No problem if I use Chrome Help

  • How can i access RFC Function module in BI

    Dear Experts, I have a RFC fm in BI system which will allow me to write data into BI DSO, but when i am trying to select that from BI system their is no option to select a service, but when we go to ECC or CRM we can find option Service through with

  • Problems with blending modes

    Hi, I have a layer with a solid color (212º,93,78) on top of which I have another layer with a solid color (205º,100,74).  Call this second layer the blend layer. I then choose for it a blending mode of Color, and the resulting color in the top layer

  • Confused with PSU...

    Hi: Just to say hello since I am new to this forum. 6 months ago, I decided to buy the following system: K7N2 Delta2 Platinum Corsair TwinX PC3200 C2 (cas 2-3-3-6), 2x512 Nvidia Gforce FX 5200 (Non Ultra, just the 128MB one). Athlon XP 3000+ (Barton

  • Why won't my creative cloud set-up run correctly?

    I downloaded the set-up app and it will not run/open anything when I try to run it.