Partial invoicing of lot tracked sales order lines.

mariussw
Member Posts: 52
In this scenario the Sales Order is shipped at once, but sales invoicing is done in chunks following the shipment.
Posting fails because the Item Tracking Line does not set Qty. to Invoice (Base) and indirectly Qty to Invoice fields, according to the Qty to Invoice field as on the Sales Order.
This causes an error message: "The quantity to invoice does not match the quantity defined in item tracking." when attempting to post an invoice from the order.
While manually setting the the Qty. to Invoice (Base) on the item Tracking Lines according to that on the PO line resolves the matter, I have some questions for discussion.
1. Is this is the correct approach, and shouldn't the system rather set the Qty to Invoice in the tracking lines automatically? One may reason that the system will not know which lot's tracking line to update (if more than one lot / tracking line is used for the same Order line). Since invoicing is about financial value of inventory, I do not think which lot matters at all. Except perhaps if the costing method is 'Specific'. Hence does it really make sence to manage Quantity to Invoice on Item tracking lines at all?
2. Will partial invoicing in this fashion adversely affect inventory costing? Average costing I believe (without checking), affects costing according to oldest open Item Ledger Entry first - i.e. regardless of lot thereof. Same for FIFO. Is this correct?
To put it differently, will COGS be affected and the open item ledger entry be closed off (applied) according to the actual lot selected or according to the oldest open ILE regardless of the Lot?
Thanks
Posting fails because the Item Tracking Line does not set Qty. to Invoice (Base) and indirectly Qty to Invoice fields, according to the Qty to Invoice field as on the Sales Order.
This causes an error message: "The quantity to invoice does not match the quantity defined in item tracking." when attempting to post an invoice from the order.
While manually setting the the Qty. to Invoice (Base) on the item Tracking Lines according to that on the PO line resolves the matter, I have some questions for discussion.
1. Is this is the correct approach, and shouldn't the system rather set the Qty to Invoice in the tracking lines automatically? One may reason that the system will not know which lot's tracking line to update (if more than one lot / tracking line is used for the same Order line). Since invoicing is about financial value of inventory, I do not think which lot matters at all. Except perhaps if the costing method is 'Specific'. Hence does it really make sence to manage Quantity to Invoice on Item tracking lines at all?
2. Will partial invoicing in this fashion adversely affect inventory costing? Average costing I believe (without checking), affects costing according to oldest open Item Ledger Entry first - i.e. regardless of lot thereof. Same for FIFO. Is this correct?
To put it differently, will COGS be affected and the open item ledger entry be closed off (applied) according to the actual lot selected or according to the oldest open ILE regardless of the Lot?
Thanks
0
Comments
-
Even with specific costing method, if it is not Automatic adjusted during posting of sales , it goes out at Average cost ,only exception is Standard. I hope it answers both of ur ques.Kapil Khanna0
-
Can you kindly help me to clear context please?
What do you mean by 'if it is not automatic adjusted'? Do you mean automatic cost posting not selected in the setup, or do you mean that a fixed application (between inventory increase and decrease) is done by the user?
What is the verdict, does Qty to Invoice appears on the item tracking line have any significance?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