[
https://issues.apache.org/jira/browse/OFBIZ-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488900
]
Scott Gray commented on OFBIZ-890:
----------------------------------
Hi Marco
I don't think this patch is the correct approach because the orderItemSeqId
field is there to relate individual order items to an order term. It looks
like the data model doesn't support what you are trying to do.
> OrderTerm/InvoiceTerm for Sales Order are not correctly stored if there are
> more than one term days specified on the agreement terms
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-890
> URL: https://issues.apache.org/jira/browse/OFBIZ-890
> Project: OFBiz (The Open for Business Project)
> Issue Type: Bug
> Components: accounting, order
> Affects Versions: SVN trunk
> Reporter: Marco Risaliti
> Priority: Trivial
> Fix For: SVN trunk
>
> Attachments: itemSeqNum.patch
>
>
> If I create an agreement within admin user and Company organization for sales
> order when I try to create an order on the backend and selecting this
> agreement then the OrderTerms and the InvoiceTerms are not correctly stored.
> The fields orderItemSeqId/invoiceItemSeqId are filled with the value "N/A"
> and so if we have two term days specified on the agreement only the last one
> is store on the OrderTerms/InvoiceTerms because orderItemSeqId is part of the
> primary key.
> I have created a patch that fill the orderItemSeqId/invoiceItemSeqId fields
> with a sequencial number.
> It's a very small bug and probably there is no-one that use this
> functionality.
> I have seen it because I'm trying to understand how to create an payment
> aging for OFBIZ.
> Thanks
> Marco
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
