You’re offline. This is a read only version of the page.
In Nav 2018, when posting payments from the payment journal, not all the time but on occasions the message to recipient would reference a different invoice number that was paid. The invoice number
would be one that was in the payment journal but not the one being paid for that vendor.
The payments were all applied to the correct invoices but on some the "message to recipient" would reference a different invoice number. It could be an invoice from a different vendor or the same
vendor. How can that be.
Just in the journal lines or after when you export, print cheque or produce remittance advice?
[quote user="Pbcharlee"]In Nav 2018, when posting payments from the payment journal, not all the time but on occasions the message to recipient would reference a different invoice number that was paid. The invoice number
would be one that was in the payment journal but not the one being paid for that vendor.
The payments were all applied to the correct invoices but on some the "message to recipient" would reference a different invoice number. It could be an invoice from a different vendor or the same
vendor. How can that be.
[/quote]I’ll assume it is from using the suggest vendor payments feature. This block of code is used to get a message depending on the state of the data and how you run the suggest vendor payments feature. Safe to say you’re not summarising per vendor. I assume it’s the last part of the code which let’s you down. Strange if you are having 1 entry per invoice.
local procedure GetMessageToRecipient(SummarizePerVend: Boolean): Text[140]
var
VendorLedgerEntry: Record "Vendor Ledger Entry";
begin
if SummarizePerVend then
exit(CompanyInformation.Name);
VendorLedgerEntry.Get(TempPaymentBuffer."Vendor Ledg. Entry No.");
if VendorLedgerEntry."Message to Recipient" <> '' then
exit(VendorLedgerEntry."Message to Recipient");
exit(
StrSubstNo(
MessageToRecipientMsg,
TempPaymentBuffer."Vendor Ledg. Entry Doc. Type",
TempPaymentBuffer."Applies-to Ext. Doc. No."));
end;
Do you get the same result in a sandbox? That way your Microsoft partner can debug it. Might be a call with Microsoft is required to log a bug or it already appears as a bug on that build of NAV and you need to apply a cumulative update to fix it
Share
Report
All responses (
Answers (
133
