Tracing messages in SAP PI 7.0

Hi,
Please let me know how to check the messages in PI 7.0 using message ID provided by other middleware system.
Flow is source system ---> non-sap middleware(messaging system)--->SAP PI --->SAP ECC.
Message ID provided by non sap middleware system is different from PI Message ID.In this case ,how to check the messages in PI 7.0.
Does payload based message search possible in PI 7.0.?If so,how does it achieved in PI 7.0?
Regards,
Karthiga

Hi Karthiga,
As per my knowledge, from PI7.0 EHP3 we can use  user defined selection criteria in SXMB_MONI for searching PI messages based on some particular field present in payload.
For user defined search criteria config, there are many links available.
Step by Step guide for Payload based message search in SAP PI
Regards,
SP

Similar Messages

  • How to log in to Service Desk to create sample message to SAP?

    Dear all,
    How to log in to Service Desk under my Solution Manager server to create sample message to SAP under Component: SV-SMG-SUP?
    Regards
    GN

    Hi GN,
    You have different options to create messages in test component SV-SMG-SUP-TST:
    1. if you are on 7.1 you can create message using CRM_UI
    2. If you are using lower vrsion then either you can create message using Workcenter or using transaction NOTIF_CREATE or using menu --> Help --> Create support message.
    Thanks
    Regards,
    Vikram

  • SR Log Error - |  Message  : com.sap.esi.uddi.sr.api.exceptions.SRException

    Hi,
    We are getting below errors in /nwa/logs. We have our PI (7.11) and Service Registry configured on the same server. And have out CE (7.2) system connected to this service registry. Does any one has similar experience? Please let me know if you have any solution for the same.
    SR Log Error
    |  11-Nov-11  14:10:45.568
    |  Method   : getClassificationSystems()
    |  Class    : com.sap.esi.uddi.sr.api.ws.ServicesRegistrySiImplBean
    |  ThreadID : 146
    |  Message  : com.sap.esi.uddi.sr.api.exceptions.SRException: No classification system found for ID 'QName: Namespace= http://uddi.sap.com/classification; Name=  ConfigurationFlags'
    |
    |       com.sap.esi.uddi.sr.impl.common.Utility.cs2srException(Utility.java:122)
    |       com.sap.esi.uddi.sr.impl.ejb.ServicesRegistryBean.getClassificationSystems(ServicesRegistryBean.java:242)
    |       sun.reflect.GeneratedMethodAccessor1325.invoke(Unknown Source)
    |       sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    |       java.lang.reflect.Method.invoke(Method.java:585)
    |       com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
    |       com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    |       $Proxy1087.getClassificationSystems(Unknown Source)
    |       com.sap.esi.uddi.sr.api.ws.ServicesRegistrySiImplBean.getClassificationSystems(ServicesRegistrySiImplBean.java:456)
    |       sun.reflect.GeneratedMethodAccessor1324.invoke(Unknown Source)
    |       sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    |       java.lang.reflect.Method.invoke(Method.java:585)
    |       com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_WS.invoke(Interceptors_WS.java:31)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
    |       com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:203)
    |       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:512)
    |       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:486)
    |       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:256)
    |       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:176)
    |       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:112)
    |       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:70)
    |       SoapServlet.doPost(SoapServlet.java:51)
    |       javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    |       javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    |       com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
    |       com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
    |       com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
    |       com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
    |       com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
    |       com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
    |       com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:245)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
    |       com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    |       com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    |       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    |       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
    |       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    |       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
    |       com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
    |       com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
    |       com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    |       com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    |       com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    |

    Hi,
    Refer Error:Service Registyr Configuration PI 7.11
    and http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8071b1b8-3c5c-2e10-e7af-8cadbc49d711?QuickLink=index&overridelayout=true
    Thanks,
    Chandra

  • Service Desk: error while sending message to SAP

    Hello Gurus,
    I have configured Service Desk in Solution Manager. When i create a message in one of my Satellite Systems the message appears in Solman but when i try ro send the message to SAP i get the following error.
    "You do not have authorization to Send or Compare a notification"
    The user has SAP_ALL and NEW and the same has been maintained in AISUSER table. After i get the error i executed SU53 but there are no missing authorization.
    Can someone please tell me what the problem could be?
    Regards
    Anil Verma B

    Hi,
    Apart from the SAPOSS, SAP-OSS, SAP-OSS-LIST-01  rfcs, pls ensure the basic authorizations for solman has been verified and given.
    SAP_SUPPDESK_ADMIN
    SAP_SUPPDESK_CREATE
    SAP_SV_FDB_NOTIF_BC_ADMIN
    Please also verify if you had the BADI settings done correctly as per note
    1140822    SAP customer number for installation number &1 unkn
    Hope this helps.
    Cheers
    Sh

  • Message on SAP login screen

    Hi all,
    How to add a system message on the SAP logon screen.
    I just want to put display some content and links on screen where we enter client and username and password.
    regards,
    helpful answers are surely rewarded.

    Hi,
    Personalization of your SAP system  logon screen, splash screen etc
    1) Adding text to the SAP logon screen. This is very handy for identifying which SAP system the user is about to log onto, especially non production boxes. You can also warn them here of pending changes, updates or outages. Because it is up while they are typing in their userid and password, they can't claim they missed the system message. SAP icons like the stop sign and warning signs can also be displayed. Details can be found in OSS note #205487. Here are the guts:
    Go to Transaction SE61 and select the document 'General text' (selection via F4 help), and create a text with the name ZLOGIN_SCREEN_INFO in the language defined with profile parameter zcsa/system_language.
    If the text does not exist in the system language, no output is made.
    Note that there is space for 16 lines with 45 fixed-font characters each or for approximately 60 proportional space font characters on the logon screen.
    Title lines (can be recognized by means of format keys starting with a 'U') are highlighted in the display.
    You may also output icons at the beginning of lines by using an icon code (for example, @1D@ for the STOP icon). You can get a list of icon codes from Report RSTXICON. Pay attention to the codes with two '@' symbols displayed by the report. You cannot include text symbols. The 'include indicator' cannot be used for this function. SUBHINT here. These can be used on system messages as well.
    Creating/changing this text requires a changeable system. Therefore, for production systems, SAP recommends maintaining the text in the upstream system and then transporting it. To do this, select a transportable (customer) development class when you create the text and save the active version prior to the export. The transport is done via the transport object R3TR DOCT ZLOGIN_SCREEN_INFO The text can be changed in the original system only (see TADIR entry R3TR DOCT ZLOGIN_SCREEN_INFO). When making a change in a non-original system, a modified text would be generated which cannot be represented sensefully on the initial screen.
    2) Changing the splash screen on the main menu can add some pizzazz to the otherwise boring screen. It can also be changed easily on a regular basis. For production systems a company logo and/or company mission statement might be appropriate. Here are the instructions:
    First, in transaction SMW0 (SAP Web Repository), select "Binary data for WebRFC applications. The logo must be in a .gif format. From this transaction, create a new object, then choose to IMPORT. You must then specify the path to the .gif object you have saved, and select the option to TRANSFER.
    Then, maintain table SSM_CUST via SM30. Change the field START_IMAGE to the name of the object you created in SMW0.
    3) Changing the rippling water on the top right on all is easy but tedious and requires no change to the SAP system. The file name is 'sapalogo.bmp' and resided in the directory "SAPpcsapguithemesdefault". Looking at this file you can see how it works. Use an editor like Paint and replace each of the SAP ripple images with a morphing image of your own. Make sure the new image is the same size as the original. There are 33 images in the original but you don't need that many. One idea for a morphing image would be to take your company logo and have it build its way across the screen and then off again.
    4) Changing the startup movie is even easier. Replace the file 'sapss.avi' with a short avi of your own. This file resides in the same directory as 'sapalogo.bmp
    Pls reward points,
    Regards,
    Ameet

  • Error Message from  SAP GUI

    Hi,
    I have designed a Custom screen for one of my requirements. However when the screen is displayed, I am facing an error message from SAP Front End Server that  says " Erroneous data received from server. Application may not work correctly".
    What could be the reason ?
    Thanks & Regards,
    Venkatesh.

    Hi,
    Please check the belos SAP notes
    1453114    Maximum string length
    1161022    Dialog box "Erroneous data received from server"
    1524462 - Erroneous Data received from server. Application may not work correctly.
    Regards,
    Naveen.

  • STEPS TO create OSS message for sap

    hi
    we i need to k now how to create a oss message for sap
    pls suggest? the steps
    regards
    Arora

    Hi,
    1. go to service.sap.com
    2. Click SAP Support Portal
    3. you can see Help & Support tab (after HOME)
    4. click that
    5. In that tab you can see Report a Product Error
    If you have suitable rights you can post your OSS message from here.
    Regards,
    Omkar.

  • In solman 4.0 how to send message to SAP through service desk

    Dear all,
            I have configured service desk functionality, My requirement is from service desk how to send message to SAP.
    Regards,
    Pavan.

    Hi,
    Following the steps:
    ƒBasic configuration - RFC Connections to SAP
    Check if the RFC Connectino SAPOSS is working properly
    Check if load distribution group is set to EWA
    The RFC Connections:
    - SAP-OSS (Send Message to SAP)
    - SAP-OSS-LIST-O01 (Update Message from SAP)
    will be created automatically by the system with a user which has been assigned
    previously.
    IMG Path: SAP Web Application Server | SAP Web Application Server | SAP Solution Manager| Basic Settings | SAP Solution Manager System | Connection to SAP | Assign user for forwarding Service Desk Message
    With transaction SM59 you can adjust the RFC connections.
    - For further information on SAP R/3 Front-end connections, see SAP Notes: 33135, 766505, 24177
    - To forward Service Desk notifications and Issues to SAP, you need to assign a user to the SAPNet R/3
    Front-end connection to SAP.
    Activities:
    - 1. From the SAP Solution Manager (transaction SOLUTION_MANAGER), choose (Edit-> Global Settings.
    - 2. Choose Display<->Change.
    - 3. For SAP Service Marketplace, specify http://service.sap.com as the URL.
    - 4. In the Connection to SAP tab, specify SAPOSS as the RFC destination. Note that the entry is casesensitive.
    - 5. For User forwading messages, enter a valid user and a password. This user will require all the authorizations for SAPNet R/3 Front-end for your customer number.
    - 6. Save your changes.
    The system automatically generates the following RFC destinations and assigns the S-User and password you specified: SAP-OSS, SAP-OSS-LIST-O01
    Good Lucky!

  • Finding message in SAP Business Connector with IDoc number

    Hi Experts,
    Since there is no separate forum for Business Connector, posing my question here.
    Does anyone have idea how we can find a message in SAP Business Connector if we know the source IDoc number, the same way we use IDX5 in PI.
    Thanks,
    Dhawal

    AFAIK there is no simple way.  What I usually do is compare timestamps. The Idoc is usually processed on the B.C. within the same minute.
    We only have up to 10 Idocs within one minute and I do not have to search every day. So it works for me.

  • Archiving  and Deleting of XML Messages in SAP NetWeaver PI 7.31 single stack

    Hello my XI friends!
    Need step by Step Guide to Archiving
    and Deleting of XML Messages in
    SAP NetWeaver PI 7.31 single stack
    Similar to these instructions
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0afdd69-a8a7-2d10-7e9a-cbf6fa21c5a7?quicklink=index&overridelayout=true
    Regards,
    Rinaz

    Please check the below blog  for archiving java only-(XMLDAS)
    http://scn.sap.com/community/pi-and-soa-middleware/blog/2011/11/16/aae-archiving-in-sap-pi-711-with-xmldas
    For deletion there is standard delete job..
    https://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/b2e0036b156ff4e10000000a42189b/frameset.htm
    Message was edited by: Hareesh Gampa

  • How to forward support messages to SAP in non-working time automatically?

    Hi colleagues and Happy New Year!
    I have a question: how to forward support messages to SAP at non-working time automatically?
    Details:
    when a support message is created at working time it shouldn't leave my system, but when
    a support message is created at non working time, for example, on saturday night it should be sent to SAP automatically. Where in the system I can find the options to customize it to provide these requirements?
    Edited by: Helen Rudnikovskaja on Jan 3, 2009 12:36 PM

    Hi These 2 notes wil solve your problem,
    Note 1084744 - Problems with the automatic function "Send to SAP"
    Note 1225682
    Pls assign pts.

  • Header missing in SOAP message header (SAP XI Extension)

    Hi Experts,
    We are implementing interface MasterDataUpdateConfirmation_Out between 2 SAP ERP systems. The middleware is SAP PI.
    SAP PI team requested a change in this interface Stack - Replace Stack ABAP by Stack Java. The changes were made.
    However, now we get an error in the interface in the SAP ERP sender system, but the message arrives to SAP PI where is processed without errors and also arrives to SAP ERP receive system and the message is also processes without errors.
    The error we have in XML message in SAP ERP sender system is:
    XML element {http://schemas.xmlsoap.org/soap/envelope/}Header missing in
    SOAP message header (SAP XI Extension)
    Exception of class CX_XMS_SYSERR_PARSER
    Can anyone please help us? We have no ideia what to do.
    Thanks in advance,
    RS

    Hi again,
    I don't know if it is important, but the communication is asynchronous and the sender system is SAP ECC 6.0.
    Thanks!

  • Envelope missing in SOAP message header (SAP XI Extension)

    I have scenario where in I am sending a file from XI to PCK. BUt i am getting a following error.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIProtocol</SAP:Category>
      <SAP:Code area="PARSER">ITEM_MISSING</SAP:Code>
      <SAP:P1>Envelope</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>XML tag Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I am enclosing the file i am trying to send.
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:CFP_SENDER_MT xmlns:ns0="HTTP://PCKXI.WORLDBANK.ORG">
    - <SEND>
      <TF_Number>12</TF_Number>
      <TF_Desc>1212</TF_Desc>
      </SEND>
      </ns0:CFP_SENDER_MT>
    Can somebody please enlighten me about this error? Points would be rewarded immediately
    Regards,
    Manish

    Dear Manish,
    quite often the reason for this kind of error
    is the fact that the receiver of the XI message is
    returning a http response to the Integration Server.
    As of XI3.0 SP21 / PI7.0 SP13 this response
    is also properly parsed and visible in the error
    header of the XI message.
    For almost all prior support package levels an
    advanced correction is available as per OSS note:
    1064346 Improved error output for connection problems
    Please check whether this applies to your system.
    If so, you will see detailed information on the error
    in the error header object of the XI message as soon
    as this issue re-occurs.
    Best Regards,
    Harald Keimer
    XI Development Support
    SAP AG, Walldorf

  • Send IDOC Messages to SAP

    I have a text file which contains lots of records. I have created a schema for that text file.Then I mapped this schema with IDOC (Acc_Document03)schema.Now I want to send this IDOC message to SAP.There is not shown any errors by BizTalk admin console.But
    the message is not reached to SAP.But when I  send this IDOC message to a location through File adapter instead of SAP adapter then it has reached there .Why this is happening ?
    Please also tell me how to send multiple IDOC message to SAP ?

    Hi Glenn.
    I got the following error:
    The adapter failed to transmit message going to send port "Interplx.SAP_SendPort" with URL "sap://CLIENT=130;LANG=EN;@A/10.151.97.51/00?RfcSdkTrace=False&AbapDebug=False&ListenerGwHost=10.151.97.51&ListenerGwServ=SAPGW00&ListenerProgramId=BTSIDOC_DEV-".
    It will be retransmitted after the retry interval specified for this Send Port. Details:"System.Xml.XmlException: Start element 'ITEMNO_ACC' from namespace 'http://Microsoft.LobServices.Sap/2007/03/Types/Idoc/3/ACC_DOCUMENT03//701' expected. Found element
    'ITEMNO_ACC' from namespace ''.
    Server stack trace: 
       at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
       at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
       at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
       at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
       at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)".
    Prakash

  • How to setup  workplace message in SAP system

    Hi Experts,
    how to setup  workplace message in SAP system.
    when am logon SAP GUI i am getting mesage of Document workplace. ( you have one new document)
    saying that in Inbox i have 1 document.
    my client they dont want Receive that pop up message. thy want receive document but no pop up message .
    where can i do customize thia i hope there was a T-code for this.
    Thank INadvance,
    Anthyodaya.

    Hi,
      Go to transaction SBWP  and Click Distribution list and choose the list where you can find one check box send express. you just deselect the check box and save it. After that you will not receive any express note . but you will get messge to your inbox.
    Regards,
    abi

Maybe you are looking for