"Select a Dimension Value Code for the Dimension Code" error message when you try to post an automatic inventory adjustment with the G/L integration in Microsoft Dynamics NAV

This article applies to Microsoft Dynamics NAV for all regions.

When you try to post an inventory journal that uses the G/L integration in Microsoft Dynamics NAV, you receive the following error message:

Select a Dimension Value Code for the Dimension Code PROJECT for G/L Account G/L Account.


This problem occurs if the following conditions are true:

  • In Inventory Setup, the Automatic Cost Posting is set to True and the Automatic Cost Adjustment is set to Always.

  • In Inventory Posting Setup, the Dimension Value Posting is set to Code Mandatory for the inventory account.


This problem occurs in the following products:

  • Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

  • Microsoft Dynamics NAV 2009 R2

  • Microsoft Dynamics NAV 2009

  • Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)

  • Microsoft Dynamics NAV 5.0

A supported hotfix is now available from Microsoft. However, it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics NAV 2009 service pack or the next Microsoft Dynamics NAV version that contains this hotfix.

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.



Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

Note Before you install this hotfix, verify that all Microsoft Navision client users are logged off the system. This includes Microsoft Navision Application Services (NAS) client users. You should be the only client user who is logged on when you implement this hotfix.

To implement this hotfix, you must have a developer license.

We recommend that the user account in the Windows Logins window or in the Database Logins window be assigned the "SUPER" role ID. If the user account cannot be assigned the "SUPER" role ID, you must verify that the user account has the following permissions:

  • The Modify permission for the object that you will be changing.

  • The Execute permission for the System Object ID 5210 object and for the System Object ID 9015 object.



Note You do not have to have rights to the data stores unless you have to perform data repair.

Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.
To resolve this problem, change the code in the BufferInvtPosting functon in the Inventory Posting To G/L codeunit (5802) as follows:
Existing code

...
END;
CalcCostToPost(CostToPost,"Cost Amount (Actual)","Cost Posted to G/L",PostToGL);
CalcCostToPost(CostToPostACY,"Cost Amount (Actual) (ACY)","Cost Posted to G/L (ACY)",PostToGL);
PostBufDimNo := 0;

// Delete the following lines.
IF NOT PostToGL THEN
EXIT(FALSE);
// End of the deleted lines.

CASE "Item Ledger Entry Type" OF
"Item Ledger Entry Type"::Purchase:
BEGIN
CASE "Entry Type" OF
...

Replacement code

...
END;
CalcCostToPost(CostToPost,"Cost Amount (Actual)","Cost Posted to G/L",PostToGL);
CalcCostToPost(CostToPostACY,"Cost Amount (Actual) (ACY)","Cost Posted to G/L (ACY)",PostToGL);
PostBufDimNo := 0;

// Add the following lines.
IF NOT PostToGL THEN BEGIN
// Cost amounts are updated by unit value so that that checking can be simulated.
CostToPost := 1;
CostToPostACY := 1;
RunOnlyCheck := TRUE;
END;
// End of the added lines.

CASE "Item Ledger Entry Type" OF
"Item Ledger Entry Type"::Purchase:
BEGIN
CASE "Entry Type" OF
...


You must have one of the following products installed to apply this hotfix:

  • Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

  • Microsoft Dynamics NAV 2009 R2

  • Microsoft Dynamics NAV 2009

  • Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)

  • Microsoft Dynamics NAV 5.0



You cannot remove this hotfix.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

VSTF DynamicsNAV SE: 245349

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

需要更多帮助?

扩展你的技能
了解培训
抢先获得新功能
加入 Microsoft 内部人员

此信息是否有帮助?

谢谢您的反馈意见!

×