[
https://issues.apache.org/jira/browse/OFBIZ-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469587
]
Jacopo Cappellato commented on OFBIZ-682:
-----------------------------------------
Si,
yes, I'm aware of this problem; in fact I have modify the code of the custom
project I'm working on to correctly handle this.
I mean that the billing accounts balance routines were assuming that an order
could be associated to more than one billing account but - in my opinion - (and
I could be wrong) there are no big advantages of handling things in this way.
I'd prefer, as soon as a decision is taken to modify the existing design of how
billingaccounts/orders/invoices interact, that we make things working for one
billing account per order per invoice.
But, again, I could be wrong.
Jacopo
> Possibly dangerous code in createPaymentApplication for billingAccount
> ----------------------------------------------------------------------
>
> Key: OFBIZ-682
> URL: https://issues.apache.org/jira/browse/OFBIZ-682
> Project: OFBiz (The Open for Business Project)
> Issue Type: Bug
> Components: accounting
> Reporter: Si Chen
>
> This code is back in createPaymentApplication and could be potentially
> dangerous:
> <if-not-empty field-name="invoice.billingAccountId">
> <set field="paymentAppl.billingAccountId"
> from-field="invoice.billingAccountId"/>
> </if-not-empty>
> there could be problems with balance calculations when billing accounts and
> other methods are used to pay for orders.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
