Skip to Content

IDOC status 03 in R3 but i cant see it in XI

Hi Experts,

R3 side idoc created successfully and 03 status in we02, there were no entries in SM58, SLDCHECK also works fine, but i cant see the idoc in XI. i deleted the meta data and created again but no luck, i created port and rfc destination and partner profile all looks good.

when i send the same idoc from WE19 it went through to XI.

What could be the reason, any one help me out of this.

Thanks,

Praveen.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

6 Answers

  • Best Answer
    avatar image
    Former Member
    Sep 08, 2010 at 10:52 AM

    Hi,

    I think the problem is because of configuration setting. While triggering IDOC from application i think parameters is somewhere problem due to this reason idoc is not passing to XI. While executing idoc from we19 manually we are entering details that is the reason IDOC is passing to XI. Better to check parameters at application side we can fix this problem.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 20, 2010 at 08:23 AM

    Hi all,

    i assume that Harald Boeing is correct with the answer of a missing commit work in the application.

    The application is creating the idoc and make an implicit db-commit if the LUW is finished.

    I assume that in the idoc outbound partner agreement the transfer mode is set to "immediate".

    If the transfer mode is set to "collect idocs", then this problem will not occur.

    The ALE framework makes a function call of the rfc api

    like

    call function "IDOC_INBOUND_ASYNCHRONOUS" in background task

    If the commit work is missing, no rfc call is created by the RFC-layer, IDoc will get status 3 and

    no idoc is sent to xi (no systemlog or warning).

    There are two rfc-ports available:

    - trfc => entry in transaction SM58 is created

    - qrfc => entry in transaction SMQ1 is created

    If the idoc is cloned and resent with the idoc test tool (TA WE19), then the rfc call is done

    and also the commit work is done.

    The customers can check if the rfc-call in SM58 is made or not with the following step:

    - in transaction SMQS the maximum amounts of rfc-connections for the used rfc-destination

    can be defined

    - if the max. amount of rfc-connections is set to 0 (zero) than no SM58/SMQ1 transaction

    are processed

    - idoc must be recreated with the application (not with WE19 tool)

    - check if the unprocessed rfc-call-entry is created in SM58 (for trfc-port)

    - if not then the application must be checked why the explicit commit work is not called

    please note that an implicit/explicit database-commit is not enough

    in case it is an SAP application it must be checked if a note for that problem exists

    - please do not forget to reset the max amount rfc-connections in TA SMQS

    to a value higher than 0 after this test

    Kind regards.

    Andreas

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 08, 2010 at 11:05 AM

    Check the control record of Idoc sent from ECC using WE19.

    Match that Control Data record with other IDoc, if there is any mismatch in control records, use Control Data record as per used in successful IDoc.

    Make changes accordingly.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 08, 2010 at 11:21 AM

    The question might be how you're creating your IDocs. If you're using some custom program/coding, then the issue you experience might be due to a missing [commit work|http://help.sap.com/abapdocu_70/en/ABAPCOMMIT.htm]. I've seen this before and the reason was quite simple: The IDoc framework triggered the sending of the IDoc via an update function, which didn't run due to the missing commit. This was quite an interesting investigation, because on SAP sender side everything looked perfect (i.e. IDoc in status 03, no corresponding entry in the outbound RFC queue and thus status could be converted to 12 signaling that everything is really fine). Maybe that's also the cause of your problem...

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 08, 2010 at 03:36 PM

    Hi,

    please check in the R3 sistem the tcode SM58, you can see the idoc in status 03 butmaybe there is a configuration problem,user,etc that only can see it in this transaction code. also you can use Tcode BD87 to monitor IDocs to check diferents kind of errors

    lets us know

    Rodrigo P-

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 22, 2010 at 06:27 AM

    Thanks for the replies, the problem is COMMIT WORK is missing in custom program, Thanks Harald Boeing

    Add comment
    10|10000 characters needed characters exceeded