[solved] 4.03 Job Cost Posting - N. American Release
MW59
Member Posts: 85
I hope I can describe my issue coherently...
In this scenario, only Resources (no Items) will ever post via the Jobs Journal. Also, nothing will ever land on the Balance Sheet. We have three P&L accounts that should net to zero when the routines in Jobs - Periodic Activities are complete. Specifically, Labor Resources are to debit one account, Machine Resources should debit another, and both types should credit the third, which is declared to be a "wash" account of sorts. I am, by the way, posting Prices rather than Costs.
I'm definitely not an expert where Job Cost Posting is concerned, but I achieved part of what I describe above. That is, I can get ALL resource cost to accumulate as a debit in one G/L account and as a credit in another. I cannot, however, create a distinction between where Labor versus Machine prices land since I can only assign a single Job Posting Group per Job.
Most of my experimentation has been in Job Posting Setup, but I note there are now some Job Cost-related columns in General Posting Setup. Maybe they've been there for a while and I never noticed (they're hidden by default). Perhaps they're a path to what I'm trying to do (since the Resources show General Product Posting Group codes), but a couple of things I tried were unsuccessful.
I guess I'm hoping someone has run into precisely this situation and got it to work. If so, I'd be grateful for any tips.
Thanks!
mw #-o
In this scenario, only Resources (no Items) will ever post via the Jobs Journal. Also, nothing will ever land on the Balance Sheet. We have three P&L accounts that should net to zero when the routines in Jobs - Periodic Activities are complete. Specifically, Labor Resources are to debit one account, Machine Resources should debit another, and both types should credit the third, which is declared to be a "wash" account of sorts. I am, by the way, posting Prices rather than Costs.
I'm definitely not an expert where Job Cost Posting is concerned, but I achieved part of what I describe above. That is, I can get ALL resource cost to accumulate as a debit in one G/L account and as a credit in another. I cannot, however, create a distinction between where Labor versus Machine prices land since I can only assign a single Job Posting Group per Job.
Most of my experimentation has been in Job Posting Setup, but I note there are now some Job Cost-related columns in General Posting Setup. Maybe they've been there for a while and I never noticed (they're hidden by default). Perhaps they're a path to what I'm trying to do (since the Resources show General Product Posting Group codes), but a couple of things I tried were unsuccessful.
I guess I'm hoping someone has run into precisely this situation and got it to work. If so, I'd be grateful for any tips.
Thanks!
mw #-o
I despise animal testing. They get all nervous and give the wrong answers.
0
Comments
-
Navision, by default, can only have one recognition account per job. So you're analyzing your financials by jobs instead of by machine or labor.
We have a client with your same exact requirement. There are 2 ways you can go about it.
1. You will need to make some changes in the standard job posting routine to use the accounts setup on your Gen. Posting Setup instead of looking from the job posting setup.
2. You can use dimensions with analysis views to differentiate each resource with their own dimension values. This way, when you do your analysis view, you can see for the job G/L accounts, which of those amounts are for machine and which are for labor.
The 2nd option requires no modification at all.Confessions of a Dynamics NAV Consultant = my blog
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book0 -
That was really helpful...
It confirmed what I was observing AND you gave me a good idea. You see, the client has no use for dimensions (even global ones), but they're open to new ideas.
I could just set up a single global dimension for use with Resources and make my values "Labor" & "Machine". Then, I could easily get away with only two G/L Accounts... and where the debit amounts are landing, the client could distinguish between the two types via global dimension 1 filters. I like it!
I think I'll leave this open just a bit longer in case others have input, but I really appreciate that Lizard.
Thank you,
mwI despise animal testing. They get all nervous and give the wrong answers.0
Categories
- All Categories
- 73 General
- 73 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
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 327 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