Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
The latest Transaction No. must be an application in Vendor
kellycyw
Member Posts: 24
Hi All,
One of our customer using NAV 5.0 SP1 Malaysia version. We encounter a problem when trying to unapply vendor ledger entries. The following error appears:
The latest Transaction No. must be an application in Vendor Ledger Entry No. ######.
Looking at the Detailed Vendor Ledger Entries I notice that the last transcation No Entry type <> Application.
And Last entry Type = Unrealized Loss and after clarify with end user, they had run the Adjust Exchange Rate batch job.
It could be causing by Unrealized Gain/Loss batch job.
Thanks in advance
Kelly
One of our customer using NAV 5.0 SP1 Malaysia version. We encounter a problem when trying to unapply vendor ledger entries. The following error appears:
The latest Transaction No. must be an application in Vendor Ledger Entry No. ######.
Looking at the Detailed Vendor Ledger Entries I notice that the last transcation No Entry type <> Application.
And Last entry Type = Unrealized Loss and after clarify with end user, they had run the Adjust Exchange Rate batch job.
It could be causing by Unrealized Gain/Loss batch job.
Thanks in advance
Kelly
0
Comments
yes, that's the case, the check is in CU 227. The reason for this is that the unapply() function would undo realized and unrealized gain / loss entries caused by the application as well. This would invalidate later adjust exchange rate batches, since the amount to adjust has changed then.
From what you write it was a partial application with the remaining amount being adjusted in the adjust exchange rates batch. This is the last transaction on the vendor ledger entry then, and the unapply() function refuses to work. And Adjust Exchange Rate cannot be reversed
What you can try - I would recommend to do this in a copy of the production database, though:
- comment out the check in CU 227
- do the unapply
- rerun the adjust exchange rates for the vendor entries.
This should result in an additional adjustment on the vendor ledger entries.
with best regards
Jens
Pargesoft
I did check via the partner source but unfortunately i not able to find it.
could you please sent the the URL and link over here, if possible.
Thanks in advance.
Kelly
Pargesoft