Howdy, Stranger!
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
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Adjust Cost Job...
Mehdi.Chahed
Member Posts: 14
Hi, :P
I’m trying to solve an Adjust costing problem on a Retail Navision 3.60 SQL BD based on Infostore 4.22. :?
Here is my problem:
As you can guess DB size is huge. Actually, it’s close to 70Gbites.
All hot fixes linked to Stock management are implemented on the system.
Items are manged in Fifo.
Adjust Cost Job have never been executed previously [no comment!]. During that period, and for every month closing, accountants were used to make inputs via Gen. journal to have Item values on G/L...
Actually, When running the Adjust Cost Job, the program enters endless loops for some items. Every time I tried, I was obliged to stop the procedure.
In any case, the DB is too big to be proceeded that way so I’m thinking to modify the Code so that only Value entries of a given period will be treated. Is it feasible :?: Is it correct :?: Any better idea :?:
Thank U for answering.
I’m trying to solve an Adjust costing problem on a Retail Navision 3.60 SQL BD based on Infostore 4.22. :?
Here is my problem:
As you can guess DB size is huge. Actually, it’s close to 70Gbites.
All hot fixes linked to Stock management are implemented on the system.
Items are manged in Fifo.
Adjust Cost Job have never been executed previously [no comment!]. During that period, and for every month closing, accountants were used to make inputs via Gen. journal to have Item values on G/L...
Actually, When running the Adjust Cost Job, the program enters endless loops for some items. Every time I tried, I was obliged to stop the procedure.
In any case, the DB is too big to be proceeded that way so I’m thinking to modify the Code so that only Value entries of a given period will be treated. Is it feasible :?: Is it correct :?: Any better idea :?:
Thank U for answering.
0
Comments
Cristina
Of primary importance: users of Navision on Navision 3.60 or MBS Navision 3.70 must be disciplined in running the Adjust Cost Item Entries at the end of the month. In addition, it is recommended that this procedure be run daily or weekly throughout the reporting period to make sure that adjustments are getting created within the correct time period.
Note - The caveat is that this process must be run when other transactions are not being processed because the operation locks tables and prevents entries from posting.
I Also Remember a HotFix For the Infinite Loop Problem. Maybe someone knows it off hand.
http://www.BiloBeauty.com
http://www.autismspeaks.org
I believe there are 26 or more hot fixes to version 3.6, a lot of which address this and similar issues. We had the same problem in a 3.6 database and were forced to install all 26 hotfixes before the problem was resolved.
Incidentally, if you don't run the adjust cost AND the post cost to GL daily, then your profit calculations will be seriously incorrect!