Skip to Content
author's profile photo Former Member
Former Member

Inbound IDOC not getting posted in database

Hello All,

I have a similar problem below:

http://www.sapfans.com/forums/viewtopic.php?t=59840&highlight=inboundaleconfiguration

Currently, I have distributed exchange rates from my sending system to my receiving system. When I check on the IDOC status, it is set to status 03 (Data passed to port OK) but on the receiving system, I am unable to find any IDOCs received.

I have checked more than 3 times the ALE configuration and I'm really stuck now.

I have already looked in to tRFC Queue (SM58) but I don't know how to trace the errors. The message I'm getting in SM58 is "Client M88 is not available. Please choose an existing client." However, I tested the connection from the sending system to the receiving system and it works OK.

I'd appreciate any help.

Regards,

Kristine

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jan 13, 2005 at 08:33 AM

    Hello Kristine,

    I'm "afraid" to make any suggestions if you say you have checked the ALE configuration more than 3 times....

    However the message you are getting suggests the client specified for the partner system is not correct. If you double click on the Target system in the overview of transaction SM58 you will go into the RFC destination; is the client specified there really ok?

    If all is ok you might you in the debug mode: Copy the transaction id from the overview and goto SE38. Put a break-point in program RSARFCSE (if you don't put a break-point before you execute you will have a hard job to get there because it is a system program). Then start the program using the transaction id and set 'Forced'.

    Regards,

    John.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Kristine,

      Take a deep breath and relax for some time.

      start looking into the ALE config again.

      FOllow these steps once again.

      1.)Go to SM59 transaction, execute ur rfc destination for test connection. Also check for remote logon. if it is successful,ok, leave it.

      2.) Go to partner profile WE20 transaction.

      Click ur partner profile and check for outbound paramaters.

      click on message type.

      u can find port no like 'A000013'.Also the partner profile can be configured to send idocs immediatley.

      3.)Go to port definition, we21 check for the port which u find in the previous step, u can see the rfc destination.

      if this is same as the one in first step, there wont be any problem.

      I hope u can find some defect in these steps, because if the rfc destination is not correct, when u try to distribute the ale model, it should have given u the error.

      pls check and revert back for any concerns.

      Regards,

      Senthil

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.