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

Problem in file2IDOC scenario

Dear all,

I am using File adapter on the receiver side and IDOC adapter on the sender side.

I am using delete option for processing mode.

The file is getting deleted in the source directory but i don't find the IDOC at all in the IDX5 (XI).

I have even verified WE05 but i didn't find any inbound iDOC.

I have checked the runtime workbench.

Both the communication channels are error free.

In such scenarios how can i find why the IDOC in not pushed to SAP.

How to trace the iDOC?

Thanks.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

7 Answers

  • Best Answer
    Posted on Nov 29, 2007 at 08:04 AM

    Hi Durga,

    While doing FILE to IDOC scenario make sure all the settings are done correctly.

    On XI server u have to create

    1.RFC destination in sm59 pointing towards Rx(receiver syst) .

    2.call transaction IDX1 for creating port & enter RFC destination created above.

    3.Call transaction IDX2 for loading IDOC metadata.

    On target system:

    1. Maintain partner profile in transaction we20.Make sure u have entered

    correct IDOC type,MessageType,Processcode.

    And also tick chek box "Trigger Immediately" while configuring partner profile.

    Regards,

    Vinod.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Durga,

      A serious error has occurred while the QIN scheduler is running.Double-clicking on the status will display the corresponding error text. Further analyses of the syslog (SM21) or Development Trace (dev_w, dev_rfc and dev_rd) may be required to identify the error.

      and also let me know what is your exact scenario.

      A queue entry with status SYSFAIL can have two causes

      1. The process cannot be processed for technical reasons (eg. Program dumpt or a system (system Mapping or receiver's system not accessible).

      2. The Queue processing should be stopped, because the message cannot be processed by a configuration mistake

      Please let me know if you have any issues.

      Thanks,

      Jag

      Message was edited by:

      jag

  • author's profile photo Former Member
    Former Member
    Posted on Nov 29, 2007 at 08:46 AM

    Hello Durga......

    For Tracing Idoc.....

    ALE Error Messages:

    02 - Error passing data to port

    04 - Error within control information on EDI subsystem

    05 - Error during translation

    25 - Processing despite syntax errors (outbound)

    29 - Error in ALE service

    32 - Resubmit edited intermediate document (DO NOT USE)

    Syntax Error Messages:

    26 - Error during syntax check of IDoc (outbound)Inbound ALE Status Codes

    IDoc Processed Successfully:

    50 - IDoc added

    53 - Successful posting

    IDoc ready for processing:

    64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.

    Errors in IDoc Processing:

    51 - Error - application document not posted

    56 - IDoc with errors added (You should never see this error code)

    60 - Error during syntax check of IDoc (inbound)

    61 - Processing despite syntax error (inbound)

    63 - Error passing IDoc to application

    65 - Error in ALE service - indicates partner profiles are incorrect

    69 - IDoc was edited

    Testing:

    Log in to Adaptor Monitor and check for the file adaptor. The status of the adaptor should be green and working.

    Check the ftp connection, it should connect to destination folder without any error.

    Log in to sender system, go to transaction WE19 (test tool to generate IDoc), generate Idoc of the required message type.

    Log in to Xi system and execute transaction SXMB_MONI and check for the XML messages. Use your source and destination system to filter messages, it should have chequered flag.

    Check the destination directory, it should have file with the name specified along with the time stamp. Check the file, it should have data for all segments.

    Reward Points If is Useful...

    Thanks,

    Satya Kumar.....

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 29, 2007 at 07:26 AM

    Hi,

    Use file Adapter on sender side and Idoc Adapter on receiver side.Check runtime workbench for monitoring adapter..U will get to know better about the problem there..Can u check there and let me know.

    Thanks,

    Anoop

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 29, 2007 at 07:28 AM

    Hi Durga,

    just cross check it with my posting on wiki

    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC&

    and check this

    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

    Sachin

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 29, 2007 at 07:28 AM

    hi durga,

    use transaction code sm58 on your r/3 to track the IDoc

    regards

    Ramesh P

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 29, 2007 at 07:28 AM

    Hi venkat,

    can u please be clear in subject line u have specified that u are using file as a sender and in the description u have mentioned that file adapter is the reciever.

    thanks

    Naveen

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 29, 2007 at 08:25 AM

    Hi,

    Just go through the below link

    <a href="/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi File-to-IDOC Scenario in XI</a>

    Regards,

    Sarvesh

    Add a comment
    10|10000 characters needed characters exceeded

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.