Managing the status for non serialized inventory items

[Jacopo Cappellato-3]

Hi all,

I would like to add support for the status for non serialized  
inventory items (right now the status is used only for serialized  
items).
The idea is to add a new status item for "Damaged" inventory (and  
maybe "On Hold" for inventory under inspection); the inventory items  
with this status will be excluded by the inventory counting algorithm  
and also by the inventory reservation service.
The main goal is to add the ability to keep into the warehouse non  
serialized inventory items but don't use them in orders etc... (at  
least until they are fixed), but don't just remove them from the  
system (as it happens when you do a manual inventory variance).

What do you think? Can I go on with this?

Jacopo

[Jacques Le Roux]

Sounds like a good idea : +1

Jacques

From: "Jacopo Cappellato" <[hidden email]>

> Hi all,
>
> I would like to add support for the status for non serialized  
> inventory items (right now the status is used only for serialized  
> items).
> The idea is to add a new status item for "Damaged" inventory (and  
> maybe "On Hold" for inventory under inspection); the inventory items  
> with this status will be excluded by the inventory counting algorithm  
> and also by the inventory reservation service.
> The main goal is to add the ability to keep into the warehouse non  
> serialized inventory items but don't use them in orders etc... (at  
> least until they are fixed), but don't just remove them from the  
> system (as it happens when you do a manual inventory variance).
>
> What do you think? Can I go on with this?
>
> Jacopo
>

[Bilgin Ibryam]

On Wed, 2008-06-04 at 16:56 +0200, Jacques Le Roux wrote:
> Sounds like a good idea : +1
Yes, for me too. +1
Bilgin

[David E Jones]

On Jun 4, 2008, at 8:35 AM, Jacopo Cappellato wrote:

> Hi all,
>
> I would like to add support for the status for non serialized  
> inventory items (right now the status is used only for serialized  
> items).
> The idea is to add a new status item for "Damaged" inventory (and  
> maybe "On Hold" for inventory under inspection); the inventory items  
> with this status will be excluded by the inventory counting  
> algorithm and also by the inventory reservation service.
> The main goal is to add the ability to keep into the warehouse non  
> serialized inventory items but don't use them in orders etc... (at  
> least until they are fixed), but don't just remove them from the  
> system (as it happens when you do a manual inventory variance).
>
> What do you think? Can I go on with this?

It's an interesting idea. Right now all damaged/held/etc inventory is  
treated per unit, ie as serialized inventory. When returns are  
received each item is evaluated individually and tracked that way.

If I understand where you are coming from, this becomes a problem when  
you receive 1000 damaged widgets and would have to create a record for  
each one.

With that in mind, perhaps this might be a good way to make the  
management easier without any data structure change, though there  
could be a number of code changes needed.

-David

[Jacopo Cappellato-3]

On Jun 4, 2008, at 8:13 PM, David E Jones wrote:

>
> On Jun 4, 2008, at 8:35 AM, Jacopo Cappellato wrote:
>
>> Hi all,
>>
>> I would like to add support for the status for non serialized  
>> inventory items (right now the status is used only for serialized  
>> items).
>> The idea is to add a new status item for "Damaged" inventory (and  
>> maybe "On Hold" for inventory under inspection); the inventory  
>> items with this status will be excluded by the inventory counting  
>> algorithm and also by the inventory reservation service.
>> The main goal is to add the ability to keep into the warehouse non  
>> serialized inventory items but don't use them in orders etc... (at  
>> least until they are fixed), but don't just remove them from the  
>> system (as it happens when you do a manual inventory variance).
>>
>> What do you think? Can I go on with this?
>
> It's an interesting idea. Right now all damaged/held/etc inventory  
> is treated per unit, ie as serialized inventory. When returns are  
> received each item is evaluated individually and tracked that way.
>
> If I understand where you are coming from, this becomes a problem  
> when you receive 1000 damaged widgets and would have to create a  
> record for each one.
>

Yes, this is the exactly the scenario I have in mind.
And maybe another one could be this: I have the suspect that the items  
in an inventory item could be damaged and I schedule an inspection...  
in the meantime I want to make sure the items are not reserved for new  
orders; so I change the status to "On Hold" until the inspection is  
done.

Thanks,

Jacopo


> With that in mind, perhaps this might be a good way to make the  
> management easier without any data structure change, though there  
> could be a number of code changes needed.
>
> -David
>
>

[Sumit Pandit-3]

+1


On Jun 5, 2008, at 12:36 AM, Jacopo Cappellato wrote:

