Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K 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
- 298 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
NAV MFG Calc. Low Level Code Funtionality.
ALyczkowski
Member Posts: 33
Hello all,
We are upgrading from a 3.60 database to NAV2009 SP1 (classic Client). I noticed after doing some testing that the "Calc. Low-Level Code" Functionality in 3.60 outperformed the same functionality in 2009. (15 Minutes in 3.6, 2-3 hrs in 2009). Both are called from CU 99000853.
As this functionality Locks several Tables (Item, Production BOM Line, Production BOM Header) while executing, it really put a strain on our business. I strongly encourage my users to perform this function daily to prevent any Looped Bills of Material, but At this amount of time where these 3 tables are locked, the users simply will not perform this task.
Do you have any ideas as to why the Routine takes so much more time, and/or any Suggestions on how I can resolve this?
Thanks,
Alan
We are upgrading from a 3.60 database to NAV2009 SP1 (classic Client). I noticed after doing some testing that the "Calc. Low-Level Code" Functionality in 3.60 outperformed the same functionality in 2009. (15 Minutes in 3.6, 2-3 hrs in 2009). Both are called from CU 99000853.
As this functionality Locks several Tables (Item, Production BOM Line, Production BOM Header) while executing, it really put a strain on our business. I strongly encourage my users to perform this function daily to prevent any Looped Bills of Material, but At this amount of time where these 3 tables are locked, the users simply will not perform this task.
Do you have any ideas as to why the Routine takes so much more time, and/or any Suggestions on how I can resolve this?
Thanks,
Alan
0
Comments
I have no idea why the increase in time, but have you tried to change the Manufacturing Setup to Dynamically Change the Low Level Code. This will recalculate each time you change the BOM and specifically target only the items impacted. It can have a negative impact, but most of the time it won't be noticeable. I would test this and see.
Good Luck,
Karen
I will test this and discuss it with my users. Thanks for the suggestion.
Alan