Post Inventory Cost to G/L

adiazram
Member Posts: 6
Hi guys!
I am in trouble because I made a mistake I ran this process and now I want to go back the information as it was...
do you have any idea how to do it?
Regards,
:roll:
I am in trouble because I made a mistake I ran this process and now I want to go back the information as it was...
do you have any idea how to do it?
Regards,
:roll:
0
Comments
-
If you selected post per entry, it would be near impossible to reverse, as it makes separate entries for everything with the original document numbers used, so there is no way to navigate and see all the entries made
If you posted by group instead then it makes all the entries together and you should be able find them all. Easiest thing is to probably just make reversing G/L entries
I do not think it is realistic the think you could reverse all the adjust cost entries made to each item ledger entry.
good luck.0 -
It's probably not a good idea to reverse the G/L entries. If you do this, your inventory value and your G/L will not tie out.Confessions of a Dynamics NAV Consultant = my blog
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book0 -
it is not likely your inventory and g/l will tie out anyways, in 6 years with Navision it hasn't happened, until I make manual entries to adjust values to match, never has the program accuratly tied inventory to g/l for us.
maybe 4.0 will be better, but 2.0 never did
just my opinion0 -
This can be done only with due diligence on the customer's end, which requires a kick in the butt from the VARs.
In the US, the banks and auditors puts a lot of pressure on the accounting to have everything tie out.Confessions of a Dynamics NAV Consultant = my blog
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book0 -
isn't it the other way around: if you posted 'per entry', then the job places the value entry number in the g/l entry table (17) and/or the g/l entry no. in the value entry table (5802). Then you can manually reverse the g/l journal and blank the column 'cost posted to g/l' in the entries of table 5802.
If you posted 'per entry type' than it's more difficult as you need to know what was posted already before you started the job. You need the included report for that, to check what the first entry number was. Blank out the 'cost posted' column for the entries after that entry number.
ALWAYS MAKE SURE THAT THE TOTAL VALUE OF THE REVERSE JOURNAL IS THE SAME AS THE AMOUNT YOU'RE BLANKING OUT IN TABLE 5802!
good luck,
Johan.0 -
joh_ver is right,
I may be wrong here but I think youll find the Journal that the routine Posted to G/L under Posted Journals and the Source Code from the Setup for this thing. from there you can find all entries made in the G/L.
Your biggest probem is that you must also reverse all Value Entries that now have been set as posted to G/L (Cost Posted to G/L field has been updated) otherwise your inventory value will never ever again match with your G/L.
If you have posted By Entry youre lucky cause your G/L Entries tells you what Value Entries you should reverse on.
Otherwise your basically screwed on that part i guess....0 -
I am working with Navision 3.70 and posted per Posting Group.
I can erase all the entries that affected G/L Entry (17) but I need to identify the others entries that were modified in Value entry or Item Ledger Entry and reverse the information.
thank you guys!
I really apreciate your suggestions0 -
joh_ver wrote:isn't it the other way around: if you posted 'per entry', then the job places the value entry number in the g/l entry table (17) and/or the g/l entry no. in the value entry table (5802). Then you can manually reverse the g/l journal and blank the column 'cost posted to g/l' in the entries of table 5802.
If you posted 'per entry type' than it's more difficult as you need to know what was posted already before you started the job. You need the included report for that, to check what the first entry number was. Blank out the 'cost posted' column for the entries after that entry number.
ALWAYS MAKE SURE THAT THE TOTAL VALUE OF THE REVERSE JOURNAL IS THE SAME AS THE AMOUNT YOU'RE BLANKING OUT IN TABLE 5802!
good luck,
Johan.
Umm... Modifying the ledgers is NOT recommended for any end users and it can and WILL cause serious damage to the integrity of your database.Confessions of a Dynamics NAV Consultant = my blog
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book0 -
adiazram wrote:I am working with Navision 3.70 and posted per Posting Group.
I can erase all the entries that affected G/L Entry (17) but I need to identify the others entries that were modified in Value entry or Item Ledger Entry and reverse the information.
thank you guys!
I really apreciate your suggestions
Oi.... I hope you're doing this on a test database first. It's not as simple as just deleting Value Entry and G/L Entry tables. There are register tables plus other tables as well...Confessions of a Dynamics NAV Consultant = my blog
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book0 -
Editing ledger tables in a production system is a VERY BAD IDEA
Since what you are talking about is basicly an unwanted GL posting. I see 2 possible approaches:
1. Restore a backup (may not be practical)
2. Reverse the entries.
It should be fairly easy to locate the G/L Register entry for this posting. Then create a process report to read through the associated General Ledger Entries and load a General Journal with reversing entries.
Then review and post.
You will also need to keep this so you can un-reverse the entries later .There are no bugs - only undocumented features.0 -
hold it for a second.
Bbrown suggested to only reverse the g/l journal. But then value on the inventory account will not be the same anymore as the sum of the value entries."cost posted to g/l" !!!
I read in one of the threads that entries should never be deleted. This was also not suggested! In the entries of table 5802 only the field 'cost posted to g/l' should be set (back) to 0.
And about the integrity: the inventory-amount of the reversed g/l journal should be the same as the value change (modifying 'cost posted' to 0) in table 5802.0 -
This is an accounting problem. Treat it as such. Stop playing with the database every time someone makes a mistake. Post an adjusting entry and use it to reconcile G/L to Inventory. Reverse the adjustment when appropriate.
Account Rule #1: Accountants do not have erasers!There are no bugs - only undocumented features.0 -
adiazram wrote:I can erase all the entries that affected G/L Entry (17)
Are you crazy? That's considered fraud! Once you post financial information it is a matter of record, and if you make a mistake you need to post a correcting journal. :shock:0 -
100% agree..
Always think of this from the accountants point of view and you can't go too far wrong.
It is always a good idea to chat with the accountants anyway, they are the guys who have to answer the awkward questions with the auditors.
Very often, they will panic the least and suggest journals (reversing or otherwise).
NEVER delete entries.
ALWAYS make correcting entries so you have an audit trail
Good rules to live by unless you really need to hide the dead bodies.Experience is what you get when you hoped to get money0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions