entity-extend or create a new entity

[Yasin Lyyas]

Hi all,

I have a dilemma here with product cost. As we know that we keep the
information about product cost in InventoryItem. But, I cannot really
use the product cost from InventoryItem, since the cost there is not
quite correct for some InventoryItem. Users sometimes typed in a wrong
number or that kind of actions. What I need is a "Master product cost"
somewhere which is related to Product. So, which way is better,
extending the existing entity (Product), or create an entirely new
entity to hold Product_id and cost? Any suggestion?


Thanks

Lyyas
Yasin

[Kirti-3]

Hello Yasin,

I want to suggest you to just extend the entity in your custom
application to fulfill your needs instead of creating a new entity.
I also want to suggest you to go through below link it will helpful to you.
http://docs.ofbiz.org/display/OFBIZ/OFBiz+Beginner%27s+Development+Guide+Using+Practice+Application

Thanks & Regards
Kirti Dhakad
Hotwax Media Pvt. Ltd.


yasin lyyas wrote:

> Hi all,
>
> I have a dilemma here with product cost. As we know that we keep the
> information about product cost in InventoryItem. But, I cannot really
> use the product cost from InventoryItem, since the cost there is not
> quite correct for some InventoryItem. Users sometimes typed in a wrong
> number or that kind of actions. What I need is a "Master product cost"
> somewhere which is related to Product. So, which way is better,
> extending the existing entity (Product), or create an entirely new
> entity to hold Product_id and cost? Any suggestion?
>
>
> Thanks
>
> Lyyas
> Yasin
>
>  

[David E Jones]

The CostComponent and related entities might be helpful.

-David


On Oct 24, 2008, at 3:56 AM, yasin lyyas wrote:

> Hi all,
>
> I have a dilemma here with product cost. As we know that we keep the
> information about product cost in InventoryItem. But, I cannot really
> use the product cost from InventoryItem, since the cost there is not
> quite correct for some InventoryItem. Users sometimes typed in a wrong
> number or that kind of actions. What I need is a "Master product cost"
> somewhere which is related to Product. So, which way is better,
> extending the existing entity (Product), or create an entirely new
> entity to hold Product_id and cost? Any suggestion?
>
>
> Thanks
>
> Lyyas
> Yasin
>

[Jaquelynn.T]

Hi Lyyas,

The best way in my opinion is to create an entirely new entity, if the current one has too many faults in it.

Regards,

Jaquelynn.T

yasin lyyas wrote

Hi all,

I have a dilemma here with product cost. As we know that we keep the
information about product cost in InventoryItem. But, I cannot really
use the product cost from InventoryItem, since the cost there is not
quite correct for some InventoryItem. Users sometimes typed in a wrong
number or that kind of actions. What I need is a "Master product cost"
somewhere which is related to Product. So, which way is better,
extending the existing entity (Product), or create an entirely new
entity to hold Product_id and cost? Any suggestion?


Thanks

Lyyas
Yasin

