Another good resource is the good old Data Model Resource Books. In
addition to the operational/transactional schemas ideas that we
obviously use a lot they have some good analytical models and they use
the same star schema patterns (facts and dimensions and what what) as
this data warehouse toolkit book.
-David
On Nov 13, 2009, at 12:43 AM, Jacopo Cappellato wrote:
Hans,
first of all: it is great that you are interested on enhancing the
star schemas and dimensions; also using Birt on top of them will be
a great way of using them.
I would really suggest the following book:
http://www.amazon.com/gp/product/0471200247
If you can get it (or a digital copy of it) you will appreciate the
way it is written; I can also help to point you to the most
important sections to speed up.
BTW, regarding sales orders:
1) I would suggest to implement the new star schema (and supporting
eca/services) for sales orders in the "order" component
(org.ofbiz.bi.starschema.order)
2) the start schema could be based on the schema described in the
book at page 116;
2.1) its name could be SalesOrderItemFact and its field could be:
orderId*, orderItemSeqId*, dateDimensionId, productDimentionId,
currencyDimensionId, orderQuantity, grossOrderTotalAmount,
orderDiscountDollarAmount, netOrderDollarAmount
Let me know if I can help more, I would be happy to.
Jacopo
On Nov 13, 2009, at 7:19 AM, Hans Bakker wrote:
for example we like to see which sales oriented data: which orders
where made through promotions,
which orders are back-ordered etc...
should be start a org.ofbiz.bi.starschema.salesOrders next to
org.ofbiz.bi.starschema.accounting?
are there any rules to follow?
The reason for all this: using birt to do sales reporting.....
--
Antwebsystems.com: Quality OFBiz services for competitive rates