>
> On Jun 4, 2008, at 8:13 PM, David E Jones wrote:
>
>>
>> On Jun 4, 2008, at 8:35 AM, Jacopo Cappellato wrote:
>>
>>> Hi all,
>>>
>>> I would like to add support for the status for non serialized  
>>> inventory items (right now the status is used only for serialized  
>>> items).
>>> The idea is to add a new status item for "Damaged" inventory (and  
>>> maybe "On Hold" for inventory under inspection); the inventory  
>>> items with this status will be excluded by the inventory counting  
>>> algorithm and also by the inventory reservation service.
>>> The main goal is to add the ability to keep into the warehouse non  
>>> serialized inventory items but don't use them in orders etc... (at  
>>> least until they are fixed), but don't just remove them from the  
>>> system (as it happens when you do a manual inventory variance).
>>>
>>> What do you think? Can I go on with this?
>>
>> It's an interesting idea. Right now all damaged/held/etc inventory  
>> is treated per unit, ie as serialized inventory. When returns are  
>> received each item is evaluated individually and tracked that way.
>>
>> If I understand where you are coming from, this becomes a problem  
>> when you receive 1000 damaged widgets and would have to create a  
>> record for each one.
>>
>
> Yes, this is the exactly the scenario I have in mind.
> And maybe another one could be this: I have the suspect that the  
> items in an inventory item could be damaged and I schedule an  
> inspection... in the meantime I want to make sure the items are not  
> reserved for new orders; so I change the status to "On Hold" until  
> the inspection is done.
>
> Thanks,
>
> Jacopo
>
>
>> With that in mind, perhaps this might be a good way to make the  
>> management easier without any data structure change, though there  
>> could be a number of code changes needed.
>>
>> -David
>>
>>
>

[Ashish Vijaywargiya]

+1.

On Thu, Jun 5, 2008 at 12:10 AM, Sumit Pandit <[hidden email]>
wrote:

> +1
>
>
>
> On Jun 5, 2008, at 12:36 AM, Jacopo Cappellato wrote:
>
>
>> On Jun 4, 2008, at 8:13 PM, David E Jones wrote:
>>
>>
>>> On Jun 4, 2008, at 8:35 AM, Jacopo Cappellato wrote:
>>>
>>>  Hi all,
>>>>
>>>> I would like to add support for the status for non serialized inventory
>>>> items (right now the status is used only for serialized items).
>>>> The idea is to add a new status item for "Damaged" inventory (and maybe
>>>> "On Hold" for inventory under inspection); the inventory items with this
>>>> status will be excluded by the inventory counting algorithm and also by the
>>>> inventory reservation service.
>>>> The main goal is to add the ability to keep into the warehouse non
>>>> serialized inventory items but don't use them in orders etc... (at least
>>>> until they are fixed), but don't just remove them from the system (as it
>>>> happens when you do a manual inventory variance).
>>>>
>>>> What do you think? Can I go on with this?
>>>>
>>>
>>> It's an interesting idea. Right now all damaged/held/etc inventory is
>>> treated per unit, ie as serialized inventory. When returns are received each
>>> item is evaluated individually and tracked that way.
>>>
>>> If I understand where you are coming from, this becomes a problem when
>>> you receive 1000 damaged widgets and would have to create a record for each
>>> one.
>>>
>>>
>> Yes, this is the exactly the scenario I have in mind.
>> And maybe another one could be this: I have the suspect that the items in
>> an inventory item could be damaged and I schedule an inspection... in the
>> meantime I want to make sure the items are not reserved for new orders; so I
>> change the status to "On Hold" until the inspection is done.
>>
>> Thanks,
>>
>> Jacopo
>>
>>
>>  With that in mind, perhaps this might be a good way to make the
>>> management easier without any data structure change, though there could be a
>>> number of code changes needed.
>>>
>>> -David
>>>
>>>
>>>
>>
>

[Jacques Le Roux]

Hi Jacopo,

Sorry I did no follow closely this thread. Did you commit some related work ?

Thanks

Jacques

Jacopo Cappellato-3 wrote

On Jun 4, 2008, at 8:13 PM, David E Jones wrote:

>
> On Jun 4, 2008, at 8:35 AM, Jacopo Cappellato wrote:
>
>> Hi all,
>>
>> I would like to add support for the status for non serialized  
>> inventory items (right now the status is used only for serialized  
>> items).
>> The idea is to add a new status item for "Damaged" inventory (and  
>> maybe "On Hold" for inventory under inspection); the inventory  
>> items with this status will be excluded by the inventory counting  
>> algorithm and also by the inventory reservation service.
>> The main goal is to add the ability to keep into the warehouse non  
>> serialized inventory items but don't use them in orders etc... (at  
>> least until they are fixed), but don't just remove them from the  
>> system (as it happens when you do a manual inventory variance).
>>
>> What do you think? Can I go on with this?
>
> It's an interesting idea. Right now all damaged/held/etc inventory  
> is treated per unit, ie as serialized inventory. When returns are  
> received each item is evaluated individually and tracked that way.
>
> If I understand where you are coming from, this becomes a problem  
> when you receive 1000 damaged widgets and would have to create a  
> record for each one.
>

Yes, this is the exactly the scenario I have in mind.
And maybe another one could be this: I have the suspect that the items  
in an inventory item could be damaged and I schedule an inspection...  
in the meantime I want to make sure the items are not reserved for new  
orders; so I change the status to "On Hold" until the inspection is  
done.

Thanks,

Jacopo


> With that in mind, perhaps this might be a good way to make the  
> management easier without any data structure change, though there  
> could be a number of code changes needed.
>
> -David
>
>

[Jacopo Cappellato-4]

yes, the code should already be in the trunk

Jacopo


