Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K 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
- 320 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 385 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
How to transfer Inventory Pick No to Sales Shipment
samantha73
Member Posts: 113
Hi All
I'm struggling to find an event to transfer inventory pick header no (Record "Warehouse Activity Header") to the posted sales shipment header field. WHat happens is when using inventory picks the warehouse employee post the doc but then struggle find a relationship when looking at posted sales shipments so though create a fiedl to hold the no
I'm struggling to find an event to transfer inventory pick header no (Record "Warehouse Activity Header") to the posted sales shipment header field. WHat happens is when using inventory picks the warehouse employee post the doc but then struggle find a relationship when looking at posted sales shipments so though create a fiedl to hold the no
0
Best Answer
-
vaprog
Member Posts: 1,152
samantha73 wrote: »Hi All
I'm struggling to find an event to transfer inventory pick header no (Record "Warehouse Activity Header") to the posted sales shipment header field.
That is, because no such relation exists. Even on a document line level there may be multiple pick documents related to one shipment, and there may be multiple shipments related to one pick document line, and these may vary from line to line.
So, to get the full picture, you need to create a query. The sales order (line) primary key is the common fields.
In your setup, probably in most cases, there really is just one pick document no. involved in one shipment. You would need to impose restrictions to make this sure.
To get data that probably is sufficient for reference, you could transfer the pick document no. to the source line (sales line) probably best during registration, then transfer the field from the sales line to the posted sales shipment line when posting the shipment, and, if you really want, find some algorithm to decide, which pick document no. from the lines to transfer to the sales shipment header, also during or directly after posting the shipment.
You should have no trouble finding events for each of these steps.
0
Answers
That is, because no such relation exists. Even on a document line level there may be multiple pick documents related to one shipment, and there may be multiple shipments related to one pick document line, and these may vary from line to line.
So, to get the full picture, you need to create a query. The sales order (line) primary key is the common fields.
In your setup, probably in most cases, there really is just one pick document no. involved in one shipment. You would need to impose restrictions to make this sure.
To get data that probably is sufficient for reference, you could transfer the pick document no. to the source line (sales line) probably best during registration, then transfer the field from the sales line to the posted sales shipment line when posting the shipment, and, if you really want, find some algorithm to decide, which pick document no. from the lines to transfer to the sales shipment header, also during or directly after posting the shipment.
You should have no trouble finding events for each of these steps.