IDOC not reaching destination system

Hello,
  I am trying to send DOCMAS type IDOC from one SAP sys to another SAP sys.The IDOC has the status 03 (The IDoc was sent to an SAP system or an external program via a transactional RFC) but i dont see the IDOC in the target sys.
Please let me know what could have gone wrong.
Thanks,
Rakesh.

Hello Rakesh More ,
First let us know how you corrected the previous error???. What was wrong?
Then talk about the  next issue.
If you maintain properly the Inbound IDOC partner profile this error should not come. Make sure you  have the below things set-up properly:-
1) In the inbound IDOC in the destination system there should be a partner receiver in the IDOC control data. Make sure you have maintained the partner profile for that partner and for the partner type as well.
2) For the partner make sure you have maintained the proper inbound mesaage type and process code properly.
Thanks,
Greetson
Edited by: Greetson Shunmugasundaram on Aug 1, 2011 9:47 PM

Similar Messages

  • MATMAS01 IDOC not reaching to SAP XI via report program.

    Dear Experts,
    WE are facing small challenge.
    I searched on SDN on scenarios: IDOC not reaching to SAP XI. But could not find exact solution t oour scenario.
    Problem:
    MATMAS01 IDOC is not reaching to SAP XI via report program and is in status of 03 on SAP system. And there are not entries under SM58.
    Under SAP XI system IDOC entry is not reflecting under IDX5 transaction, I tried to delete meta data of MATMAS01 thru IDX1 and uploaded again but still IDOC is not reaching to SAP XI.
    The strange is that MATMS01 IDOC is reaching to XI via WE19 test tool. So PORT and RFC destination settings betweeen R3 and XI is also correct.
    What could be the wrong ?
    Thanks
    Divyesh

    When sending Idoc from R/3,
    Settings at R/3
    create one port at WE21,
    Create Partner Profile for Outbound Message type in WE20.
    settings at XI
    Create one port in IDX1
    Import Matadata in IDX2.
    Create complete scenario in ESR for Idoc sender, also import IDoc in Imported Objects.
    Check these settings & send test idoc using WE19.

  • E-mailed photos not reaching destination

    Hi,
    E-mailed photos not reaching destination
    . Can you help?

    DCAINTLRE
    If you have Premiere Elements, then your question relates to Premiere Elements via the Elements Organizer that comes with it.
    And, as we know, Photo Email is an Elements Organizer feature found under the Elements Organizer Share/Photo Mail.
    What version of Premiere Elements do you have and on what computer operating system is it running?
    How far are you getting in the Photo Mail feature:
    a. Do you get your created photo mail and see the email with its active Send button ready for you to hit the Send button?
    b. If so, after you press the Send button, does the email appear to have been sent...even if you do not see a specific message saying
    message sent? To verify that the message was sent, in the Elements Organizer Find Menu, go to By History/Emailed to to confirm
    the sending.
    Have you checked with the recipients of your Photo Mail to make sure that your sending is not ending up in the recipient's email junk
    folder? Have you troubleshooted by sending a Photo Mail to yourself?
    What have you set up as Email Client in the Elements Organizer preferences?
    Please review and consider and then let us know the outcome.
    Thank you.
    ATR

  • Sent messages not reaching destination

    Mail sent through .mac account does not reach destination, but everything looks completely normal. Messages sent using mail but from another mail account reach their destinations just fine. I still have tons of space on my .mac mail account and absolutely no error messages are appearing. Most grateful if anyone has a clue about what's going on.
    Thanks, SP

    hi jim, thanks for the reply.
    yes, i tried sending mail to myself, also at a yahoo acct... it seems to be sent (doesn't bounce) but never reaches destination. The only way i can make it work is not to use mac.com as my outgoing server (i have to use the server of my local provider) and not to activate ssl sockets in mail preferences... naturally no pw check etc.
    the annoying thing is that Mail doesn't tell me when it's not working, it saves the messages as sent but doesn't deliver them.
    any ideas?
    thanks again, sp

  • Idoc Not reaching PI even with 03 status

    Hi everybody
    There are many posts with similar question, but none of them could help me.
    I am trying to post an IDOC from one SAP system 3.1 to SAP 6.0 through PI.
    I added FIDCC1 to to my partner profile in BD64.
    I am creating a invoice and clearing it through f-30 and using the details from the invoice i am trying to trigger an idoc through a program.
    Three idocs are getting triggered
    1.when i create invoice(f-22)-automatically
    2.when I clear invoice (f-30)-automatically
    3.When I execute my program
    The first two IDOCS are reaching 6.0, but my third IDOC is not reaching. All have same port details and partner profile details.
    *All have 03 status in we02 in 3.1*. I am not able to understand why those two are reaching and why the third is not reaching.
    None of them are stuck in any queues.
    My actual requirement is only the third IDOC to reach 6.0 and I do not even want the first two IDOCs to reach 6.0.
    Pls help!
    Thank you
    Donny
    Edited by: Donnesh on Dec 27, 2011 1:14 AM

    Hi Friends,
    Thanks for the suggestions.
    I have checked with all the above provided suggestions.
    But as I have clearly mentioned in the problem that other idocs are reaching well in XI from R3 using the same Port, Partner Profile and RFC.
    The error is occuring only with only one idoc in which they have made certain changes (added new segments). I have imported the idoc in Design again and then did the mapping again with the changed idoc.
    Before the changes I could receive the Idoc successfully in XI system. I don no what happened after the changes.
    If it would have been an authorization problem then I guess the other idocs would not have reached the XI system as well.
    I guess the problem is somewhere else..
    Thanks in advance.

  • Idocs not reaching SAP R3 from XI

    Hi All,
    I have a File to IDOC scenario, in which i need to process a text file of size 1 Mega Byte. The file from Leagacy reached XI and this has to create 12000 idocs in target R3 system. I can see the idocs(12000) in the IDOC Adapter but these idocs have not reached R3.
    In SM58 I see an entry for this with the status "Transaction Executing". This entry is pending since 3 days. This always results in "Time exceeded out", and Iam manually executing it with F6 but still the status shows "Transaction executing".
    There are no entries in SMQ1 & SMQ2
    I want to push these idocs to R3.
    Any suggestions on this will be helpful
    Regards,
    Santosh

    Santosh,
    Use IDOC packaging as shown in Michal's blog
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    Also, try increasing time out values
    /people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
    Regards,
    Jai Shankar

  • IDOCS not reaching XI (IDEX-GE Content)

    If I send IDOCS from I/SU to XI no IDOC is reaching XI.
    IDX5 doesn't show any incoming IDOC. There is no error neither in XI nor in the log viewer of Visual Administrator.
    The Sender system says in WE02: Datatransfer to port ok.
    I checked the port and its RFC: The correct RFC (the one to XI) is set and RFC is working (sm59: test connection is ok, Remote Login from I/SU to XI is working).
    IDOCS from a second backend are visible in IDX5. This backend is configured like the first backend (same RFC).
    Did anyone have a solution?
    Thanks
    Ralf

    Hi,
    These are the complete steps for IDoc communication, check if you have missed any one...
    SAP XI
    1) RFC Destination (SM59)
         a) Choose create.
         b) Specify the name of the RFC destination
         c) Select connection type as 3 and save
         d) In the technical settings tab enter the details SAP SID/URL and system number#.
         e) Enter the Gateway host as same details above SID/URL.
         f) Gateway service is 3300+system number#.
         g) In the Logon /Security tab, enter the client user & Password details of Destination system.
         h) Test the connection and remote logon.
    2) Create Port (IDX1)
         a) Select create new button
         b) Enter the port name as SAP+SID (The starting char should be SAP)
         c) Enter the destination client.
         d) Enter the RFC Destination created in SAP R/3 towards other system.
         e) Save
    3) Load Meta Data for IDOC (IDX2) a) Create new
         b) IDOC Message Type
         c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
         a) Choose create.
         b) Specify the name of the RFC destination
         c) Select connection type as 3 and save
         d) In the technical settings tab enter the details SAP SID/URL and system number#.
         e) Enter the Gateway host as same details above SID/URL.
         f) Gateway service is 3300+system number#.
         g) In the Logon /Security tab, enter the client user & Password details of Destination system.
         h) Test the connection and remote logon.
    2) Create Port (We21)
         a) First Select Transactional RFC and then click create button
         b) Enter the destination port name as SAP+SID (The starting char should be SAP)
         c) Enter the destination client.
         d) Enter the RFC Destination created in SAP R/3 towards other system.
         e) Save
    3) Create Partner Profile (WE20)
         a) Create New
         b) Create the Partner no. name as same the logical system name of the destination system.
         c) Select Partner type LS
         d) Enter details for Type: US/USER, Agent, and Lang.
         e) Click on the + button to select the message type.
         f) Select Partner no. and LS which ever create above.
         g) Select Message type     
         h) Select Process code related to the Message type.
         I) save.
    In SLD 
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system
    Name.
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    Check these steps
    Regards
    Vikas

  • Idocs not reaching new PI server

    Hi Experts,
                        We have cloned SAP-PI 7.0 server and SAP-ISU server. Now idocs from from SAP-ISU is not reaching SAPI-PI at all.
    Could you pls suggest how to anlayse and solve this problem?
    Regards
    Anupam

    Hi,
    Also Could you please try refreshing CACHE and also check the configuration of Integration server in sxmb_adm.please refer this similar threads below for reference.
    Link: [https://forums.sme.sap.com/message.jspa?messageID=7947041]
    Link: [https://forums.sdn.sap.com/thread.jspa?messageID=374227#374227]
    Also check this [https://forums.sdn.sap.com/thread.jspa?threadID=1236817]
    Regards,
    Venkata S Pagolu

  • Email is 'Sent' but does not reach destination - Please Help

    Hi Guys,
    Need some help with this. I have recently discovered that all emails I have been sending from Mail over the last month or so have not reached their destinations.
    I get no error messages when sending from Mail - the email is dispatched as usual, the sound is heard and mail deposited in my 'Sent' folder. I have tested this by emailing myself with no joy.
    Interestingly, the 'webmail' facility via the internet works OK and emails are all received. So looks like the problem lies at my end.
    Have checked the settings for the outgoing mail server (my current Portugal ISP) and they seem OK. I do not recall having touched anything here.
    The mail account is one of those free POP mail accounts with my old UK ISP which I have continued to use successfully out here since august...that is until now!
    I am using Port 25 without SSL and no authentication - everything as before. Have already tried changing the port to those mentioned in similar threads but nothing gives.
    Any ideas would be greatly appreciated!
    Many thanks
    1.33GHz Powerbook G4   Mac OS X (10.4.2)  
    1.33GHz Powerbook G4   Mac OS X (10.4.2)  

    Hi Paulo.
    If Mail puts the message in the Sent mailbox, that means Mail has got confirmation from the SMTP server that the message will be delivered. Whether the SMTP server actually does what it promised, or the message is filtered out by the recipient’s incoming server for some reason, is another story that Mail can do nothing about.
    Interestingly, the 'webmail' facility via the internet works OK and
    emails are all received. So looks like the problem lies at my end.
    Sending messages via webmail is not the same as sending them via SMTP. If the problem is at your end, it’s at the server-side part of your end; more specifically, at the SMTP server part...

  • Outlook 2013 sent email not reaching destination

    This is a first for me!
    Since early yesterday morning any email sent from Outlook 2013 (pop3) does not reach its destination that includes btinternet addresses.
    Outlook receive works on messages coming from other clients.
    Outlook send appears to work as messages go from Outbox to Sent Mail.
    Test Message in Outlook settings appears to work but no Outlook test message received.
    Email sent from the web client works.
    No PC settings have changed.
    Outlook settings are correct (mail.btinternet.com, etc).
    First line Helpdesk can’t see anything wrong.
    I have the feeling that something has changed in the background with servers or the move.
    Can this be pointed towards second line support?
    Solved!
    Go to Solution.

    Can you send and receive with BTMail via webmail?
    If everything on your Outlook account is otherwise working and nothing has changed at your end I would leave it for a day or two to see if it clears itself.  
    The settings for BTMail are here if you want to re-check them.
    http://bt.custhelp.com/app/answers/detail/a_id/44917/kw/bt%20mail/c/346,6588,6591

  • Mail sent does not reach destination

    I am able to send mail from smtp.mac.com, or at least that's what it looks like, but the mail does not reach its destination. I tested it on myself. I have two accounts, .mac and another one. I sent mail from .mac to my other account and it didn't reach.
    The problem started a few hours back. I got the typical "cannot send mail from this server ...." error message and I changed servers. Usually, it used to work with this change, but this time around it didn't. I deleted all servers that I didn't need, checked the connection doctor - it's connecting fine to the Internet, the activity Viewer shows the mail being sent. But, the mail does not reach where it is sent.
    I don't have problems with my other mail account - just .mac.com.
    Can anybody help?
    PB G4   Mac OS X (10.4.7)  

    A message is either sent or not sent and if not successfully sent for whatever reason, the message will remain in the Outbox mailbox and will not be moved to the account's Sent mailbox. If a sent message is available in the account's Sent mailbox, this indicates the message was successfully sent.
    A successfully sent message is either accepted or rejected by the recipient's incoming mail server and if not accepted by the recipient's incoming mail server for whatever reason, you will receive a return email error message from the recipient's incoming mail server indicating why the message was not accepted.
    Sent messages are usually received almost instantly for the most part but not always. Successfully sent messages do not take a straight line from the SMTP server used for the account to the recipient's incoming mail server. There can be delays along the way or a temporary problem with the recipient's incoming mail server.

  • IDOC to xi  problem  IDOC not reaching xi

    Dear all,
    this is a case of IDOC scenario in development server.
    we are sending a IDOC form R/3 system to xi system,and when we are checking it with Tcode sm58 ,it is coming as status 12 .
    but when we try ti view this IDOC in xi system with Tcode IDX5 nothing is coming.   we check every thing like port configuration in IDX1 and IDX 2.
    we checked the code also which is used to trigger Idoc from R/3 System. every thing is fine thete also.
    please give some input regarding this problem.
    thanks and regards,
    Navneet Sumit

    HI,
    Check whether u have done the proper configuration at the R3 end.
    ALE configuration for pushing idocs from SAP to XI
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    Thnx
    Chirag

  • IDOCs sent from sender R/3 system do not reach XI system

    Hello everyone,
    We have a IDOC to JDBC scenario in place.
    Sender R/3 system is R1A. XI system is XDA.
    IDOCs are successfully sent out of R1A:
    On R1A.(R/3)
    1. WE05 shows data passed to Port OK
    2. SM58 does not show the IDOC to be stuck in TRFC queue
    On XDA (XI)
    1. Port has been mentioned in IDX1
    2. IDOC Adapter monitoring (IDX5) does not show any message from R1A.
    3. SXMB_MONI does not show any message from R1A.
    The above scenario is for acceptance box.
    On Dev boxes (RDD and XDD)the same scenario works OK.
    Could we be missing something in the ALE configuration?
    If there was something wrong in the Integration Scenario, then atleast the IDOCs should have reached XDA right?
    Please assist.
    Ashwin Bhat

    The option to Transfer IDOCS Immediately was not working. All IDOCs were later sent Batchwise successfully.
    The Basis team is investigating why IDOCs are not transferred immediately.
    Thanks for all your help Guys.
    Regards,
    Ashwin

  • IDOC -- File:(R/3-- XI) : Idocs not reaching XI. Where to check for error

    Hi,
    I have completed the config for IDOC to XI (R/3-->XI) scenario based on various weblogs available on Sdn.
    For testing, I am using we19 to trigger the outbound idoc from R/3. But when I look in IDX5 in XI or message monitor, I do not see any message or IDOC there. Even SXMB_MONI in XI does not have any message.
    What could be the potential issue for this behaviour. Is there a way where I could debug or any steps that could tell me where to look for the error.
    So far only odd behaviour I have observed is:
    When in WE19 I trigger the IDOC for outbound processing, XI login screen pops up, where I need to enter password. Once I click enter the screen disappears and the message, IDOC sucessfully sent to external system/Port appears.
    Appreciate your help.
    Thanks
    Shirin

    Hi,
    I checked SM58 and teher indeed are errors saying
    "Name or Password is incorrect (repeat logon) "
    So which connection is having incorrect password in SM59?
    I checked and I have a working RFC connection  (TYpe 3) in SM59 for XI.
    Just to add TCP/IP connection(Type T) has 2 connections not working. They are LCRSAPRFC and SAPSLDAPI.
    So what should be my next step in correcting this error as I am not sure which RFC connection user-id is responsible for SM58 errors.
    Any feedback is welcome.
    Thanks
    Shirin

  • IDOC not reaching XI from SAP

    Hi,
    I am trying to fire IDOC (DEBMAS) from SAP to XI. The basic Idoc has been exxtended to add some new segments. The required configuration has been done on SAP and XI side(partner profile on SAP and IDX1/IDX2 on XI).
    However whenever I fire this idoc from SAP, it shows that Idoc has been triggered but am not able to see the same in SXMB_MONI in XI.
    Please let me know if you have any clues

    Hi Anand,
    The monitoring in SXMB_MONI can only inform u about integration engine.
    SM58 errors occur if a RFC destination does not work.
    Also what is the Status Text message you see in the SM58 ?
    Anyways have a look at this Blog....
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    Regards,
    Abhy
    Message was edited by: Abhy Thomas

Maybe you are looking for