Posting with SN Specific

Tonie_CA
Member Posts: 6
My client always complain that he take a much time to posting document using SN tracking specific to the items. because from daily operation one document is about 1000 quantity with all SN Tracking specific.
Does anybody have an idea to solve this problem, to decrease time consume for posting document with SN Tracking specific??
Does anybody have an idea to solve this problem, to decrease time consume for posting document with SN Tracking specific??
Tonipo
PT. Citrathirza Astarijaya
PT. Citrathirza Astarijaya
0
Comments
-
This is complex task, because to be able to enter such a huge amount of data need some processes which will support that (bar code scanners, bar code labels, employees with the scanners in field, etc.). Mainly you need to decide who will enter these data - someone who is really moving the boxes in the warehouse, or someone in office who do not know what will be shipped etc... you need to map the processes and change them to be able to enter the correct data to correct place as soon as possible...0
-
yes i am agree with kine. you can use barcode reader to overcome this tedious task. actually we have done it for one of our customer.Experience Makes Man Perfect....
Rajesh Patel0 -
thank you already response my question
but the main problem is not on entry of enormous data, but posting the document with item using SN Tracking Specific, like posting receive from Purchase Order. it will take a long time to posting one document and i always got complain from my customer like that. does anyone have a solution to decrease time for posting to meet my customer need?? or may be do some customization to decrease the time....thx beforeTonipo
PT. Citrathirza Astarijaya0 -
SN tracking is designed to support specific costing for each SN. To do this it post an item ledger entry (plus GL and value entries) for each unique SN. Your 1000 unit example would result in 1000 Item ledger entries being created.
We had a client, a few years back, with a similar situation. They were using SN tracking and posting sales orders have upward of a few to several thousand units. Needless to say, postings took forever. Considering they usually had a truck driver waiting to leave this was not good.
After they agreed that they did not require costing at the SN level and the costing at the sales line level was acceptable, we modified their system so that it would post only 1 ILE per sales line. We created a new table where we posted the serial numbers related to that line. We had to modify a few forms and reports to support this.There are no bugs - only undocumented features.0
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