Hi Adrian,
thanks for your comment,
I agree with the separate entity, because there is a also requirement
that history is also to be kept.
Not sure about the productPiceType field? We could use a standard type
and use the from/thrue dates on the productprice to determine to which
price it belongs?
Regards,
Hans
On 11/12/2011 03:30 PM, Adrian Crum wrote:
> If the same rules apply to all orders, then it seems to me you would
> want a separate entity to hold the group order properties:
>
> groupOrderId*
> productId
> productPriceTypeId
> fromDate
> thruDate
> orderQty
>
> -Adrian
>
> On 11/12/2011 3:16 AM, Hans Bakker wrote:
>> Some extra requirements:
>> 1. It seems a start date is also required because deals are often
>> announced before they are active
>> 2. The same product can be ordered as a grouporder and as a normal
>> product. This can be done with list/default price for normal ordering
>> and a new 'grouporder' price for group ordering.
>>
>>
>> On 11/12/2011 10:02 AM, Hans Bakker wrote:
>>> Hi OFBiz community,
>>>
>>> I have a request to implement group ordering.
>>>
>>> That means orders are only full filled when a certain quantity of a
>>> product is ordered before a certain date. When not, the orders are
>>> automatically canceled.
>>>
>>> The current proposal is:
>>>
>>> Add the following fields to product:
>>> groupOrderRequiredQuanty : fixed-point (zero or null: not active)
>>> groupOrderEndDate : date-time
>>>
>>> When this is set:
>>> 1. inventory is not checked
>>> 2. order item stays at the 'entered' status
>>>
>>> Regular job in the background checks for these orderitems and will
>>> set to approved when the orderitems in total reach the product
>>> required quantity before the end date and the inventory is available.
>>>
>>> any comments or suggestions?
>>>
>>> Regards,
>>> Hans
>>>
>>>
>>
Locked
