We are noticing this error coming up in our inbound EDI Orders and as far as I understand this issue comes up if the same customer PO has been processed before.

On little digging, I found out that there were few orders that made it partially into Baan successfully (Like one out of five lines) and then apprently it ran into an issue and put the whole order back into Messages to be Received Queue.

Is this a normal behavior? Shouldn't EDI module first check the whole order to make sure it will make it through without error and then process it rather than putting partial order in the system and then putting it in the error queue?

The issue it is causing is that our users then look at the Customer PO number and see that it is already there in Baan (and don't look whether all the lines are there or not) and then delete the order from error batch.

Thanks in advance.

In our system the standard behavior is that order gets imported either fully or it gets completely rejected. Our system doesn't allow partial orders.

Arvind Patil

Thanks Arvind.

Thats what I thought should be the behavior but I have found multiple orders that have this partially imported and still order is present in messages to be received.

I will wait and see if someone else has seen this behavior.

Baan will not load partial orders unless there is the problem with the EDI file or some other process killing the EDI process in between. While checking the EDI file check the second field (bano) of the EDi segments and ensue its unique for entire PO file.

Chandra

Thanks Guys and you confirmed what I thought was the case.

In any case, it kept happening and finally we were able to find out that the EDI job is throwing a duplicate error on tdsls041 and that caused the order import to fail in the middle of an order. As the job failed, the 850S file did not move to store_recv folder and hence when the next time the job ran, we got the error back in Messages To Be Received queue as duplicate.

The duplicate on tdsls041 looks like is caused by a bug in Baan and we are going to open a case with them. We have two 850S-In setups, one that uses the customer PO line number as our sales order line number and one that will let Baan generate its own sales order line numbers. If in a single 850S file, we have orders for each setup, then we will get this error.

Thanks again.