IDoc not received by the Webmethods

Dear Abapers,
I have a scenario :
Here the idoc  is being created perfectly with all the segments prooperly populated.  Also from SAP side, we are getting the message that it has been sent.
However, the receiver ( Webemthods) is saying that it is not receiving the idocs . So, what can be the possible reason ??
Appreciate your reply...
Thanks and Best Regards,
Kunal.

error send questionnaire in srm Ros
Registration - Error after Send / No Questionnaire
ROS Questionnaire link sent by email
ROS Questionaire
Re: Status for the transferred Suppliers is not updated in ROS client!

Similar Messages

  • Outbound IDOC not received at the receiver system.

    Hi,
    Im sending an IDOC from sap to a non-sap system. During this process, from sap system it is executing successfully without any erros and the status is also '03' .
    The problem is that the other system is unable to receive the IDOC sent from SAP system.
    The connection is like TCP/IP and the registered server program is given as 'PROGRID' in RFC destination.
    I would like to know what would be the possible cases where this IDOC is not received at the receiver system.
    The configuration is perfect as per my knowledge. Just want to confirm one thing 'do i need to include any message type such as "SYNCH".
    Awaiting for your solutions.
    Thanks
    rohith

    Hi,
    If the IDOC is sent successfully from the sender system then the status of the IDOC will be '03' , no matter whether the receiver has received the IDOC or not.
    As per your case,
    Check the Partner Profile parameters , whether the basic and extended message types are used properly.
    The message type Synchron (Sync) is generally needed in Inbound IDOC side. Check whether you have added SYNCH or not.
    Hope this Helps.
    Regards,
    Abhinab Mishra.
    Experience is the name everyone gives to their mistakes.

  • Orders02 IDOCs not received on the  EDI side

    Hello SRMer's
    System Information:
    R/3 4.6 C
    Issue related to EDI Purchase orders Pushed from R/3:
    We have a situation where the  Orders02 IDOCS in R/3 have status Code 3  in WE02 (data passed to port successfully) with a green light, but they are not recieved on the EDI side.
    Is there any extra step that needs to be done to push these IDOCS to the EDI side.
    Thanks in advance.
    Points will be rewarded for answers.
    Best Regards,
    Bob

    go to we09 and send it forcefully...and then check it.

  • Idoc Not received?

    Hi
    During data loading , I got one Error that Idoc Not received.
    What will be the cause of problem and How to resolve it?
    Regards & Thanks
    Durai

    Hi Robert Negro !
    I checked  , Dump has been there.
    How can I resolve?
    what will be other causes apart from the Dump?
    Thanks A Lot .
    Regards
    Durai

  • Documents I forward are not received under the original document name. How do I solve this?

    Documents I forward are not received under the original document name. How do I solve this?

    If you're referring to the name of the attatchment showing when viewing the entire email, that's there's no way to change how it's done.  The title and body of the actual document is unchanged after it's opened. 
    Does this naming of the attachment really confuse the recipient?  If so, put something in the body of the email to make it clear what's attached.

  • TS2755 My ipad does not receive messages, the bubble in the green background. My iphone does.

    My ipad does not receive messages, the bubble in the green background. My iphone does.
    I can use my ipad to send messages, but it only moniltors the ones i send with the ipad. All the other messages I get on my iphone are missing.
    Any idea why?

    "The bubble in the green background" indicates the message was an SMS (cellular text) message.  If the background were blue, it would mean the message was an iMessage.
    The difference is important.  Your iPad is not a cellular telephone.  It cannot send or receive cellular text or MMS messages.  It is, however, an Apple device which means it can communicate using Apple's iMessage to/from other Apple devices (typically over WiFi).

  • Aironet 1600 - A response was not received from the router or access point

    Hi,
    I'm trying to set up a wireless network with multiple SSID's. The new network only has CISCO products (router, switches). For the moment I'm trying to connect to 1 SSID (Windekind.Gast). the SSID is visible but when connecting devices have te folowing error message in the log:
    Connection status summary
    Connection started at: 2015-02-17 09:55:49-951
    Profile match: Success
    Pre-Association: Success
    Association: Fail
    Security and Authentication: Not started
    Root cause:
    Wireless association to "Windekind.Gast" failed
    A response was not received from the router or access point.
    Detailed root cause:
    Wireless association to this network failed. Windows did not receive any response from the wireless router or accesspoint.
    The signal is perfect (I'm only a few feet away from the AP).
    To make sure there is no dhcp problem I tested the swich port in access mode for vlan 30 which supplied an IP correctly. I'm really not seeing the problem and searched the web for days now! Any help would be very much appreciated! 
    Below the config of the access point (done via de web interface).
    ! Last configuration change at 05:30:28 UTC Mon Mar 1 1993
    version 15.2
    no service pad
    service timestamps debug datetime msec
    service timestamps log datetime msec localtime show-timezone
    service password-encryption
    hostname AP002-C
    logging rate-limit console 9
    enable secret 5 $1$Bxv3$Of8o5..8v6gzIiAe2tXlh/
    no aaa new-model
    no ip cef
    dot11 syslog
    dot11 vlan-name Windekind.Directie vlan 50
    dot11 vlan-name Windekind.Gast vlan 30
    dot11 vlan-name Windekind.Klasnet vlan 40
    dot11 ssid Windekind.Directie
    vlan 50
    band-select
    authentication open
    mobility network-id 50
    dot11 ssid Windekind.Gast
    vlan 30
    band-select
    authentication open
    authentication key-management wpa version 2
    mbssid guest-mode
    mobility network-id 30
    wpa-psk ascii 7 14201B05080121222A2C6A6D63
    dot11 ssid Windekind.Klasnet
    vlan 40
    band-select
    mobility network-id 40
    crypto pki token default removal timeout 0
    username Cisco password 7 112A1016141D
    bridge irb
    interface Dot11Radio0
    no ip address
    no ip route-cache
    encryption vlan 30 mode ciphers aes-ccm tkip
    ssid Windekind.Directie
    ssid Windekind.Gast
    ssid Windekind.Klasnet
    antenna gain 2
    stbc
    beamform ofdm
    mbssid
    speed basic-1.0 2.0 5.5 11.0 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 m0. m1. m2. m3. m4. m5. m6. m7. m8. m9. m10. m11. m12. m13. m14. m15.
    channel 2452
    no preamble-short
    station-role root
    payload-encapsulation dot1h
    bridge-group 1
    bridge-group 1 subscriber-loop-control
    bridge-group 1 block-unknown-source
    no bridge-group 1 source-learning
    no bridge-group 1 unicast-flooding
    interface Dot11Radio0.30
    encapsulation dot1Q 30
    no ip route-cache
    bridge-group 30
    bridge-group 30 subscriber-loop-control
    bridge-group 30 spanning-disabled
    bridge-group 30 block-unknown-source
    no bridge-group 30 source-learning
    no bridge-group 30 unicast-flooding
    interface Dot11Radio0.40
    encapsulation dot1Q 40
    no ip route-cache
    bridge-group 40
    bridge-group 40 subscriber-loop-control
    bridge-group 40 spanning-disabled
    bridge-group 40 block-unknown-source
    no bridge-group 40 source-learning
    no bridge-group 40 unicast-flooding
    interface Dot11Radio0.50
    encapsulation dot1Q 50
    no ip route-cache
    bridge-group 50
    bridge-group 50 subscriber-loop-control
    bridge-group 50 spanning-disabled
    bridge-group 50 block-unknown-source
    no bridge-group 50 source-learning
    no bridge-group 50 unicast-flooding
    interface Dot11Radio1
    no ip address
    no ip route-cache
    encryption vlan 30 mode ciphers aes-ccm tkip
    ssid Windekind.Directie
    ssid Windekind.Gast
    ssid Windekind.Klasnet
    antenna gain 4
    no dfs band block
    stbc
    beamform ofdm
    mbssid
    speed basic-6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 m0. m1. m2. m3. m4. m5. m6. m7. m8. m9. m10. m11. m12. m13. m14. m15.
    channel dfs
    station-role root
    payload-encapsulation dot1h
    bridge-group 1
    bridge-group 1 subscriber-loop-control
    bridge-group 1 block-unknown-source
    no bridge-group 1 source-learning
    no bridge-group 1 unicast-flooding
    interface Dot11Radio1.30
    encapsulation dot1Q 30
    no ip route-cache
    bridge-group 30
    bridge-group 30 subscriber-loop-control
    bridge-group 30 spanning-disabled
    bridge-group 30 block-unknown-source
    no bridge-group 30 source-learning
    no bridge-group 30 unicast-flooding
    interface Dot11Radio1.40
    encapsulation dot1Q 40
    no ip route-cache
    bridge-group 40
    bridge-group 40 subscriber-loop-control
    bridge-group 40 spanning-disabled
    bridge-group 40 block-unknown-source
    no bridge-group 40 source-learning
    no bridge-group 40 unicast-flooding
    interface Dot11Radio1.50
    encapsulation dot1Q 50
    no ip route-cache
    bridge-group 50
    bridge-group 50 subscriber-loop-control
    bridge-group 50 spanning-disabled
    bridge-group 50 block-unknown-source
    no bridge-group 50 source-learning
    no bridge-group 50 unicast-flooding
    interface GigabitEthernet0
    no ip address
    no ip route-cache
    duplex auto
    speed auto
    bridge-group 1
    bridge-group 1 spanning-disabled
    no bridge-group 1 source-learning
    interface GigabitEthernet0.30
    encapsulation dot1Q 30
    no ip route-cache
    bridge-group 30
    bridge-group 30 spanning-disabled
    no bridge-group 30 source-learning
    interface GigabitEthernet0.40
    encapsulation dot1Q 40
    no ip route-cache
    bridge-group 40
    bridge-group 40 spanning-disabled
    no bridge-group 40 source-learning
    interface GigabitEthernet0.50
    encapsulation dot1Q 50
    no ip route-cache
    bridge-group 50
    bridge-group 50 spanning-disabled
    no bridge-group 50 source-learning
    interface BVI1
    ip address 10.0.0.81 255.255.255.0
    no ip route-cache
    ip default-gateway 10.0.0.1
    ip forward-protocol nd
    ip http server
    no ip http secure-server
    ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
    logging facility user
    bridge 1 route ip
    line con 0
    line vty 0 4
    login local
    transport input all
    end

    Hi Rasika
    thanks for the reply! 10.0.0.81 belongs to vlan 1. I changed the config as suggested but no luck.. (same problems are logged in the event viewer). the ap is connected to a switchport in trunk mode and vlan 1 is the native lan (untagged). the port also is joined to vlan 30 (and others).
    Below the new config. Hope you can see an error..
    ! Last configuration change at 22:56:10 UTC Thu Apr 1 1993
    version 15.2
    no service pad
    service timestamps debug datetime msec
    service timestamps log datetime msec localtime show-timezone
    service password-encryption
    hostname AP002-C
    logging rate-limit console 9
    enable secret 5 $1$Bxv3$Of8o5..8v6gzIiAe2tXlh/
    no aaa new-model
    no ip cef
    dot11 syslog
    dot11 vlan-name Default vlan 1
    dot11 vlan-name Windekind.Directie vlan 50
    dot11 vlan-name Windekind.Gast vlan 30
    dot11 vlan-name Windekind.Klasnet vlan 40
    dot11 ssid Windekind.Directie
       vlan 50
       band-select
       authentication open
       mobility network-id 50
    dot11 ssid Windekind.Gast
       vlan 30
       band-select
       authentication open
       authentication key-management wpa version 2
       mbssid guest-mode
       mobility network-id 30
       wpa-psk ascii 7 14201B05080121222A2C6A6D63
    dot11 ssid Windekind.Klasnet
       vlan 40
       band-select
       mobility network-id 40
    crypto pki token default removal timeout 0
    username Cisco password 7 112A1016141D
    bridge irb
    interface Dot11Radio0
     no ip address
     no ip route-cache
     encryption vlan 30 mode ciphers aes-ccm tkip
     ssid Windekind.Directie
     ssid Windekind.Gast
     ssid Windekind.Klasnet
     antenna gain 2
     stbc
     beamform ofdm
     mbssid
     speed  basic-1.0 2.0 5.5 11.0 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 m0. m1. m2. m3. m4. m5. m6. m7. m8. m9. m10. m11. m12. m13. m14. m15.
     no preamble-short
     channel 2452
     station-role root
     payload-encapsulation dot1h
    interface Dot11Radio0.1
     encapsulation dot1Q 1 native
     no ip route-cache
     bridge-group 1
     bridge-group 1 subscriber-loop-control
     bridge-group 1 spanning-disabled
     bridge-group 1 block-unknown-source
     no bridge-group 1 source-learning
     no bridge-group 1 unicast-flooding
    interface Dot11Radio0.30
     encapsulation dot1Q 30
     no ip route-cache
     bridge-group 30
     bridge-group 30 subscriber-loop-control
     bridge-group 30 spanning-disabled
     bridge-group 30 block-unknown-source
     no bridge-group 30 source-learning
     no bridge-group 30 unicast-flooding
    interface Dot11Radio0.40
     encapsulation dot1Q 40
     no ip route-cache
     bridge-group 40
     bridge-group 40 subscriber-loop-control
     bridge-group 40 spanning-disabled
     bridge-group 40 block-unknown-source
     no bridge-group 40 source-learning
     no bridge-group 40 unicast-flooding
    interface Dot11Radio0.50
     encapsulation dot1Q 50
     no ip route-cache
     bridge-group 50
     bridge-group 50 subscriber-loop-control
     bridge-group 50 spanning-disabled
     bridge-group 50 block-unknown-source
     no bridge-group 50 source-learning
     no bridge-group 50 unicast-flooding
    interface Dot11Radio1
     no ip address
     no ip route-cache
     encryption vlan 30 mode ciphers aes-ccm tkip
     ssid Windekind.Directie
     ssid Windekind.Gast
     ssid Windekind.Klasnet
     antenna gain 4
     no dfs band block
     stbc
     beamform ofdm
     mbssid
     speed  basic-6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 m0. m1. m2. m3. m4. m5. m6. m7. m8. m9. m10. m11. m12. m13. m14. m15.
     channel dfs
     station-role root
     payload-encapsulation dot1h
    interface Dot11Radio1.1
     encapsulation dot1Q 1 native
     no ip route-cache
     bridge-group 1
     bridge-group 1 subscriber-loop-control
     bridge-group 1 spanning-disabled
     bridge-group 1 block-unknown-source
     no bridge-group 1 source-learning
     no bridge-group 1 unicast-flooding
    interface Dot11Radio1.30
     encapsulation dot1Q 30
     no ip route-cache
     bridge-group 30
     bridge-group 30 subscriber-loop-control
     bridge-group 30 spanning-disabled
     bridge-group 30 block-unknown-source
     no bridge-group 30 source-learning
     no bridge-group 30 unicast-flooding
    interface Dot11Radio1.40
     encapsulation dot1Q 40
     no ip route-cache
     bridge-group 40
     bridge-group 40 subscriber-loop-control
     bridge-group 40 spanning-disabled
     bridge-group 40 block-unknown-source
     no bridge-group 40 source-learning
     no bridge-group 40 unicast-flooding
    interface Dot11Radio1.50
     encapsulation dot1Q 50
     no ip route-cache
     bridge-group 50
     bridge-group 50 subscriber-loop-control
     bridge-group 50 spanning-disabled
     bridge-group 50 block-unknown-source
     no bridge-group 50 source-learning
     no bridge-group 50 unicast-flooding
    interface GigabitEthernet0
     no ip address
     no ip route-cache
     duplex auto
     speed auto
    interface GigabitEthernet0.1
     encapsulation dot1Q 1 native
     no ip route-cache
     bridge-group 1
     bridge-group 1 spanning-disabled
     no bridge-group 1 source-learning
    interface GigabitEthernet0.30
     encapsulation dot1Q 30
     no ip route-cache
     bridge-group 30
     bridge-group 30 spanning-disabled
     no bridge-group 30 source-learning
    interface GigabitEthernet0.40
     encapsulation dot1Q 40
     no ip route-cache
     bridge-group 40
     bridge-group 40 spanning-disabled
     no bridge-group 40 source-learning
    interface GigabitEthernet0.50
     encapsulation dot1Q 50
     no ip route-cache
     bridge-group 50
     bridge-group 50 spanning-disabled
     no bridge-group 50 source-learning
    interface BVI1
     ip address 10.0.0.81 255.255.255.0
     no ip route-cache
    ip default-gateway 10.0.0.1
    ip forward-protocol nd
    ip http server
    no ip http secure-server
    ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
    logging facility user
    bridge 1 route ip
    line con 0
    line vty 0 4
     login local
     transport input all
    end
    t

  • Idoc not found in the receiving system

    Hi Experts,
    In the sending system idoc status is 03 (Data passed to port OK), but in the receiving system the idoc is not there. How to rectify this error?
    Thanks & Regards,
    Soumya.

    Hi Soumya,
               Check the RFC connections, becoz in the sending system once the IDOC is sent the status becomes 03 it does not check whether the IDOC has sent to the received system, if there are any errors before sending the IDOC it will not send and the status will be 01, so check the RFC connections at sending and receiving systems.......
    Reward points if this helps............
    Regards,
    Ravi G

  • SAP ERP - SAP ME - iDOCS - Not received

    Dear Experts,
    We are trying to send data ( MATMAS iDOC) from ERP to ME.
    We used the below transaction in SAP.
    1. using BD10 transaction in SAP ( Send material) Idoc was sent
    Checks :
    We checked in WE05 in SAP and found that Idocs sent is successful
    Opened MII ( Queue Monitor) and Found that Idoc was received successfully with ID but Message ( "" sucessfully Queued) Status : Queued
    Problem : We are not able to see the material in ME system
    No errors found in NWA logs.
    Kindly suggest any solution.
    Regards
    Shankar

    Make sure you have the plant id in the idoc. Here are the few place in the idoc that you need to add the PlantID. We're using TN01 as our plant.
    <MATMAS03>/ <IDOC>/ <E1MARCM>/ <WERKS>TN01</WERKS>
    <MATMAS03>/ <IDOC>/ <E1MBEWM>/ <BWKEY>TN01</BWKEY>
    <MATMAS03>/ <IDOC>/ <E1MVKEM>/ <DWERK>TN01</DWERK>

  • IDOC not receiving in XI

    Hi -
    Using PI 7.0 and checked all the configurations and read all the related blogs but i don't see the IDOC coming into XI.
    Checked the SM58 on R3 and does not show any errors.
    I checked the WE02 on XI system and shows a status of 60 and 56. Status 60 says "Basic Type MATMAS05 does not exist" which is true because it does not exist on the XI system but exists on the r3 system.
    All the ports on xi and r3 system seem to be fine. i pushed the idoc and shows a status '03' on the r3 side.
    Any tips/ideas to solve the issue are greatly appreciated.
    Thanks,
    Tirumal

    Hi,
    Go to SMQ2 and try to check the Queue Status .
    Did you check this SAP note I referred earlier- 940313
    Also -http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
    GO thru each step ..because it will help you to resolve the problem.
    Hints-
    1) check WE02 and check the status of Idoc in the R/3 system. Is it sent to XI box/port correctly ?check its control record info , in WE19
    2) Did you check Partner Profiles - for outbound parameters -check out this
    3) Check the SM59 entry in SAP system - pointing to XI box.
    4) Check IDX5 transaction in XI box, if eevrything is success in R/3 system
    5) check the Business system in XI - is it pointing to correct R/3 system.
    Hope this helps,
    Regards,
    Moorthy

  • Mail not received by the receiver but successfully sent out

    hello sir
    i m new to java mail and i have installed one free server from in internet ........i have connected to that server through my programme ..........
    i have send mail through my programme .....
    from : [email protected]
    to : [email protected]
    it send it out successfully and showing in the server but it will not been received by the receiver..................can u plz tell me why and what i should do to come out of with this problem so that it will be delivered to the receiver...
    thank you
    gaurav

    I sent like 6 msgs today and all day could not get one freaken message delivered. I have now permenetly turned off iMessage. The service in my opinon is horrible, not reliable and annoying. This is not the first time I couldnt get messages through.
    In general iOS5 has caused me more problems then solutions.

  • IDoc not received in MII

    Hi All, 
    I am using SAP MII 12.1.5 Build 87. 
    I am facing problem with iDoc Listner we have configured iDoc Listner properly in SAP ERP, SAP NW and in SAP MII. 
    We are able to send iDoc from SAP but we are not able to receive same in MII. 
    Port and iDoc Server is giving status connected previously it was working fine in SAP MII 12.1.5 Build 83. 
    Following are the log details for SAP MII Logger as well as SAP NW Log. 
    SAP NW Log: 
    Error processing JRA IDOC message  
    SAP MII Log: 
    Error processing JRA IDOC message  
    Error processing JRA IDOC message [server=xxx, client=xxx]  
    [EXCEPTION]
    java.lang.NullPointerException
    at com.sap.xmii.ejb.JRAListenerBean.onMessage(JRAListenerBean.java:130)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:110)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:77)
    at $Proxy943.onMessage(Unknown Source)
    at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.onMessage(JRAIDocExtension.java:72)
    at com.sap.mw.jco.jra.JRA$ReaderThread.sendDirectToMdb(JRA.java:6641)
    at com.sap.mw.jco.jra.JRA$ReaderThread.sendAsynchRequest(JRA.java:6601)
    at com.sap.mw.jco.jra.JRA$ReaderThread.handleRequest(JRA.java:6771)
    at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:989)
    at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:967)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:142)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2927)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2659)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2478)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2362)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2207)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:259)
    at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:322)
    at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:220)
    at com.sap.mw.jco.jra.JRA$ReaderThread.run(JRA.java:7260)
    at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:255)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Please help me out on this issue.                                         
    Regards,
    Manoj Bilthare
    Edited by: Manoj Bilthare on May 19, 2010 12:57 PM

    Hi Manoj,
    Once you have configured your Listener have you checked pressing the update button and i dont want to ask you which version of NW SP you have installed as you said it was working for you with Build 83, but nevertheless NW SP Level should not be not less than SP3.
    If this doesn't help you,please try  restarting your server again.
    How about the credential editor have you configured this as well?
    Regards,
    Sudhir Kumar
    Edited by: Sudhir Kumar Shambana on May 19, 2010 10:46 AM

  • Idoc not received in receiver , sender shows successful in WE02

    Hello,
    I am sending Vendor from Production to Quality , sender system shows in WE02, idoc status as sucessful. I have checked all ALE settings and they are perfectly fine.
    But in receving system I am not able to receive it. In sender , transaction SM58 is showing error:
    No authorization to send IDocs with message type CREMAS
    Can any one suggest what is the soultion for this scenario?
    Thanks,
    Madhura

    Hello,
    Solution for above problem:
    After executing transcation SM58, screen will show Function Module as IDOC_INBOUND_ASYNCHRONOUS , put cursor on FM IDOC_INBOUND_ASYNCHRONOUS
    , go to EDIT->Execute LUW.
    This will solve the problem of authorization.
    Thanks,
    Madhura

  • Idoc not received in xi

    Hi,
    i using idoc to file  scenario  . idoc are getting posted from sap sucefully i.e  status 03 & no entries are found in sm58  . 
    I am unable to trace the idoc  in xi i.e idx5 , sxmb_moni  .
    I have create port in idx1 for r3 also.
    I am unable trace message in RWB .
    Plz help me to solve this thread
    Thanks,
    Sridhar

    Hi,
    This are the ALE settings,
    These will be the Configurations needed in your R3,
    1. SM 59 - Create an RFC destination for your XI .
    2. We21 -- Create a port for XI
    3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.
    Configuration on XI
    1. IDX2 - Import IDOC metadata.
    For eg : Lets assume the R/3 system and Xi system are QZA and X7A.
    In XI :
    Step 1 : In SALE Tcode :
    a)Create Logical systems for R/3 and XI.
    EG : (QZACLNT100) and (X7ACLNT100).
    b) Assign the logical system of XI to Client.(X7ACLNT100)
    Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab
    Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.
    Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.
    In R/3 :
    Step 1:
    In SALE Tcode :
    a) Create Logical systems for R/3 and XI for
    b) Assign the logical system of R/3 to Client.(QZACLNT100)
    Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.
    Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.
    a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.
    b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.
    c)In Menu Bar EDIT->Generate Partner Profile.
    Click on that and press Execute .
    This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .
    d) Click EDIT->MODEL VIEW->Distribute.
    This shall distribute the model and you can see the distribution mode aslo getting created in XI system.
    This configuration shall surely help u out as it worked out for me.
    Configurations required for IDocs in R/3
    In your XI system, you need to do the following.
    1. Create a RFC destination to your R/3 system
    2. Create a port in IDX1 of your XI system and use the RFC destination in step1.
    3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.
    4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.
    5. Import the business system and you can use it in your configuration scenario.
    Please also refer below links for details.
    Go thru this-
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    SAP R3 ->Legacy system including master data using XI
    Regards,
    Phani

  • Idoc Not received on MII Message Listener

    Hi All,
    I am trying to post Idoc from R/3 to MII Server , but some how I am not getting it
    I have configured Destination, Parter, Partner Profile on the R/3 and Message Listener on MII.
    When I am trying to send Idoc from R/3 using BD10 transaction (Idoc type MATMAS), Idoc Status as 03 in WE02 transaction , but I the MII server does not show up for this.
    Even the Failed Messages is showing no results.
    Am I missing some thing here.
    Any help is appreciated.
    Kind Regards

    I got the issue,
    The problem was Partner was wrongly selected.
    Thanks

Maybe you are looking for