cancel
Showing results for 
Search instead for 
Did you mean: 

Effect of disallowing incompletion on EDI orders

0 Kudos

Hi all,

We do not allow incomplete sales orders, tvak-diafe is set to 'X'.

Now we want to start using the customer's expected price functionality, with price condition types EDI1/2, for EDI orders. We added cepok to the incompletion log. It works well, an EDI order coming in with a different expected price becomes incomplete for cepok and shows in V.25. Happy.

What I do not understand is how the order is allowed to be created with tvak-diafe set to 'X'? I tried and can not create a sales order manually with a bad EDI1 condition, and I expected that because of the diafe setting, but how is it that an EDI order can be created incomplete with diafe set to 'X' ? Is this normal behaviour?

Thanks, Rad.

View Entire Topic
0 Kudos

The cepok field in the incompletion log is set to warning, this means that a warning comes during manual order entry. The status is 04, which means general incompletion, no delivery possible, etc.

Then, at order header level, there is this setting:

During manual order entry the effect of this setting is that I can not save the order when incomplete. But EDI orders are saved even when incomplete for expected price (cepok). This is what surprises me.

When I remove the tick here, I can save the manually entered order incomplete.

It surprises me that the setting does not have the same effect on EDI orders and manually entered orders.