Purchase Invoices for G/L Accounts and Dimensions

NickA
Member Posts: 32
Hi,
There must be a reasonable explanation for this one, some obvious reason why it works the way it does, can anyone help?
Using Cronus, I enter a Purchase Invoice for a G/L Account (Say, 8430 - Travel) and assign a Dimension with value against the line.
Problem is, the dimension only seems to get applied to one side of the G/L posting - IE not the 'accounts payable' balancing posting.
This isn't what I expected - I thought the balancing posting would be broken down by dimension too, but it seems to be across the whole invoice.
Is there a reasonable explanation for this? Or must I tell the customer to start splitting their invoices by dimension?
Thanks in advance,
NickA
There must be a reasonable explanation for this one, some obvious reason why it works the way it does, can anyone help?
Using Cronus, I enter a Purchase Invoice for a G/L Account (Say, 8430 - Travel) and assign a Dimension with value against the line.
Problem is, the dimension only seems to get applied to one side of the G/L posting - IE not the 'accounts payable' balancing posting.
This isn't what I expected - I thought the balancing posting would be broken down by dimension too, but it seems to be across the whole invoice.
Is there a reasonable explanation for this? Or must I tell the customer to start splitting their invoices by dimension?
Thanks in advance,
NickA
0
Comments
-
Do u mean that the dimension code in the header ultimately overrides the dimension code in the Purch line. If that is the case, then u will have to take a look in "dimension priorities" and make G/l superior to let's say Vendor0
-
And yes if u like to post deifferent Dimension values to the same dimesnion code u will have to take care of this on line level0
-
The dimension only exists against the purchase line, it doesn't exist against the purchase header - so I don't think priorities come into it?
The dimension does appear on one side of the G/L posting, just not on the other 'balancing' side (The Vendor accounts payable G/L account).
It's like the first posting comes from a purchase line and takes the dimensions from the line but the balancing posting is 'whole invoice' - it isn't broken down by line and takes the dimensions from the header.
I think it may just be something they'll have to live with.
Thanks for responding
NickA0
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