cancel
Showing results for 
Search instead for 
Did you mean: 

error in file to idoc scenario

Former Member
0 Kudos

HI all,

In file to idoc scenario at target side i am getting idoc with added some error

status and then hoe to get sucess status?

thanks in advance

gupt

Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member
0 Kudos

Dear All,

For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.

For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.

I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.

Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

Former Member
0 Kudos

Hi friends,

here is new document for IDOC TO FILE scenario..

http://jskcomput.blogspot.com/2013/08/idoc-to-file-scenario.html

Former Member
0 Kudos

Resolve the error.

You can check the various config data to find the error

former_member184619
Active Contributor
0 Kudos

Hi Gupta,

What error msg. are you getting. check the below link for error msg. and how to change idoc status.

http://www.erpgenie.com/sap/sapedi/idoc_statuses.htm

Regards,

Sachin

Former Member
0 Kudos

Hi Gupta,

what is error msg ru getting

pls do chk this link it is worth

http://www.sappress.com/product.cfm?account=&product=H1935

Thanx

Sampath

Former Member
0 Kudos

hi,

Troubleshooting File-to-IDOC Scenario in XI

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

also see the discussion

Thanks,

Vijaya.

Former Member
0 Kudos

Hi,

What Error status that you are getting on IDCO side.

Probably its getting schedueld for background job and later on have changed the successful status.

Thanks

swarup