You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2018/12/11 10:12:00 UTC

[jira] [Assigned] (OFBIZ-2456) Allow to control Prefix and Purchase Order sequence.

     [ https://issues.apache.org/jira/browse/OFBIZ-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacques Le Roux reassigned OFBIZ-2456:
--------------------------------------

    Assignee:     (was: Jacques Le Roux)

Too bad this was not done before OFBIZ-9986

> Allow to control Prefix and Purchase Order sequence.
> ----------------------------------------------------
>
>                 Key: OFBIZ-2456
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2456
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: accounting
>    Affects Versions: Trunk
>            Reporter: Jacques Le Roux
>            Priority: Major
>
> For the moment the Data Model does not take into account the possibility to control Prefix and Purchase Order sequence.
> In PartyAcctgPreference, there are the couples of fields (invoiceSequenceEnumId, invoiceIdPrefix), (quoteSequenceEnumId, quoteIdPrefix) and (orderSequenceEnumId, orderIdPrefix). So we should either add a couple (purchInvoiceSequenceEnumId, purchinvoiceIdPrefix), which IMO is simpler and enough, or deprecate the couple (invoiceSequenceEnumId, invoiceIdPrefix) to (salesInvoiceSequenceEnumId, salesInvoiceIdPrefix) and add the couple above. Then the same User Interface than for Sales Order  (configuration settings in Organization GL Settings) could be used but it would have to differentiate the 2 kinds of invoices.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)