Value Entry already exists Error when posting shipment.

Business Central/NAV User Forum
1

Hi all,

I got some problem when I am trying to post a shipment, after I doing the test, it turns out, two of items got problem.

First Item give me an error message said:“The Value Entry already exists. Identification fields and values: Entry No.=XXX”. And I debug it, in Unit Code 80(Sales-post). When this Item doing posting shipment, it finds the old value entries. However, after the loop, it doesn’t find what it needs, then it loops again. That’s how the error message come from when it trying to do insert value entry again.

Second item has the same problem with first one, this one is more wired, it’s finding a different Item no. entries when doing posting shipment.

Can anybody tell me what might cause the problem Or How I can debug it more specifically? Thank you.

Please forgive my English.

2

is the cu 80 customized ?

can you reconstruct the behavior with a new sales order using the same items ?

3

Thanks for Replying.

No, We didn’t modify Code Unit 80, and I created new sales order for the the same items, and they can’t be shipped. Same error pops out when I was trying to post the shipment.

4

I tried to used the “Revaluation Journal”, filled in the item number and applies to the Latest item ledger record, and modified its unit cost. Then it’s work.(One item’s latest unit cost in item ledger entry has value 20.75, however, this item’s new unit cost is 11.00). I thought this problem caused by modification of unit Cost.

Then I found another item has the same problem, but the latest item ledger record has the same unit cost as its item card. But I tried the same way to this item, change 11.00 to 11.01, and then after I successfully post the Revaluation Journal Line for this item. It worked again.

Now, both of these two items can be post shipment. However, I still wonder ask, what cause the problem, and why change item unit cost helps.

Thank you.

5

This looks weird. Codeunit 80 itself does not insert value entries - it works on another level of abstraction. Does this happen in a localized database?

Could you share a debugger screenshot with this error?

6

Hi Alexander,

This only happens to 2 specified items. Therefore, this does not happen in a localized data base. During the debug, the program actually find the old value entries for these 2 items. However, it can’t be found at first loop(This is weird), then it loops again; That’s why the error pops out, since the first loop has been insert the value entry once.

I will upload the debugger screenshot later.

Thank you.