[BJ Freeman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

also the product pricing is done in
https://demo.hotwaxmedia.com/catalog/control/EditProductPrices?productId=GZ-1000
where inventory is done
https://demo.hotwaxmedia.com/catalog/control/EditProductInventoryItems?productId=GZ-1000&showAllFacilities=Y


Jaquelynn.T sent the following on 1/20/2009 10:42 AM:

> Hi Lyyas,
>
> In my opinion, the best way to solve this problem is to make sure that you
> have a working Master Product Cost.
> If you already have a wrong Product Cost because of the wrong data input in
> the Inventory Item, then the Inventory Item is of no good use. You should
> make sure you correct all the data first, as this is the main root of your
> problem.
> Still using it will give you a bigger problem in the future, and it is also
> not the customer's fault since the cost there is not correct. That way the
> customer will put in the value just like what it is written there.
> Extending the product line will cause more trouble in the future.
> What you should do is try to filter down and set aside the ones that has
> wrong input. And correct it.
> Or reset the whole data and create a new one which is satisfactory and will
> not cause anymore trouble in the future.
> When you are making a new one make sure that it is easy to use and easy to
> understand for the whole employee and customer.
>
> Best Regards,
>
> Jaquelynn.T
>
>
> yasin lyyas wrote:
>> Hi all,
>>
>> I have a dilemma here with product cost. As we know that we keep the
>> information about product cost in InventoryItem. But, I cannot really
>> use the product cost from InventoryItem, since the cost there is not
>> quite correct for some InventoryItem. Users sometimes typed in a wrong
>> number or that kind of actions. What I need is a "Master product cost"
>> somewhere which is related to Product. So, which way is better,
>> extending the existing entity (Product), or create an entirely new
>> entity to hold Product_id and cost? Any suggestion?
>>
>>
>> Thanks
>>
>> Lyyas
>> Yasin
>>
>>
>>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD4DBQFJdh7trP3NbaWWqE4RAo71AJ44pF67AEVOkWVsv3SFYSe2u2nw4ACVGyun
gzaCOPDPS0WFrGcLADKmKQ==
=D3yL
-----END PGP SIGNATURE-----

[BJ Freeman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

https://demo.hotwaxmedia.com/catalog/control/EditProductCosts?productId=GZ-1000
is where you set up costs of the product. you will note you can actually
 enter a cost figure.
Note it is the services and SECAS that tie the inventory, Cost, and
product cost together.


Jaquelynn.T sent the following on 1/20/2009 10:53 AM:

> Hi Lyyas,
>
> The best way in my opinion is to create an entirely new entity, if the
> current one has too many faults in it.
>
> Regards,
>
> Jaquelynn.T
>
>
> David E Jones wrote:
>>
>> The CostComponent and related entities might be helpful.
>>
>> -David
>>
>>
>> On Oct 24, 2008, at 3:56 AM, yasin lyyas wrote:
>>
>>> Hi all,
>>>
>>> I have a dilemma here with product cost. As we know that we keep the
>>> information about product cost in InventoryItem. But, I cannot really
>>> use the product cost from InventoryItem, since the cost there is not
>>> quite correct for some InventoryItem. Users sometimes typed in a wrong
>>> number or that kind of actions. What I need is a "Master product cost"
>>> somewhere which is related to Product. So, which way is better,
>>> extending the existing entity (Product), or create an entirely new
>>> entity to hold Product_id and cost? Any suggestion?
>>>
>>>
>>> Thanks
>>>
>>> Lyyas
>>> Yasin
>>>
>>
>>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJdiCxrP3NbaWWqE4RAqshAJ4wvKSwqeiNp5OGn8pb8xGtCQ9E+QCcDRxl
q9plwG90kwQ2eIP2x5MIGJk=
=0zvK
-----END PGP SIGNATURE-----

[BJ Freeman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

if prices are changed, they are kept the price change enitiy
https://demo.hotwaxmedia.com/webtools/control/FindGeneric?entityName=ProductPriceChange&find=true&VIEW_SIZE=50&VIEW_INDEX=0
so you can revert if a price is changed mistakenly

BJ Freeman sent the following on 1/20/2009 10:58 AM:

> also the product pricing is done in
> https://demo.hotwaxmedia.com/catalog/control/EditProductPrices?productId=GZ-1000
> where inventory is done
> https://demo.hotwaxmedia.com/catalog/control/EditProductInventoryItems?productId=GZ-1000&showAllFacilities=Y
>
>
> Jaquelynn.T sent the following on 1/20/2009 10:42 AM:
>> Hi Lyyas,
>
>> In my opinion, the best way to solve this problem is to make sure that you
>> have a working Master Product Cost.
>> If you already have a wrong Product Cost because of the wrong data input in
>> the Inventory Item, then the Inventory Item is of no good use. You should
>> make sure you correct all the data first, as this is the main root of your
>> problem.
>> Still using it will give you a bigger problem in the future, and it is also
>> not the customer's fault since the cost there is not correct. That way the
>> customer will put in the value just like what it is written there.
>> Extending the product line will cause more trouble in the future.
>> What you should do is try to filter down and set aside the ones that has
>> wrong input. And correct it.
>> Or reset the whole data and create a new one which is satisfactory and will
>> not cause anymore trouble in the future.
>> When you are making a new one make sure that it is easy to use and easy to
>> understand for the whole employee and customer.
>
>> Best Regards,
>
>> Jaquelynn.T
>
>
>> yasin lyyas wrote:
>>> Hi all,
>>>
>>> I have a dilemma here with product cost. As we know that we keep the
>>> information about product cost in InventoryItem. But, I cannot really
>>> use the product cost from InventoryItem, since the cost there is not
>>> quite correct for some InventoryItem. Users sometimes typed in a wrong
>>> number or that kind of actions. What I need is a "Master product cost"
>>> somewhere which is related to Product. So, which way is better,
>>> extending the existing entity (Product), or create an entirely new
>>> entity to hold Product_id and cost? Any suggestion?
>>>
>>>
>>> Thanks
>>>
>>> Lyyas
>>> Yasin
>>>
>>>
>>>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJdjqDrP3NbaWWqE4RAtaiAKCKSjqgrPGA7h0UDmYW8WgLUzdDLACgz3JT
3GywAIRSESDRtTPPOCs/oqk=
=4rdv
-----END PGP SIGNATURE-----