Planning one item code, but managing more than one.

cstupazz
Member Posts: 7
I've more than one different item codes.These codes are very similar
so that for planning porpouses I want them to be just one single code.
Suppose, for istance, I want to manage my invetory with a classic reorder
point; I would like to set the reorder point for a "father" item , but to manage single operative codes.
For this requirement I've tried "Variant" concept in Navision, but I don't
like it , because the system consider also the "Blank" Varaint.
Does anyone has suggestion for this issue , using standard Navision ?
so that for planning porpouses I want them to be just one single code.
Suppose, for istance, I want to manage my invetory with a classic reorder
point; I would like to set the reorder point for a "father" item , but to manage single operative codes.
For this requirement I've tried "Variant" concept in Navision, but I don't
like it , because the system consider also the "Blank" Varaint.
Does anyone has suggestion for this issue , using standard Navision ?
Carlo Stupazzini
0
Comments
-
Carlo,
Can't you disable the blank Variant? e.g. in the table's OnInsertRecord:
IF Variant = blank THEN
ERROR
AlastairAlastair Farrugia0 -
The problem is that Navision uses the variant blank internally.
I try to explain with an example :
I have 3 variant codes, very similar and for each one this
quantity on hand (Inventory) is given :
Variant A : 100 Pieces
Variant B : 20 Pieces
Variant C : 120 Pieces
Reorder point for the father item is 200 Pieces.
Even if totally I have 100+20+120 = 240 pieces > Reoder point,
if I run Navision Planning features it suggests me a requisition
line for a certain quantity of the blank variant.
On the other side I don't want to put the reorder point on the
variant code (Stockeeping Unit).
This is the reason for which I cannot use variant features. Still
looking for any suggest that could allow me to use standard Navision.
thanksCarlo Stupazzini0 -
You can set reorder points on the SKU level, if you really want to distinguish between Variants. That way, for Variant A you can set a different point than for Variant B. I think that when you create the SKU, it defaults to the value of the Item's, but you should check that.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