On Sep 25, 2008, at 10:21 PM, jacques.le.roux wrote:

>
> Hi Jacopo,
>
> Sorry I did no follow closely this thread. Did you commit some  
> related work
> ?
>
> Thanks
>
> Jacques
>
>
> Jacopo Cappellato-3 wrote:
>>
>>
>> On Jun 4, 2008, at 8:13 PM, David E Jones wrote:
>>
>>>
>>> On Jun 4, 2008, at 8:35 AM, Jacopo Cappellato wrote:
>>>
>>>> Hi all,
>>>>
>>>> I would like to add support for the status for non serialized
>>>> inventory items (right now the status is used only for serialized
>>>> items).
>>>> The idea is to add a new status item for "Damaged" inventory (and
>>>> maybe "On Hold" for inventory under inspection); the inventory
>>>> items with this status will be excluded by the inventory counting
>>>> algorithm and also by the inventory reservation service.
>>>> The main goal is to add the ability to keep into the warehouse non
>>>> serialized inventory items but don't use them in orders etc... (at
>>>> least until they are fixed), but don't just remove them from the
>>>> system (as it happens when you do a manual inventory variance).
>>>>
>>>> What do you think? Can I go on with this?
>>>
>>> It's an interesting idea. Right now all damaged/held/etc inventory
>>> is treated per unit, ie as serialized inventory. When returns are
>>> received each item is evaluated individually and tracked that way.
>>>
>>> If I understand where you are coming from, this becomes a problem
>>> when you receive 1000 damaged widgets and would have to create a
>>> record for each one.
>>>
>>
>> Yes, this is the exactly the scenario I have in mind.
>> And maybe another one could be this: I have the suspect that the  
>> items
>> in an inventory item could be damaged and I schedule an inspection...
>> in the meantime I want to make sure the items are not reserved for  
>> new
>> orders; so I change the status to "On Hold" until the inspection is
>> done.
>>
>> Thanks,
>>
>> Jacopo
>>
>>
>>> With that in mind, perhaps this might be a good way to make the
>>> management easier without any data structure change, though there
>>> could be a number of code changes needed.
>>>
>>> -David
>>>
>>>
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Managing-the-status-for-non-serialized-inventory-items-tp17648284p19677568.html
> Sent from the OFBiz - Dev mailing list archive at Nabble.com.
>

[Jacques Le Roux]

Thanks

 

Jacques

----- Original Message -----

From: [hidden email]

To: [hidden email]

Sent: Monday, October 12, 2009 2:17 PM

Subject: Re: Managing the status for non serialized inventory items

yes, the code should already be in the trunk

Jacopo


On Sep 25, 2008, at 10:21 PM, jacques.le.roux wrote:

>
> Hi Jacopo,
>
> Sorry I did no follow closely this thread. Did you commit some  
> related work
> ?
>
> Thanks
>
> Jacques
>
>
> Jacopo Cappellato-3 wrote:
>>
>>
>> On Jun 4, 2008, at 8:13 PM, David E Jones wrote:
>>
>>>
>>> On Jun 4, 2008, at 8:35 AM, Jacopo Cappellato wrote:
>>>
>>>> Hi all,
>>>>
>>>> I would like to add support for the status for non serialized
>>>> inventory items (right now the status is used only for serialized
>>>> items).
>>>> The idea is to add a new status item for "Damaged" inventory (and
>>>> maybe "On Hold" for inventory under inspection); the inventory
>>>> items with this status will be excluded by the inventory counting
>>>> algorithm and also by the inventory reservation service.
>>>> The main goal is to add the ability to keep into the warehouse non
>>>> serialized inventory items but don't use them in orders etc... (at
>>>> least until they are fixed), but don't just remove them from the
>>>> system (as it happens when you do a manual inventory variance).
>>>>
>>>> What do you think? Can I go on with this?
>>>
>>> It's an interesting idea. Right now all damaged/held/etc inventory
>>> is treated per unit, ie as serialized inventory. When returns are
>>> received each item is evaluated individually and tracked that way.
>>>
>>> If I understand where you are coming from, this becomes a problem
>>> when you receive 1000 damaged widgets and would have to create a
>>> record for each one.
>>>
>>
>> Yes, this is the exactly the scenario I have in mind.
>> And maybe another one could be this: I have the suspect that the  
>> items
>> in an inventory item could be damaged and I schedule an inspection...
>> in the meantime I want to make sure the items are not reserved for  
>> new
>> orders; so I change the status to "On Hold" until the inspection is
>> done.
>>
>> Thanks,
>>
>> Jacopo
>>
>>
>>> With that in mind, perhaps this might be a good way to make the
>>> management easier without any data structure change, though there
>>> could be a number of code changes needed.
>>>
>>> -David
>>>
>>>
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Managing-the-status-for-non-serialized-inventory-items-tp17648284p19677568.html
> Sent from the OFBiz - Dev mailing list archive at Nabble.com.
>

---

View message @ http://n4.nabble.com/Managing-the-status-for-non-serialized-inventory-items-tp193584p193588.html
To unsubscribe from Re: Managing the status for non serialized inventory items, click here.