Howdy, Stranger!
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
- 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
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 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
Why does Lot Specific Tracking prevent out of stock?
toft
Member Posts: 3
Hi,
Does anybody know why COD 22 does not allow posting of "outbound before inbound" when the item has Lot Specific Tracking.
Procedure InsertItemLedgEntry:
IF (ItemLedgEntry.Quantity < 0) AND
(ItemTrackingCode."SN Specific Tracking" OR ItemTrackingCode."Lot Specific Tracking")
THEN
ERROR(Text018,"Serial No.","Lot No.","Item No.","Variant Code");
In my search for a reason I have tried to bypass the check and tried different scenarios to see if there was an undesired sideeffect, f.eks
sale of Lot A from Location1.
puch of Lot B to location 2
transfer from Location 2 to location 1
reclass of lot 2 to lot 1
So far all scenarios I have run has succesfully handled applications and tracked the cost through the chain of applications from purch to sale.
Thanks
Jens
Does anybody know why COD 22 does not allow posting of "outbound before inbound" when the item has Lot Specific Tracking.
Procedure InsertItemLedgEntry:
IF (ItemLedgEntry.Quantity < 0) AND
(ItemTrackingCode."SN Specific Tracking" OR ItemTrackingCode."Lot Specific Tracking")
THEN
ERROR(Text018,"Serial No.","Lot No.","Item No.","Variant Code");
In my search for a reason I have tried to bypass the check and tried different scenarios to see if there was an undesired sideeffect, f.eks
sale of Lot A from Location1.
puch of Lot B to location 2
transfer from Location 2 to location 1
reclass of lot 2 to lot 1
So far all scenarios I have run has succesfully handled applications and tracked the cost through the chain of applications from purch to sale.
Thanks
Jens
0