BOM Error

wesleys
Member Posts: 30
I've been unable to find a reference to this error anywhere on the forums so I must be the only person to uses dimensions on item records and also does a little BOMing.
The actual error I get while trying to post a BOM for certain SKUs states:
The Item Journal Batch does not exist.
Identification fields and values:
Journal Template Name='',Name='REECEF'
Journal Template Name: '', Name: REECEF
The Batch "REECEF" does in fact exist for the "BOM" template, but while posting, the template name does not manage to make it to the TempJrnlLine for whatever reason. I actually don't think it is copied to the TempJrnLine ever for any BOM. I can work around this error by removing the dimension values for the item being created as well as removing the dimension values for all of the items that make up the final SKU.
Anyone else ever experience this problem? Is there a default setting somewhere that I'm missing?
Any help would be greatly appreciated.
The actual error I get while trying to post a BOM for certain SKUs states:
The Item Journal Batch does not exist.
Identification fields and values:
Journal Template Name='',Name='REECEF'
Journal Template Name: '', Name: REECEF
The Batch "REECEF" does in fact exist for the "BOM" template, but while posting, the template name does not manage to make it to the TempJrnlLine for whatever reason. I actually don't think it is copied to the TempJrnLine ever for any BOM. I can work around this error by removing the dimension values for the item being created as well as removing the dimension values for all of the items that make up the final SKU.
Anyone else ever experience this problem? Is there a default setting somewhere that I'm missing?
Any help would be greatly appreciated.

0
Comments
-
Hi,
I had a similar error while I was trying to use a production BOM in manufacturing. It turned out that there was an empty line at the end of the BOM. I deleted it and the problem went away.
Hopefully it's that easy.
J0 -
I had the same problem.
Unfortunately, in 3.7 (and I think in 4.0 as well) you cannot produce the BOM if any of its components have dimensions.This of course is a problem if your setup is such that the dimension in question has "Code Mandatory" value posting for the Item table (27).
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