getting 2 idocs for one file sent in PI

[Former Member]

Hi.

i have an issue in which 2 idocs have been posted although only one file is sent in PI in File to idoc scenario.

this 2 idocs posted successfully got posted and hence showing 2 documents with different number while reference number,posting date,document date remains same.

how to find what could be the reason and how to fix,

all the rest company code,customer for the AR invoice remains same.

Also,do ineed to check any mapping in PI but it has happened for the first time only for one customer in a span of 5 months.

plese help.

thanks

[Former Member]

SXMB_MONI in this case is your friend - run the transaction and see what the cause of the transmission of the second IDOC.

One possibility is that the file found itself back in the import directory, and was read twice.

[Former Member]

thnks for the reply.

But i have checked in SXMB_moni,the file coming from the legacy is just one,but idocs have been created twice.

Well,this is file to idoc and its been marked as 0 to unbounded,hence many idocs can come.

is it because all the data are same for that reference number,there is no validation of data on sap side or PI side for check of duplicate invoices.

will there be any flaws in mapping or context handling.

i am totally clueless where to start my investigation..

please reply.

[Former Member]

HI Nishi,

Investigate the data in your file , is it meant to create two idocs or one. With the data in the moni , test your mapping to

see how many IDOC node is getting created for the same file.If its two there also then work on fixing/validating the

mapping part.

Regards,

Srinivas

[Former Member]

Hi Nishi,

Do you have 2 Server nodes maintained for PI??

If yes this may be the reason for your same file getting read twice by PI itself and may be the reason for it posting 2 IDOCS instead of one at R/3.

Out of the 2 IDOCS that will be posted for the same file one IDOC will be processed and the other one will be in error. Is this noticed in your case??

If yes then the solution would be to add the below parameter in the Advance tab of File Adapter

"clusterSyncMode - This parameter should be used with Sender File adapter only. Set the value to u201Clocku201D."

Hope this helps.

Cheers

Dhwani