Fix payment entry bug: Handle None value in payment_term_outstanding

[husamhammad]

Fix Payment Entry Bug: Handle None Value in Payment Term Outstanding

Description:

This pull request addresses the bug in the Payment Entry module, which occurs when a Payment Entry is generated from a Purchase Order with payment terms. The issue results in a validation error due to an unexpected None value for the latest.payment_term_outstanding when referencing the Purchase Order on the Payment Entry.

Bug Details:

Module: accounts
Version: Frappe v14.42.0, ERPNext v14.32.1
Root Cause:

The bug occurs because the original code does not handle the case when latest.payment_term_outstanding is None for the Purchase Order reference on the Payment Entry.

Solution:

To fix the issue, I introduced a condition to check whether latest.payment_term_outstanding is None. If it is None, the comparison is bypassed, allowing the Payment Entry to proceed without throwing an error.

[lafi87]

I think the sentence should be:

and latest.payment_term_outstanding and ( flt(d.allocated_amount) > flt(latest.payment_term_outstanding))

[codecov]

Codecov Report

Merging #36455 (6e25441) into develop (ba15810) will increase coverage by 0.01%.
Report is 55 commits behind head on develop.
The diff coverage is 84.03%.

❗ Current head 6e25441 differs from pull request most recent head 3976e06. Consider uploading reports for the commit 3976e06 to get more accurate results

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #36455      +/-   ##
===========================================
+ Coverage    64.52%   64.54%   +0.01%     
===========================================
  Files          786      787       +1     
  Lines        61123    61171      +48     
===========================================
+ Hits         39440    39483      +43     
- Misses       21683    21688       +5     

Files Changed	Coverage Δ
...ccounts/doctype/loyalty_program/loyalty_program.py	75.60% <0.00%> (ø)
...ext/accounts/report/trial_balance/trial_balance.py	81.97% <ø> (ø)
...eport/voucher_wise_balance/voucher_wise_balance.py	0.00% <ø> (ø)
erpnext/controllers/website_list_for_contact.py	56.02% <0.00%> (ø)
...facturing/doctype/bom_update_log/bom_update_log.py	43.36% <ø> (ø)
...uring/doctype/bom_update_log/bom_updation_utils.py	44.23% <0.00%> (ø)
erpnext/manufacturing/doctype/job_card/job_card.py	72.84% <0.00%> (ø)
...t/manufacturing/doctype/workstation/workstation.py	88.15% <0.00%> (ø)
...rpnext/stock/report/stock_balance/stock_balance.py	88.84% <ø> (ø)
erpnext/stock/report/stock_ledger/stock_ledger.py	66.66% <ø> (ø)
... and 19 more

... and 2 files with indirect coverage changes