David,

So what do you think would be the best approach for creating a fixed asset after a PO is approved? Should there be a link to receive the fixed asset, as opposed to receive inventory, which causes the fixed asset to be created?

On Dec 3, 2006, at 12:56 AM, David E Jones wrote:


David,

I just read David's post http://lists.ofbiz.org/pipermail/dev/2006- May/011004.html and your posting and I think I would suggest something a little different. The different OrderItemTypes for product vs fixed asset vs service is a good idea, but it should not be presented to the user. Rather, it should be possible to set up a Product as a "Fixed Asset", "Finished Good", and "Service", and the storeOrder service should figure out correct OrderItemType for it. During order creation (shopping cart) any order item is like any other order item, but then when the order is created the different types are stored.


Why the groups "Fixed Asset", "Finished Good", and "Service"? What would those mean? I guess I'm confused because it seems like an arbitrary selection of ProductTypes and other general stuff. A FixedAsset is (or can be) an instance of a Product, which can have a type of "Finished Good", for example.


Then, when the order is created, depending on the different types of order items, you can 1) receive inventory or ship inventory (physical products) 2) automatically fulfill for digital products-- already implemented, you can start your own iTunes with ofbiz 3) commission a fixed asset item if it's a fixed asset order item and 4) create a workeffort if it's a service item


Here again this is kind of a funny mix of things, and I'm not sure what sort of process you have in mind. There are generally different processes for different things, and these can of course vary by the company. Purchases and sales are obviously different too. For service sales you could trigger creation of a WorkEffort, but for many companies that plan and quote before they sell the WorkEffort would already exist, for example.

-David

Best Regards,

Si
[EMAIL PROTECTED]



Reply via email to