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
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 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
Question about Serial No. handling in Axapta
harold
Member Posts: 8
I have a question about how serial numbers are implemented in Axapta.
I work with Attain and in Attain the serial numbers are stored in the Item Ledger Entry Table. One line is created for each serial number. When I did a test of creating a Sales Order with 1 item x Qty 20,000 and then generate serial numbers for these items, the result of posting the sales order is approximately 40 MB of database usage (there are other reasons for this growth such as variances and dimensions - but the main growth is caused by 20,000 item ledger entry lines being created for each item/serial number).
This also severely impacts Attains Serial Number Item tracking screen. After a few hundred thousand serial numbers have been generated, the screen to select/input serial numbers in Sales/Purchase orders will take a long time to open.
How does Axapta handle serial numbers? is it similar to Attain? and would result in large database growth also?
Thanks in advance for any help.
Harold
I work with Attain and in Attain the serial numbers are stored in the Item Ledger Entry Table. One line is created for each serial number. When I did a test of creating a Sales Order with 1 item x Qty 20,000 and then generate serial numbers for these items, the result of posting the sales order is approximately 40 MB of database usage (there are other reasons for this growth such as variances and dimensions - but the main growth is caused by 20,000 item ledger entry lines being created for each item/serial number).
This also severely impacts Attains Serial Number Item tracking screen. After a few hundred thousand serial numbers have been generated, the screen to select/input serial numbers in Sales/Purchase orders will take a long time to open.
How does Axapta handle serial numbers? is it similar to Attain? and would result in large database growth also?
Thanks in advance for any help.
Harold
0