Payment Applied to Credit Memo
Mauddib
Member Posts: 269
Hi all,
In Navision 5 and 2009 if I posted a payment of, say, +200 against a credit memo of, say, -100 the result in Cust. Ledger Entry would be:
1) The credit memo would get a remaining amount of 0 and OPEN = FALSE.
2) The payment would have a remaining amount of 100 and OPEN = TRUE.
I just repeated this in our 2015 Cronus however and the result is that:
1) The Credit Memo is still open = TRUE with a Remaining Value of +100 (But Positive = FALSE !!!)
2) The payment will have remaining value of 0 and OPEN = FALSE.
Further "application" attempts then fail on this customer because the system does not handle that I have a +100 with Positive = FALSE. So when trying to apply other entries to this credit memo to close it I am thrown the error "The Table Cust. Ledger Entry is empty". Which I think comes from the CU12 line "TempOldCustLedgEntry.FIND('-');" or similar.
Anyone know what has changed in 2015 in the application process that suddenly open up such as weird result?
And yes, if I use "Refund" instead of "payment" it works correctly with the result:
1) The credit memo would get a remaining amount of 0 and OPEN = FALSE.
2) The refund would have a remaining amount of 100 and OPEN = TRUE.
So I am aware that using "refund" here would solve my issue, but not answer the question of why it is suddenly going wrong with the application.
In Navision 5 and 2009 if I posted a payment of, say, +200 against a credit memo of, say, -100 the result in Cust. Ledger Entry would be:
1) The credit memo would get a remaining amount of 0 and OPEN = FALSE.
2) The payment would have a remaining amount of 100 and OPEN = TRUE.
I just repeated this in our 2015 Cronus however and the result is that:
1) The Credit Memo is still open = TRUE with a Remaining Value of +100 (But Positive = FALSE !!!)
2) The payment will have remaining value of 0 and OPEN = FALSE.
Further "application" attempts then fail on this customer because the system does not handle that I have a +100 with Positive = FALSE. So when trying to apply other entries to this credit memo to close it I am thrown the error "The Table Cust. Ledger Entry is empty". Which I think comes from the CU12 line "TempOldCustLedgEntry.FIND('-');" or similar.
Anyone know what has changed in 2015 in the application process that suddenly open up such as weird result?
And yes, if I use "Refund" instead of "payment" it works correctly with the result:
1) The credit memo would get a remaining amount of 0 and OPEN = FALSE.
2) The refund would have a remaining amount of 100 and OPEN = TRUE.
So I am aware that using "refund" here would solve my issue, but not answer the question of why it is suddenly going wrong with the application.
0
Categories
- All Categories
- 75 General
- 75 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
- 610 NAV Courses, Exams & Certification
- 1.9K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 251 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions