Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
Options
Just Curious
Fred_Deutsch
Member Posts: 51
The Company I worked for a while back was sold to a company that uses GP. I stayed on a while to prepare our Navision data for importing into their GP. One thing that always nagged me was when I was told that it was EXTREMELY important to change the case of the Unit of Measure for the non-serialized Items. It was explained to me that Serialized Items (Specific Cost) must be "EA" (all caps) and non-serial items (Average/Std/FIFO,etc) must be "ea" (lower case) and using a UOM of "EA" would force GP into treating any item as serialized. I never had a chance to actually look at GP, but this seemed to be 100% crazy. Is there any truth to that statement that the letter case of the UOM determines the costing and Serial Number requirements of an Item ?
0