Howdy, Stranger!
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
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Job G/L Journal Unit Costs
KWevick
Member Posts: 103
We have rarely used the Job G/L Journal before, but have a client who needs to now. This client is using Jobs to measure performance to budget, etc, but has no desire or need to accrue and has many expense accounts that they hit. We set up the Job Posting setup to just basically do a wash posting so the original G/L posting just passes thorugh.
The PROBLEM is, that the Job G/L Journal does not allow you to enter a unit cost, so you can't extend your costs using NAV. It will allow you to enter a total unit cost, then back into the Unit Cost. Needless to say, my client, who is new to NAV is not impressed. I did go back several releases, and it appears to have worked this way for a while. It also clears the Job number pretty often and makes you start again. There is not any documentation that explains this behavior. I'm assuming that we need to modify it to act nice. But would like some "Lessons learned from experience" stories. This seems a little bazaar to me.
Thanks.
The PROBLEM is, that the Job G/L Journal does not allow you to enter a unit cost, so you can't extend your costs using NAV. It will allow you to enter a total unit cost, then back into the Unit Cost. Needless to say, my client, who is new to NAV is not impressed. I did go back several releases, and it appears to have worked this way for a while. It also clears the Job number pretty often and makes you start again. There is not any documentation that explains this behavior. I'm assuming that we need to modify it to act nice. But would like some "Lessons learned from experience" stories. This seems a little bazaar to me.
Thanks.
0