On Dec 1, 2006, at 12:36 PM, Si Chen 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
So then once you call createFixedAsset, the general ledger posting
magic happens.
The really interesting thing is what kind of accounting are you
planning to do once the fixed assets are created?
On Nov 29, 2006, at 11:41 AM, David Zelaya Herrera wrote:
Hi Si,
I think what you must have done is created an association between the
FixedAsset and Product using the Accounting > Fixed Asset >>
Products
tab. In this case, however, I think those screens are for
maintaining rental calendar of a fixed asset, like a hotel room. In
fact, the section in OrderServices where you got your crash looks
like something Hans wrote.
Yes, you are rigth.
I think looking at it, it is possible as David Jones said, to create
a PO with a fixed asset product. Where we're missing though is that
this fixed asset needs to be able to be received as a fixed asset
and
commissioned as a fixed asset, rather than received as inventory
right now. That's the big piece we're missing--we should probably
have some kind of a routine to create FixedAsset from OrderItem
which
are of the "Fixed Asset" type.
I agree with you. Also we have to think in others kinds of PO..
for eg. if I
contract a service like "Information Technology Service".. the
product type
must to be "Services" and the OrderItem type too, and of course
this kind of
PO dont have reception.. just a confirmation that the service was
done.
I think that the accounting of these could work like this:
(event) when createShipmentReceipt run and OrderItem type is "PO:
Inventory"
(action) postShipmentReceiptToGl
(event) when createShipmentReceipt run and OrderItem type is "PO:
FixedAsset"
(action) postFixedAssetReceiptToGl
(event) when ... and the OrderItem type is "Services"
(action) postServiceConfirmToGl
--
Best Regards,
David Zelaya Herrera
Best Regards,
Si
[EMAIL PROTECTED]
