Mgroeneveld
Well Known Member
Dear list members,
Luckily i'm not the only consultant suffering with the commit failure error. So hopefully someone can help me with the following:
My customer frequently receives a commit failure during different inventory transactions (inventory adjust/transfer, purchase receipt, ship confirmation). In order to trace this, we've activated the F41021WF for this purpose only. We cannot rollback because these errors are often reported days after the incident occurred.
The F41021WF only shows commit failures that occurred during ship confirmation. Other commit failures have been reported also.
According to Edwards, the most likely causes are:
1.) weighted average cost in conjunction with negative QOH=> Weighted average cost is however deactivated for our customer.
2.) additional lines during ship confirm=> this however only results in a commit failure as soon as adding lines (freight cost) results in a lock of the order. This is not the case for our customer.
3.) a conflict with the data dictionary => this can't be the cause because an order can sometimes not be shipped (commit failure) and after changing the status code, it can be shipped without changing data.
Does anyone have other suggestions on possible causes ? I want to write down all possible causes and come to the most likely conclusion.
Thanks for your input.
Regards,
Martijn Groeneveld
Oneworld XE, Upd 1, Sp20
Luckily i'm not the only consultant suffering with the commit failure error. So hopefully someone can help me with the following:
My customer frequently receives a commit failure during different inventory transactions (inventory adjust/transfer, purchase receipt, ship confirmation). In order to trace this, we've activated the F41021WF for this purpose only. We cannot rollback because these errors are often reported days after the incident occurred.
The F41021WF only shows commit failures that occurred during ship confirmation. Other commit failures have been reported also.
According to Edwards, the most likely causes are:
1.) weighted average cost in conjunction with negative QOH=> Weighted average cost is however deactivated for our customer.
2.) additional lines during ship confirm=> this however only results in a commit failure as soon as adding lines (freight cost) results in a lock of the order. This is not the case for our customer.
3.) a conflict with the data dictionary => this can't be the cause because an order can sometimes not be shipped (commit failure) and after changing the status code, it can be shipped without changing data.
Does anyone have other suggestions on possible causes ? I want to write down all possible causes and come to the most likely conclusion.
Thanks for your input.
Regards,
Martijn Groeneveld
Oneworld XE, Upd 1, Sp20