Problem in file2IDOC scenario

[Former Member]

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.

[former_member537867 · Accepted solution]

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.

[Former Member · Accepted solution]

Hi

The see the XML msg in sxmb_mini with green flag (scheduled).

The Comm channel is working fine.

What could be the reason for this green flag.

[former_member214364 · Accepted solution]

Hi Durga,

Check whether Queues are running or not in SMQ2 Tcode.

[Former Member · Accepted solution]

Hi

I am getting the status of the QUEUE as

SYSFAIL.

Can i manually push the msg in another queue.

or is there a work around for this type of scenarios?

Thank you.

[former_member214364 · Accepted solution]

Hi Durga,

if you double click on Sysfail error you can see long text .from that we can find where it went wrong.

can you also check space using DB02 Tcode.

[Former Member · Accepted solution]

HI

When i double click ion the sysfail error i get a pop up "XI restart in qRFC not allowed"

I am not sure on how to leverage DB02 features for queues?

Thanks

[former_member214364 · Accepted solution]

Run RSQIWKEX report by selecting option "No running" Queues.

[Former Member · Accepted solution]

Thank you very much.

Scenario is working fine.

But i would like to know what happened exactly by executing this report.

[Former Member · Accepted solution]

First time it executed fine after

Running RSQIWKEX report by selecting option "No running" Queues.

But now again i am facing the same problem.

I have run the report RSQIWKEX also.

Still in SMQ2, the status of the queue is SYSFAIL.

How to solve such problems????

[former_member214364 · Accepted solution]

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

[Former Member]

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.....

[Former Member]

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

[Former Member]

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

[Former Member]

Sorry,

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

[Former Member]

hi durga,

Check this link for troubleshooting

/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process

regards

Ramesh P

[prateek]

What is the status of message in transaction sxmb_moni at XI? If its in error, then wht is the error? If it is successful, then u must receive message in idx5 at XI.

Regards,

Prateek

[Former Member]

hi durga,

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

regards

Ramesh P

[former_member184619]

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

[Former Member]

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