Hi Guys
I have a strange issue when users post Transfer order the Error “select a dimension value code for the dimension code Cost Center for g/l account 60104”.Which is (Direct cost applied for Raw Material Account).Pops up but both dimension codes required for the g/l account are filled correctly and i even checked the Dimension set id it is inserted to the transfer header and line table correctly, and tried to debug it and i landed at the following code in Codeunit 11 Gen. Jnl.-Check Line
IF NOT DimMgt.CheckDimValuePosting(TableID,No,“Dimension Set ID”) THEN
IF “Line No.” <> 0 THEN
ERROR(
Text012,
TABLECAPTION,“Journal Template Name”,“Journal Batch Name”,“Line No.”,
DimMgt.GetDimValuePostingErr)
ELSE
ERROR(DimMgt.GetDimValuePostingErr);//Debugger traced it here
Dynamics NAV Version 2015
Thanks in advance!
If you have Global dimension 1 code or Global dimension 2 code set as code mandatory in G/L account then you get this error. The error is very misleading but that’s what it is. If you go to your G/L account 60104—>dimensions you will be having the Global dimension1 or global dimension 2 set as code mandatory.
Yes it is Global dimension 1 code or Global dimension 2 on general ledger setup and also given as mandatory on that specific GL account, but it was working fine until now, there is nothing changed on the setup.It is strange why it surfaced right now.
Because when it’s trying to post the Transfer order the posting routine checks for already posted ledger entries/Value entries for this transaction when it hits account 60104. I am positive in Value entry or Item ledger entry there is a entry that belongs to account 60104 that is missing the Global dimension 1 code or Global dimension 2 code. You will have to navigate on the document nos. of Value entry and when you navigate if the entry has a transaction posted to this G/L account then for that Value entry you will be missing the global dimension1 or global dimension 2 code. Once you insert the global dimension then you should be able to post. I also had the same issue and it took me a while to debug this and figure out the entry from Value entry that was missing Global dimension value.