adding salesOrder data to the BI component

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

adding salesOrder data to the BI component

hans_bakker
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

Reply | Threaded
Open this post in threaded view
|

Re: adding salesOrder data to the BI component

Scott Gray-2
Hi Hans,

I would suggest getting hold of a good data warehousing book before  
starting, making sure that the schemas are well designed will have a  
huge impact on performance and usability going forward.  That aside,  
I'm a big +1 for fleshing out the schemas more and I'll try and find  
some time myself to study up on the topic.

I think Jacopo was using a book that he really liked when he was  
working on BI but I'm not sure what the name of it was.

Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

On 13/11/2009, at 7:19 PM, 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
>


smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: adding salesOrder data to the BI component

Jacopo Cappellato-4
In reply to this post by hans_bakker
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
>

Reply | Threaded
Open this post in threaded view
|

Re: adding salesOrder data to the BI component

hans_bakker
In reply to this post by Scott Gray-2
Yes after Jacopo's presentation last year i ordered the book some time
ago and found it again: The Data Warehouse Toolkit - Second Edition" by
Ralph Kimball.

I have one of my people working on de orderfact entity to be able to
make some birt reports in that area...We will extend the current BI
pattern and follow the naming conventions already there.....

Regards,
Hans

--
Antwebsystems.com: Quality OFBiz services for competitive rates

On Fri, 2009-11-13 at 19:35 +1300, Scott Gray wrote:

> Hi Hans,
>
> I would suggest getting hold of a good data warehousing book before  
> starting, making sure that the schemas are well designed will have a  
> huge impact on performance and usability going forward.  That aside,  
> I'm a big +1 for fleshing out the schemas more and I'll try and find  
> some time myself to study up on the topic.
>
> I think Jacopo was using a book that he really liked when he was  
> working on BI but I'm not sure what the name of it was.
>
> Regards
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com
>
> On 13/11/2009, at 7:19 PM, 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
> >
>
--
Antwebsystems.com: Quality OFBiz services for competitive rates

Reply | Threaded
Open this post in threaded view
|

Re: adding salesOrder data to the BI component

hans_bakker
In reply to this post by Jacopo Cappellato-4
Thank you Jacopo, we will work in that direction...

Regards,
hans

On Fri, 2009-11-13 at 08:43 +0100, 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
> >
>
--
Antwebsystems.com: Quality OFBiz services for competitive rates

Reply | Threaded
Open this post in threaded view
|

Re: adding salesOrder data to the BI component

David E. Jones-2
In reply to this post by Jacopo Cappellato-4

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
>>
>

Reply | Threaded
Open this post in threaded view
|

Re: adding salesOrder data to the BI component

Scott Gray-2
Thanks David I forgot about those, it'll give me something to read  
while I wait for the data warehouse book to arrive :-)

Regards
Scott

On 19/11/2009, at 4:36 PM, David E Jones wrote:

>
> 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
>>>
>>
>


smime.p7s (4K) Download Attachment