Mail-Adapter Integration Engine Error during parsing of SOAP header

Hello,
we use XI with the mail adapter. Most of the messages are processed correctly. But sometimes I get following errors in the J2EE-logviewer:
Transmitting the message to endpoint http://<xi-host>:<http-port>/sap/xi/engine
?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.a
pi.RecoverableException: Received HTTP response code 500 : Error during
parsing of SOAP header.
Failed to transmit message 4e913640-4cc5-11dc-8560-00e000c55366(OUTBOUND)
due to com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP
response code 500 : Error during parsing of SOAP header.
Retries exceded, set message
4e913640-4cc5-11dc-8560-00e000c55366(OUTBOUND) to status NON_DELIVERED.
Has somebody else the same problem and solved it or any idea what the matter could be?
Thanks for your help
Christian

Hi Reddy,
We´ve got the following scenario:
Exchange-Server (is always up)
XI Mail-ReceiverAdapter
I use IMAP4 to access the Outlook-Email-Box
Everything works fine. But some Emails aren´t processed.
I think it´s a problem between adapterframework and the integration engine?
There is no difference between the emails?
If you´ll need further informations ask me?
Thanks

Similar Messages

  • HTTP response code 500 : Error during parsing of SOAP header

    Hi Experts,
    I have a MAIL to IDOC scenario.  An external third party emails invoices to our inbox - which we pick up and process the attachment.  All is well when I test the scenario internally, but when the third party emails it fails with (see ERROR MESSAGE below).
    When I look at the SOAP header of the failed message I see the values from the dump in this field:
      <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderTHREAD-INDEX">AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=</sap:Record>
    Can anyone tell me what SHeaderTHREAD-INDEX does?  Or what my problem is  (Our email is Outlook)
    ERROR MESSAGE.........
    SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/WRONG_VALUE; Params: SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14), AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=協彎䅍䔾ਉ़䥎噏䥃䕟乏㸸㌱ㄵㄹ㰯䥎噏䥃䕟乏㸊उ㱁䵏啎呟䕘䍌彖䅔㸷⸵〼⽁䵏啎呟䕘䍌彖䅔㸊उ㱃啒剅乃失㹅啒㰯䍕剒䕎䍙ㄾਉ़䅍何乔彖䅔㸱⸴㜼⽁ꯃ䅢坡汫, ST: ST_XM; AdditionalText: An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC; ApplicationFaultMessage:  ; ErrorStack: XML tag SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14) (or one of the attributes) has the incorrect value AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQ An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC Data loss occurred when converting AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1p
    Transmitting the message to endpoint http://sdcxp1-ci.na.fmo.com:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header.

    We work with Microsoft Outlook, but I'm sure this could work with any email system.
    This error only came from external emails - what we did in the end is to get the third party to email a particular email (email1) in our company.  This is set up as a regular email account.  On this email put a forward rule to email2 for a particular sender/subject.  email2 is set up as POP3 so that XD1 can poll it - we also block any emails except from email1.
    Doing this accomplishes a couple of things:
    1)  We get around the error because XI polls email2 (which has adapter settings of IMAP4 so we can see MAIL adapter attributes ie. sender, subject etc...When we originally had as POP3 we were not able to see these - but setting as IMAP4 causes the error for external emailers)
    2) We have a SPAM filter - the XI email is clean from SPAM and the adapter will not have errors, as it only receives valid emails to process
    3) We have a central email (email1) which is used to archive all XI emails - we use this for all email scenarios (as we also save to folder and forward in the rule)
    Hope this helps your situation.

  • Error during parsing of SOAP header

    Hi all,
    I have configured the j-meter to send an http request to inegration engine of PI.
    The request xml that I am sending is as follows:
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP:Header>
    <SOAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30"
    versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1">
    </SOAP:Main>
    </SOAP:Header>
    <SOAP:Body>
    <ns1:UnitOfMeasure xmlns:ns1="urn:sapappl:mdm:cp:eame:masterdata:uom:620">
    <Record>
    <FinishedMaterialCode>000000000000000233</FinishedMaterialCode>
    <BaseUOM>KG</BaseUOM>
    <AlternateUOM>GEB</AlternateUOM>
    <UnitsInAlternateUOM>100</UnitsInAlternateUOM>
    <UnitsInBaseUOM>2268</UnitsInBaseUOM>
    <Active_Deleted></Active_Deleted>
    </Record>
    </ns1:UnitOfMeasure>
    </SOAP:Body>
    </SOAP:Envelope>
    I am getting the following response from the XI:
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP:Header>
    </SOAP:Header>
    <SOAP:Body>
    <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during parsing of SOAP header</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="PARSER"/><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>System error in parser
    </SAP:Stack></SAP:Error></detail></SOAP:Fault>
    </SOAP:Body>
    </SOAP:Envelope>
    Any idea as to why PI is not able to parse the request header?
    Thanks,
    Amit

    Hi,
    Better to take WSDL from PI(ID window) and try.

  • XI SOAP adapter : Error during parsing the SOAP part

    Hello experts,
    We have several scenarios SOAP to IDocs.
    We are on XI 3.0 SP19, and since 9/6/09 around 4:00 PM GMT, our SOAP channels used to communicate with a specific 3rd party all stoped accepting incoming SOAP requests. All the messages are stucked on third party side, and we get the following error in the defaulttrace and application logs :
    #1.5#001125A5BCD00066000076850013109E00046BF6A963E479#1244607054865#/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.messaging.mo.Message.reparseRootDocument()#PIMSOAP#21217##pxaci_PXA_6443451#PIMSOAP#a71ebfa0556d11decc24001125a5bcd0#SAPEngine_Application_Thread[impl:3]_50##0#0#Error#1#com.sap.aii.messaging.mo.Message#Plain###Error during parsing the SOAP part --- java.lang.NullPointerException#
    It happened at the same time on all the environments for every interfaces using SOAP message from this sender to XI. That's the reason why we think it is a global issue, but we can not find anything concerning this error. Has anybody encountered this error or would have any clue of where it comes from ?
    Many thanks,
    Best regards,
    Guislain

    Hello Michal,
    Thanks a lot for your help. Actualy we have tested with SOAP UI yesterday and this is what came out of the tests :
    test 1 : we tried to call the XI service with the wsdl and put dummy data inside --> test OK
    test 2 : we loaded in SOAP UI one of the file from our partner and tried to call the service --> test NOT OK
    test 3 : we realized that there were some blank lines at the beginning of the file provided by the partner. we removed these blank lines --> test OK.
    So we first thought that the format of the file sent by the partner was wrong and this is why we were getting the parsing error, because of these blank line. The thing is that these blank lines have always been here ! We have checked with old successful messages and they contain also these lines and if we test them in SOAP UI we get an error also. so it does not seems to come from this.
    Moreover, as I said in my previous message, it happened on all the environments approximatly at the same time, so we are suspecting a global problem, but which one ? That's the million dollar question
    Would you have any other ideas ?
    Thanks a lot,
    Best regards,
    Guislain

  • XOQ-01703: error during parse of build process script: (clear, compile)", "

    Hi All ,
    I was just clearing the dimensions using the below in SQL commandline throwing below error . However this works fine with my another 5 dimensions .Any advice ?
    SQL> exec dbms_cube.build('POSITION using (clear, compile)');
    BEGIN dbms_cube.build('POSITION using (clear, compile)'); END;
    ERROR at line 1:
    ORA-37162: OLAP error
    XOQ-01703: error during parse of build process script: "BUILD POSITION using
    (clear, compile)", ""
    ORA-06512: at "SYS.DBMS_CUBE", line 236
    ORA-06512: at "SYS.DBMS_CUBE", line 280
    ORA-06512: at line 1
    Thanks,
    DxP

    I believe in this case the parser that is parsing the build process script is treating the dimension name "POSITION" as a keyword and not as an OLAP Cube Dimension name. You may wish to rename the dimension to a name other than "POSITION" or double quotes as specified previously.
    Edited by: user713408 on Aug 1, 2011 12:12 PM

  • [SOLVED] Error during update of LUKS header on device ./file

    dd if=/dev/zero of=./file bs=1M count=200
    cryptsetup luksFormat -s 512 -c aes-xts-plain64 -h sha512 ./file
    WARNING!
    ========
    This will overwrite data on ./file irrevocably.
    Are you sure? (Type uppercase yes): YES
    Enter LUKS passphrase:
    Verify passphrase:
    Error during update of LUKS header on device ./file.
    This only happens on my 1TB HDD (GPT, xfs filesystem).  I have 2 SSDs that do not throw the error. 
    I tested using a flash drive formatted as GPT and using xfs filesystem and it worked.
    Ideas?
    Last edited by not_sure (2013-03-01 02:50:32)

    Hmm... I didn't know you could do that. Are you sure it can? https://wiki.archlinux.org/index.php/Di … ison_table
    I thought dm-crypt basically did block level encryption.
    I guess this is a "virtual partition"? Maybe https://www.linux.com/community/blogs/1 … nux/280174 helps? It seems to mount it as loopback prior to encryption?
    Last edited by cfr (2013-03-01 01:07:16)

  • Sender mail Adapter - Log in Error

    Hi,
    I am facing the below error while communicating with the mail server using the POP3 transport protocol.
    exception caught during processing mail message; java.io.IOException: unexpected password response; read -ERR Logon failure: unknown user name or bad password.
    Confimed with  the mail server administrator there is no issue with log in credentials.
    We are able to access the mail box using the same user ID & password through webservice URL. But if we use the same User ID & password in communication channel it is showing the above error.
    Any one have the idea about other possibilities to get this error?
    Thanks & regards,
    Krishna

    Hi Vijay,
    It is POP3 protocol setup. We are able to login using webservise URL. But not able to log in with Mail adapter.
    Regards,
    Krishna

  • Adapter_plain and engine error during test service

    Hi All,
    Am not able to test the adapter_plain service under default_host->sap->xi. When i do a Test Service i get an Action Cancelled page with the url http://iscsapapp4w:8010/sap/xi/adapter_plain?sap-client=100
    I checked the Pipeline URL parameters in SLD for my Integration Server BS, httpport setting in eXhangeProfile and specific confirmations IS_URL parameter in sxmb_adm.
    And i get the following error when i Test default_host->sap->xi->engine
    Pipeline ID which is expected as value of attribute &quot;type&quot; in the URL, does not exist in the Integration Engine (URL = /sap/xi/engine?sap-client=100)

    Synchronous RFC
    1. CALL FUNCTION func DESTINATION dest
                         parameter_list.
    Asynchronous RFC
    2. CALL FUNCTION func STARTING NEW TASK task
                    [DESTINATION {dest|{IN GROUP {group|DEFAULT}}}]
                    parameter_list
                    [{PERFORMING subr}|{CALLING meth} ON END OF TASK].
    Transactional RFC
    3. CALL FUNCTION func IN BACKGROUND TASK
                         [DESTINATION dest]
                         parameter_list
                         [AS SEPARATE UNIT].
    Use help function of your ABAP editor for more details.
    Regards
    Stefan

  • Customize email alert messages for Integration Engine Errors

    Hi experts,
    I've configured auto-reaction emails for alerts raised by Integration Engine in CCMS.
    The email content I got is as below:
    Subject: CCMS alerts PI1 20070319 140556
    <i>ALERT for PI1 \ IEngine_PI1_001 Integration Server \ Category MAPPING \ Message alerts by Error Codes at 20070319 060447 ( Time in UTC )
    RED CCMS alert for monitored object Message alerts by Error Codes
    Alert Text:Error code: GENERIC error text: com/sap/xi/tf/_MM_OperationPro cInfo_ODSOperationP~com.sap.ai i.utilxi.misc.api.BaseRuntimeExceptionFatal Error:
    System:PI1
    Segment:SAP_CCMS_ootspdbs02_PI1_01
    MTE:PI1\IEngine_PI1_001 Integration Server\Category MAPPING\Message alerts by Error Codes
    Client:001
    User:PIAFUSER
    Severity:       50</i>
    May I know how I can configure the contents of this message?
    I can't seem to find them in any of the CCMS alerts settings.
    Please help.
    Thanks.
    Ron

    Hi,
    Go through these links..
    /people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i
    http://help.sap.com/saphelp_nw04/helpdata/en/17/550c404a435509e10000000a1550b0/content.htm
    https://websmp102.sap-ag.de/monitoring
    http://help.sap.com/saphelp_nw04/helpdata/en/2a/ae8d4243a5de54e10000000a155106/frameset.htm
    /people/sap.india5/blog/2005/12/06/xi-ccms-alert-monitoring-overview-and-features
    http://help.sap.com/saphelp_nw04/helpdata/en/25/27fb1c56ff3b41a5d6807d3174d5c7/frameset.htm
    regards
    manoj kumar

  • Integrity constraint error during install

    We have installed htmldb on zlinux from the companion CD.
    Because we had an error during install of the flows schema we repeat it (have removed the Flows-User and Flow-Files before) using ins.sql! The apache was still running.
    Most of the new installation was fine but near the end we got:
    error creating "Procedure arguments" id=122 Ora-01400, cannot insert NULL into ("FLOWS_010500,"WWv_Flows_STEPS","SECURITY_GROUP_ID")
    declare
    Error at line1
    Ora-02291- integrity constraint(FLOWS_0150000.WWV_FLOW_PLUG_ZO_PAGE_FK) violated
    parent key not found
    ORA-06512 at "FLOWS_01500.WWV_FLOW_API line 4695
    ...

    OK, it's solved:
    I finally managed to install Apex 3.0 correctly once I figured out my error.
    I was logging in remotely to the server the dadbase was on, then trying to connect to sqlplus using 'sys/password@instance as sysdba' to run the script.
    Turns out that the problem had something to do with sys not being allowed to be sysdba when I log in remotely, or that having the username/password and instance info in there made the program think I was logging in remotely and therefore not giving me sysdba privileges.
    The root of the problem was running the install .sql without the correct privileges.
    Since I found out the database server I was trying to install on uses OS authentication, I remote-connected to the database server as the oracle user, tried to run the install .sql again after connecting to sqlplus: 'conn / as sysdba'
    and everything worked like a charm!
    ~PF :)

  • Conversion Agent - Mail Adapter integration issue

    Hi Experts,
    I have a Conversion Agent Serializer for generating a text file on the receiver side.
    The Serializer works perfectly with the File Adapter on the receiver
    side and generates the text file.
    Now I have a requirement to send this file as an attachement in an email.
    When I include the Serializer Module in the File Adapter
    (Receiver), the email is not triggered.
    The Communication Channel Monitoring shows the following:
    2007-04-29 07:34:55      Success         Message successfully received
    by messaging system. Profile: XI URL:
    http://bibox01:50000/MessagingSystem/receive/AFW/XI Credential (User):
    PIISUSER      
    2007-04-29 07:34:55      Success         Using connection
    Mail_http://sap.com/xi/XI/System. Trying to put the message into the
    receive queue.
    2007-04-29 07:34:55      Success         Message successfully put into
    the queue.    
    2007-04-29 07:34:55      Success         The message was successfully
    retrieved from the receive queue.     
    2007-04-29 07:34:55      Success         The message status set to DLNG.
    2007-04-29 07:34:55      Success         Delivering to channel:
    FIle_Mail     
    2007-04-29 07:34:55      Success         MP: entering 
    2007-04-29 07:34:55      Success         MP: processing local module
    localejbs/sap.com/com.sap.nw.cm.xi/CMTransformBean    
    2007-04-29 07:34:55      Success         TransformationName:
    TravelexBAI_Serializer
    2007-04-29 07:34:56      Success         CM_Transformation_succeeded  
    2007-04-29 07:34:56      Success         MP: processing local module
    localejbs/sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean      
    2007-04-29 07:34:56      Success         Mail: message entering the
    adapter
    2007-04-29 07:34:56      Success         Mail: Receiver adapter entered
    with qos ExactlyOnce  
    2007-04-29 07:34:56      Success         Mail: calling the adpter for
    processing    
    2007-04-29 07:34:56      Success         Mail: call completed 
    2007-04-29 07:34:56      Success         Mail: continuing to response
    message 4ee64c80-f5d0-11db-8932-000bcdcf4920  
    2007-04-29 07:34:56      Success         Mail: sending a delivery ack
    2007-04-29 07:34:56      Success         Mail: sent a delivery ack    
    2007-04-29 07:34:56      Success         MP: leaving  
    2007-04-29 07:34:56      Success         The message was successfully
    delivered to the application using connection
    Mail_http://sap.com/xi/XI/System.     
    2007-04-29 07:34:56      Success         The message status set to DLVD.
    The Audit log above states that the Serializer was executed successfully
    and the the Mail Adapter was called.
    The Message Content shows the Payload being generated correctly. But the
    Email is still not triggered.
    Could someone please provide some help with pinpointing the issue over here.
    Michael, are you there??
    Thanks & Regards,
    Shobhit

    Hi Ahmad,
    The mail adapter works perfectly fine when I remove the Conversion Agent module from it. And the Conversion Agent module works perfectly fine with the File Adapter on the receiver side. So that authenticates that both the objects (Mail Adapter - receiver & Conversion Agent Serailizer module) are configured correctly as individual objects.
    I have used the following parameters in the receiver mail adapter:
    PARAMETERS
    Transport Protocall: SMTP
    Message Protocall: XIPAYLOAD
    URL: smtp://xyz.com
    Content Encoding: Base64
    Keep Attachments: <TICKED>
    MODULE
    Processing Sequence==>>
    Module Name: localejbs/sap.com/com.sap.nw.cm.xi/CMTransformBean
    Type: Local EJB
    Module Key: 1
    Module Configuration==>>
    Module key: 1
    ParameterName: TransformationName
    Parameter Value: <SerializerServiceName>
    Regards,
    Shobhit

  • Error in SXMB_MONI in SOAP Header -- Call Adapter

    Hi ALL,
    Got a problem with monitoring activity.
    In SXMB_MONI, iam getting errors with Call Adapter section in SOAP HEADER section of the message.
    The Error part shows 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="1">
      <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: Problem inserting 4657f861-f853-60e8-e100-00000a80314d(INBOUND) into the database: java.sql.SQLException: ORA-25153: Temporary Tablespace is Empty</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Can anybody give me a clear picture of the exact error and what could be the diagnosis for this particular problem.
    cheers,
    Santosh

    Hi Santhosh
    1.Check your authorization settings in XI and R/3. Whether the user has sufficient rights to execute the Function Module etc. This is the most common reason for this error.
    2.If the XI system was brought online even before the R/3 system then re-activate the communication channels from the Integration directory.
    Cheers..
    Vasu
    <u><i><b>** Reward Points if found useful **</b></i></u>

  • Alerts not getting Triggered for Integration Engine Error

    Hi,
    We are configuring Alert Framework in our project. Here when the scenario fails at communication channel we receive alerts but when it fails in message mapping we aren't getting any alerts.
    Below are the settings:
    Alert rule created with no restrictions (Sender: * Receiver: *)
    Where did error occur ? No restriction
    Suppress multiple alerts of this Rule : Not set
    It would be great if some would help us on this.
    Regards,
    Tejas

    If you have created separate alert categories then test you alert as described later in this post. Else create a new alert category for your IE level exceptions. Give a description, long text, add your sap id in the fixed recipient list. Make sure you have ur email id configured for ur sap id in SU01. Create a rule in RWB. Make sure that you click on the "Add rule" tab once done. Keep all the entries as default. Give a description, remove suppress multiple alerts ,for now, keep rule active checkbox as checked, where did error occur- choose IE both stars.
    Now we need to test if this alert category is working fine. Go to se38 and execute RSALERTTEST. There give the name of your alert category. Execute. Now check in the ALRTDISP, if you get an entry there. Let me know....

  • SAP eWM: Integration Model error during transaction CFM2

    Hi,
    I am new in eWM and i am trying to transfer the material master, plant, shipping point, vendor and customer from SAP ECC 6.0 to eWM 5.0.
    I am getting this message:
    Inbound Queue is Blocked
    Queue for Current initial Data transfer is deregistered
    Target System : SCDCLT100 (My eWM system)
    Can someone help me to fix this problem so i can move on?
    I will realy appreciated
    Thanks & Regards
    Bouba

    Hi Sharad,
    Thank you very much for your reply.
    I was able to execute SMQ2 in eWM but i was not able to understsnd why the the product, vendor, customer,.. are  not yet created in eWM.
    The status is  Ready and when i executed, i got a system fail status.
    When i double click on the line i got this message:
    Business partner 0000000511: no arrangement(enclosure,appendix) with this. 0000000511 is the vendor i created in ECC 6 and i also link my plant to this vendor.
    Can you help me again to understsnd the root of the problem?
    Thanks & Regards
    Aboubakar

  • ERROR During call of SOAP with a SOAP- RFC- SOAP Synchronous scenario

    Hello Experts,
    I've recently created a SOAP->RFC->SOAP synchronous scenario but every time I'm invoking the SOAP via XMLSpy then i will hang and send a timeout error. Also a log in XI was generated as shown below.
    I hope you could help me on this one.
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Date and Time          28.09.2010 09:31:23
    Short text
         SQL error in the database when accessing a table.
    What happened?
         The database system detected a deadlock and avoided it by rolling back
         your transaction.
    What can you do?
         If possible (and necessary), repeat the last database transaction in the
          hope that locking the object will not result in another deadlock.
         Note which actions and input led to the error.
         For further help in handling the problem, contact your SAP administrator
         You can use the ABAP dump analysis transaction ST22 to view and manage
         termination messages, in particular for long term reference.
         Note which actions and input led to the error.
         For further help in handling the problem, contact your SAP administrator
         You can use the ABAP dump analysis transaction ST22 to view and manage
         termination messages, in particular for long term reference.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
          in
         procedure "DELETE_LUW_PACKET" "(FORM)", nor was it propagated by a RAISING
          clause.
         Since the caller of the procedure could not have anticipated that the
         exception would occur, the current program is terminated.
         The reason for the exception is:
         The database system recognized that your last operation on the database
         would have led to a deadlock.
         Therefore, your transaction was rolled back
         to avoid this.
         ORACLE always terminates any transaction that would result in deadlock.
         The other transactions involved in this potential deadlock
         are not affected by the termination.
    Regards,
    Alfred

    Normally such an error comes when the DB of SAP PI is full.
    Contact your BASIS or ADMIN team and ask them to free the DB space.
    Regards,
    Abhishek.

Maybe you are looking for

  • How to get the assignees for a specific role in process in BPM 11g

    Hi, Gurus, I am using BPM 11g. I am trying to retrieve all the assignees for a a specific role in process. It will be a parameter for a business rule to do further routing rule. But it seems there is no way to get the information. I found that there

  • Create a Puchase order using Bapi

    Hi all, I have requirent to create  a PO by using Bapi based on text file sent from interface system here with the file layout. 1.plant (ekko-werks)                 2. material   EKPO-MATNR      3. pur.group       EKKO-EKGRP 4.vendor      EKKO-LIFNR

  • Strange problem with opening PDF's

    Hello, We have roughly 80 users at one location that use a terminal server session to access our medical software.  A certain group of four users that share a network printer have issues within the medical software when they try to open a scanned in

  • Hi , friends pls explain abap mapping and message mapping

    1) pls explain abap mapping and message mapping    send me screen shorts also.

  • Solaris Volume Manager - Raid5 device permanently resyncing

    A device on my RAID5 array appears to have failed, and has been taken over by the hot spare: -bash-3.00$ /usr/sbin/metastat d100 d100: RAID State: Resyncing Hot spare pool: hsp001 Interlace: 32 blocks Size: 286457856 blocks (136 GB) Original device: