Reserving a specific serialized inventory item

[Bob Morley]

We have an order entry screen that allows the Sales Rep to select a specific serial number for a serialized piece of inventory.  The reservation process must honor this selection and reserve that piece (if possible) or produce a reasonable error message.

Question lead in -- if the inventory item is known up-front, most of the hub-bub around figuring out proper facilities and then applying LIFO/FIFO/etc and going through primary/pick locations is not required.  It appears while this is being done, "reserveForInventoryItemInline" is called (in a loop) which updates the InventoryItem OR creates an InventoryItemDetail and calls "reserveOrderItemInventory" which creates a OrderItemShipGrpInvRes entity.

Question -- as part as reserving inventory is this it?  (Ignoring ECAs for quantity thresholds and such).

If this is the case, my solution is going to be (as part of order create/update) avoid calling the whole reserveInventory chain, and call a new new service that simply calls reserveForInventoryItemInline (with appropriate parms).  This would be in situations where the ShoppingCartItem has the inventoryItemId specified.

Anyone see any flaws in this approach?  Also, has anyone else had this type of thing to do before?  I took a brief look at the POS implementation and this type of logic does not seem to be in place yet.  It would seem to me that it would be important for the POS that they sell the actual product the customer brings to the counter.  Serialized by serialNumber and Non-Serialized by location (either directly or indirectly).

[Jacques Le Roux]

Hi Bob,

Did you pursue on this way ? If yes would you have something to contribute that could be used by the POS ?

Jacques

From: "Bob Morley" <[hidden email]>

>
> We have an order entry screen that allows the Sales Rep to select a specific
> serial number for a serialized piece of inventory.  The reservation process
> must honor this selection and reserve that piece (if possible) or produce a
> reasonable error message.
>
> Question lead in -- if the inventory item is known up-front, most of the
> hub-bub around figuring out proper facilities and then applying
> LIFO/FIFO/etc and going through primary/pick locations is not required.  It
> appears while this is being done, "reserveForInventoryItemInline" is called
> (in a loop) which updates the InventoryItem OR creates an
> InventoryItemDetail and calls "reserveOrderItemInventory" which creates a
> OrderItemShipGrpInvRes entity.
>
> Question -- as part as reserving inventory is this it?  (Ignoring ECAs for
> quantity thresholds and such).
>
> If this is the case, my solution is going to be (as part of order
> create/update) avoid calling the whole reserveInventory chain, and call a
> new new service that simply calls reserveForInventoryItemInline (with
> appropriate parms).  This would be in situations where the ShoppingCartItem
> has the inventoryItemId specified.
>
> Anyone see any flaws in this approach?  Also, has anyone else had this type
> of thing to do before?  I took a brief look at the POS implementation and
> this type of logic does not seem to be in place yet.  It would seem to me
> that it would be important for the POS that they sell the actual product the
> customer brings to the counter.  Serialized by serialNumber and
> Non-Serialized by location (either directly or indirectly).
> --
> View this message in context: http://www.nabble.com/Reserving-a-specific-serialized-inventory-item-tp25208526p25208526.html
> Sent from the OFBiz - Dev mailing list archive at Nabble.com.
>

[Bob Morley]

Hi Jacques,

What I ended up doing was creating a new service that could call the inline service to perform a specific inventory item reservation.  This could theoretically be used whenever the sales rep selects a specific inventory item, but in our sales order entry it is only used for serialized inventory.  I could contribute back this service and I could look at retrofitting the serialized inventory selection into either webpos or pos if you think there is value.

Let me know which direction you would like me to take.

jacques.le.roux wrote

Hi Bob,

Did you pursue on this way ? If yes would you have something to contribute that could be used by the POS ?

Jacques

From: "Bob Morley" <[e-mail]>
>
> We have an order entry screen that allows the Sales Rep to select a specific
> serial number for a serialized piece of inventory.  The reservation process
> must honor this selection and reserve that piece (if possible) or produce a
> reasonable error message.
>
> Question lead in -- if the inventory item is known up-front, most of the
> hub-bub around figuring out proper facilities and then applying
> LIFO/FIFO/etc and going through primary/pick locations is not required.  It
> appears while this is being done, "reserveForInventoryItemInline" is called
> (in a loop) which updates the InventoryItem OR creates an
> InventoryItemDetail and calls "reserveOrderItemInventory" which creates a
> OrderItemShipGrpInvRes entity.
>
> Question -- as part as reserving inventory is this it?  (Ignoring ECAs for
> quantity thresholds and such).
>
> If this is the case, my solution is going to be (as part of order
> create/update) avoid calling the whole reserveInventory chain, and call a
> new new service that simply calls reserveForInventoryItemInline (with
> appropriate parms).  This would be in situations where the ShoppingCartItem
> has the inventoryItemId specified.
>
> Anyone see any flaws in this approach?  Also, has anyone else had this type
> of thing to do before?  I took a brief look at the POS implementation and
> this type of logic does not seem to be in place yet.  It would seem to me
> that it would be important for the POS that they sell the actual product the
> customer brings to the counter.  Serialized by serialNumber and
> Non-Serialized by location (either directly or indirectly).
> --
> View this message in context: http://www.nabble.com/Reserving-a-specific-serialized-inventory-item-tp25208526p25208526.html
> Sent from the OFBiz - Dev mailing list archive at Nabble.com.
>

[Jacques Le Roux]

Hi Bob,

Yes please, as you initially mentioned, this would be really a plus for the POS

Thanks

Jacques

From: "Bob Morley" <[hidden email]>

>
> Hi Jacques,
>
> What I ended up doing was creating a new service that could call the inline
> service to perform a specific inventory item reservation.  This could
> theoretically be used whenever the sales rep selects a specific inventory
> item, but in our sales order entry it is only used for serialized inventory.
> I could contribute back this service and I could look at retrofitting the
> serialized inventory selection into either webpos or pos if you think there
> is value.
>
> Let me know which direction you would like me to take.
>
>
> jacques.le.roux wrote:
>>
>> Hi Bob,
>>
>> Did you pursue on this way ? If yes would you have something to contribute
>> that could be used by the POS ?
>>
>> Jacques
>>
>> From: "Bob Morley" <[hidden email]>
>>>
>>> We have an order entry screen that allows the Sales Rep to select a
>>> specific
>>> serial number for a serialized piece of inventory.  The reservation
>>> process
>>> must honor this selection and reserve that piece (if possible) or produce
>>> a
>>> reasonable error message.
>>>
>>> Question lead in -- if the inventory item is known up-front, most of the
>>> hub-bub around figuring out proper facilities and then applying
>>> LIFO/FIFO/etc and going through primary/pick locations is not required.
>>> It
>>> appears while this is being done, "reserveForInventoryItemInline" is
>>> called
>>> (in a loop) which updates the InventoryItem OR creates an
>>> InventoryItemDetail and calls "reserveOrderItemInventory" which creates a
>>> OrderItemShipGrpInvRes entity.
>>>
>>> Question -- as part as reserving inventory is this it?  (Ignoring ECAs
>>> for
>>> quantity thresholds and such).
>>>
>>> If this is the case, my solution is going to be (as part of order
>>> create/update) avoid calling the whole reserveInventory chain, and call a
>>> new new service that simply calls reserveForInventoryItemInline (with
>>> appropriate parms).  This would be in situations where the
>>> ShoppingCartItem
>>> has the inventoryItemId specified.
>>>
>>> Anyone see any flaws in this approach?  Also, has anyone else had this
>>> type
>>> of thing to do before?  I took a brief look at the POS implementation and
>>> this type of logic does not seem to be in place yet.  It would seem to me
>>> that it would be important for the POS that they sell the actual product
>>> the
>>> customer brings to the counter.  Serialized by serialNumber and
>>> Non-Serialized by location (either directly or indirectly).
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Reserving-a-specific-serialized-inventory-item-tp25208526p25208526.html
>>> Sent from the OFBiz - Dev mailing list archive at Nabble.com.
>>>
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Reserving-a-specific-serialized-inventory-item-tp25208526p25436435.html
> Sent from the OFBiz - Dev mailing list archive at Nabble.com.
>