In NM2.6E, we are attempting to post output for multiple production orders (final routing step) in one output journal. When “Automatic Cost Posting” is checked, we get an error message saying “G/L Entry No. xxx already exists.” The first Prod. Order posts both the routing step cost and the transfer of standard cost to Inventory correctly, and the second Prod. Order posts the routing step cost correctly, but when posting the transfer of the second line, codeunit 12 has forgotten to increment the NextEntryNo field for the second routing step cost entry, resulting in the error. Has anyone else seen this problem and, if so, have you solved it? Obviously we can work around this by turning off Automatic Cost Posting or posting one Prod. Order at a time, but we would prefer not to. Thanks in advance, Scot Carlson
Have you asked your NSC for assistance or for them to contact Navision-US support for assistance on this? It seems this is one they should address for you - especially when you’ve narrowed it down so well. Dave Studebaker das@libertyforever.com Liberty Grove Software A Navision Services Partner Edited by - daves on 2001 Dec 31 21:23:07
quote:
Originally posted by daves: Have you asked your NSC for assistance or for them to contact Navision-US support for assistance on this? It seems this is one they should address for you - especially when you’ve narrowed it down so well. Dave Studebaker das@libertyforever.com Liberty Grove Software
We sent them a notice on this problem this morning. I was hoping to cast a wider net by posting here as well. Happy New Year! Scot Carlson
[quote]
Originally posted by Scot_Carlson: In NM2.6E, we are attempting to post output for multiple production orders (final routing step) in one output journal. When “Automatic Cost Posting” is checked, we get an error message saying “G/L Entry No. xxx already exists.” The first Prod. Order posts both the routing step cost and the transfer of standard cost to Inventory correctly, and the second Prod. Order posts the routing step cost correctly, but when posting the transfer of the second line, codeunit 12 has forgotten to increment the NextEntryNo field for the second routing step cost entry, resulting in the error. Has anyone else seen this problem and, if so, have you solved it? Obviously we can work around this by turning off Automatic Cost Posting or posting one Prod. Order at a time, but we would prefer not to. Thanks in advance, Scot Carlson Mr. Scot Carlson observation is correct. We NSC at Saudi Arabia are also facing the same problem. To one our client we have recently upgraded Navision Financials to Navision Manufacturing 2.6E. We are not able to post Production Orders from Output Journal in multiple lines. We get the error message " G/L entry No.—" already exists. Presently we are managing to post by selecting one line at a time. This is very tedious and time consuming. with Regards, ERP Project Manager (Navision Financials)
I believe the problem you’ve described is fixed in the update to NM 2.60f. In the changes.txt for that update is the following item: ________________________________________ 21) Automatic Cost Posting and Flushing When flushing took place while Automatic Cost Posting was on, you could get an error message stating that a G/L entry already existed. _________________________________________ Check with your NTR for the updates from NM2.60e to NM2.60f Dave Studebaker das@libertyforever.com Liberty Grove Software A Navision Services Partner
Thankyou for your reply Mr.Scot_Carlson and Mr.David Studebaker. R. Sunder Rao ERP Project Manager (Navision Financials)