Delopment Quest.-Modification for Production BOM No. used
Mindi@iig
Member Posts: 6
I was considering a modification that would affect which Production BOM was used when a Production Order was created. Maybe just something as simple as allowing the user to setup a Production BOM No. per Varient Code.
I just need to know how many places this will affect. How many code units or reports make calculations based on the Production BOM No. assigned to the Item record?
Now with 4.0 there are even more planning option but I haven't been able to determine if means there would be even more changes that would need to be made.
Have any of you already made a modification in this area and already know this answer?
Thanks,
Mindi
I just need to know how many places this will affect. How many code units or reports make calculations based on the Production BOM No. assigned to the Item record?
Now with 4.0 there are even more planning option but I haven't been able to determine if means there would be even more changes that would need to be made.
Have any of you already made a modification in this area and already know this answer?
Thanks,
Mindi
0
Comments
-
There's a codeunit called something like 'Version management' that navision uses to determine which version to use. If you make your change there, it should cover most instances. Other than that you'll just have to run the where used of the version code field.0
-
"There's a codeunit called something like 'Version management' that navision uses to determine which version to use. If you make your change there, it should cover most instances. Other than that you'll just have to run the where used of the version code field."
Is There a where used field/Function/code unit in Navision ????//EMK\\0 -
-
Oh :? I was hoping it was a field relation identifing tool//EMK\\0
-
there are about 10 objects that use getbomversion function of versionmanagement codeunit.
If you want to use variant code based production BOM, you must setup BOM versions that will be used by one or more variant of item. In thias point, a table with columns itemno, variantcode,promBOmno,versioncode can help you.
1. If you use requistion worksheets, you have to edit the source code requisition table(onvalidate trigger of Prod. Bom No. field). On there, you must fill manually the bom version code field by using the table you created or the version code directly.
2. If you dont use requisition worksheet and you will create prod. orders manually, you have to change the source code of prod. order line table.
this solution can help, but it is not the exact solution. If you have production BOMs that is more than one level, you come up with another problem. the answers i mentioned above can deal with one level production bom. for the exact solution, you musn't use variant code for the items that are in 2. or 3. level of production BOMs.
additionally, you have to comment some lines of some codeunits like Inventory Profile Offsetting... just follow the code when you click the "calculate net change" function in planning worksheet.
PS: write error('asas') to the function getbomversion of versionmanagemant codeunit. this can help you.0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K 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
- 610 NAV Courses, Exams & Certification
- 1.9K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 251 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
