Well I'm back to my first idea of removing the OrderItemShipGrpInvRes
entity. If removed then "Reserve Method Enum Id" store setting would be
useless but the inventory item assignment operations it performs limits
the amount of control over inventory assignment anyways. A better
design would be one that doesn't automatically assign new inventory
received to a specific order item like the FIFO, LIFO options.
I need to be able to choose the particular order items to which received
inventory should be assigned and the FIFO and LIFO options prevent it.
I have complex ship groups associated with order where order items are
scheduled to be shipped in intervals throughout the year. Therefore the
order of reservation mostly depends on the ship group due date rather
than first order in (FIFO) or last out (LIFO). For example, I could
have two different orders for the same product and the first order is
scheduled to ship 20 in a week and then 20 more in 5 months while the
second is scheduled to ship 20 in two weeks. In this case the
reservations should first occur on the first order schedule then the
second order schedule then the first order second schedule. Basically it
would be reserving based on the shipBeforeDate of ship groups associated
with orders. But adding a new reserve method like FIFO or LIFO to
handle reserving based on ship groups still wont be sufficient for my
needs because there are cases when the user needs to manually assign
received inventory to an order item regardless of the ship group
shipBeforeDate. Therefore I think that the inventory reservation code
should be replaced with something that allows such control.
Having a view-entity that joins OrderItemShipGroupAssoc with
ItemIssuances to determine the amount has been shipped seems like the
best solution. This would allow for a list of ship group with
quantities still left to ship to be generated and inventory could be
assigned manually during picking, packing, and shipping and instead of
automatically based on LIFO, FIFO, etc. when was received.
On 10/24/2013 08:49 AM, Christian Carlow wrote:
Would someone please provide scenarios where "Reserve Inventory"
should be set to "N" for a store. It causes OrderItemShipGrpInvRes
not to be used so there's no way to ship the order item. Does this
mean that "Reserve Inventory" is necessary anytime a store requires
shipments?
I'm wondering if I should code for allowing "Reserve Inventory" set to
"N" to allow for creating shipments for order items.
On 10/24/2013 08:05 AM, Christian Carlow wrote:
OrderItemShipGrpInvRes seems like it was meant to track backorder
information by storing aggregate quantities that could otherwise be
calculated by subtracting ItemIssuance records from matching
InventoryItem records in the way that InventoryItem quantityOnHand
and availableToPromise fields are aggregates of the
InventoryItemDetail records. I suppose that referencing an aggregate
quantity would be much faster way to get a value so I'll attempt to
fix the without trying to remove the entity.
I'm going to start working on this and assume the shipment operations
have not yet been completed in any version.
On 10/23/2013 04:28 PM, Christian Carlow wrote:
IMO, the OrderItemShipGrpInvRes entity should be removed and
anything referencing it should be changed to derive quantities from
the entities that cause the quantities in OrderItemShipGrpInvRes to
change.
For example, the Order Items page of the Shipments application bases
the list of items that may be issued to the Shipment on the
OrderItemShipGrpInvRes entity. I think it should be changed to
generate the list based on the joining of the
OrderItemShipGroupAssoc and ItemIssuance entities and only list
those records that have a remaining quantity greater than 0.
OrderItemShipGroupAssoc is only used when the store "Reserve
Inventory" setting is set to "Y" and is the only way to create
itemIssuance records. Without itemIssuances being used there is no
way to ship order items.
On 10/23/2013 03:30 PM, Christian Carlow wrote:
Hey Jacques,
Sorry, using 12.04 stable release.
On 10/23/2013 03:28 PM, Jacques Le Roux wrote:
Which Release.revision?
Though I did not try it recently, I remember it was working in
"old" releases.
Jacques
Christian Carlow wrote:
I was wondering if anyone could tell me whether or not OFBiz's
shipment
capabilities are sophisticated enough to work OOTB or if its
considered
something too buggy to use yet. I've tried creating shipments to
fulfill OrderItem ShipGroup schedules multiple ways and have
encountered
bugs with all of them. The majority of the bugs relate to incorrect
calculation of the OrderItemShipGroupInvRes.
OrderItemShipGroupInvRes
seems to determine what is allowed to be picked, packed and
shipped but
can easily contain incorrect information.
I tried disabling the Reserve Inventory option of the store but this
prevented me from shipping anything. Does Reserve Inventory have
to be
enabled to allow shipment capabilities for orders?
Is anyone using OFBiz OOTB to handle order shipments?
