Monday, May 20, 2013

SAP BusinessObjects BI 4.1 Release to Customers

Just before the SAPPHIRE NOW conference, SAP announced the Release to Customer (RTC) of SAP BusinessObjects BI 4.1, Edge BI 4.1 and Crystal Server 2013.

Read here about all the new features in this version:





Monday, January 14, 2013

Lifecycle Manager Overrides in BI4

A good article I read today explaining the difficulties using promotion management

 (former known as life cycle management ) in BI4 platform :
 
you can also read here a in general but the bugs aren't mentioned :
 

How SAP BW and HANA will merge over time -- and why it matters

Read the first of this two-part series on SAP Business Warehouse and HANA. Part one addresses how companies should consider their data management needs when assessing the technologies.
 
 

Wednesday, November 21, 2012

Sneak Peek of SAP BusinessObjects Dashboards 4.0 SP5

What's new in  BusinessObjects Dashboards 4.0 SP5 ?
 
"Dashboards 4.0 SP05 (formerly Xcelsius) will support iPad only in the first release. Publish your dashboard to the SAP BusinessObjects business intelligence platform and then download or run it on your iPad using SAP BusinessObjects Mobile. We may support other tablets in future releases..."
 
 
Get a Sneak Peek of SAP BusinessObjects Dashboards 4.0 SP5: How to Mobilize Your Dashboards
 
 

What’s new in SAP BusinessObjects 4.0 SP5...

Whats's new in BI4 platform ,SP5 ?
 
Read here strating from page 81:
 

Sunday, November 11, 2012

Exists or not exists- that is the answer


Using more complex queries that can answer simple question like who bought product A but didn't bought product B? Or in another Case: which customers from the customer’s table don’t have an order in the order table ,is one of the abilities that we would like to give for the users and allow them to use it simply and freely as we can.

In order to do that we can use in some cases the sub query method which is good and solid, but in some cases using the Exist \ not exist would be better.
And why is that?

There are first of all performance differences that makes the exists operator make a better work of evaluating which is the driving table and by doing so , use in some cases the appropriate index ,there is also the ability to work with nulls.
For a better understanding of the differences between Exists and subquery read here:





Using the Island resort we will use the Customer and the Sales tables in order to answer a simple question:

Who are the customers who haven’t paid so far?

  1. first we will build the following predefined condition using this syntax:



SELECT Customer.cust_id
FROM Customer

WHERE NOT EXISTS

(select Sales.cust_id from Sale where Customer.cust_id=Sales.cust_id)





  1. We will create a simple query that returns the customers ID’s :

  1. The result will be getting just those customers who don’t have any invoice :