BEx query - Infoview - obbligation add a mesure

[Former Member]

Hi to all,

could you please explain me why if a create a new infoview report with two or more caracteristics I MUST add a mesure in order to have the correct result.

In fact I have selected the following characteristics (dimensions) in my infoview query:

- Customer ID

- ZIp code

And I filter the "Customer ID" field in order to fix only one record(eq Customer ID = 000001)

The result set is the following

cust ID ZIP

-

---

000001 1

000001 2

000001 3

000001 4

000001 5

000001 6

... ...

It looks like a strange "cartesian product". It seems that the same customer Id is repeted the exact number of the row retriveid by me BEX query.

Could you please explain me this behaviour ?

Thank'you very much!

[Former Member · Accepted solution]

Unfortunately it's by design.

I'd say that without a measure (the fact table or pseudo fact if you're reporting on an infoobject/DSO) it can't relate two dimensions and so creates a carthesian product.

[Former Member · Accepted solution]

Thank'you very much!

So if I understood correctly when I read an ODS with a Bex query I didn't use two caracteristics without a measure because the Bex query will see these as two dimensions of a cube.

But my new question is : Can I force or allow the BEX query to read an ODS and not a cube ?

Indeed an ODS is a plan table without the dimentions tables...

Thank'you in advance !

[IngoH · Accepted solution]

Hi,

so are you trying to link an ODS with data from a cube ?

ingo

[Former Member · Accepted solution]

No, I'm trying to create a query bex onto a DSO in order to extract the wide data.

Actually my problem is a cartesian product between two dimensions selected in the infoview pannel.

But if i understood correctly this behavior is due to the fact that the query bex see the dso like a cube and then the two carateristics are associate to an hypotetic start schema, where the cartesian product will be correct.

Therefore my idea is: can i force the query bex to understand that the source date is not a cube but is a dso and than the two caracteristics are not two dimensions of a star schema but they are two fields of a plano table?

Thank'you very much!

[IngoH · Accepted solution]

Hi,

No, I'm trying to create a query bex onto a DSO in order to extract the wide data.

Actually my problem is a cartesian product between two dimensions selected in the infoview pannel.

>>> a BEx query is not an ETL Tool !

Are you trying to do actual reporting on top of the DSO or is this really related to ETL ?

Ingo

[Former Member · Accepted solution]

Hi,

yes I'm trying to create a report very simple in order to understand an caractheristic of a customer.

Indeed in my query filter of my infoview I select the interesting customer.

I attempt only one line as a result.

but when the query runs I have more than one records...so because there is a cartesian product between my two dimension.

Do you think that this is a restriction or bug of the query bex / integration of bo with bw ?

Thank'you in advance.

[Former Member]

Yep you can do that.

To access ODS/DSO or Multiprovider or Infoset & Infocube(Navigational attributes) one has to design BEx query on top of it.

Create BEx query on top of ODS/DSO and check "Allow External Access" Enabled.

(BW3.x ==>> properties ==>> Extended tab)

(BI7.0 ==>> Properties ==>> Advanced tab)

Hope it helps you.

Thank You!!

Sent from iPhone

[Former Member]

Yes, I do already it. But my problem persist?

Do you think that there is another solution?

[Former Member]

Obviously, it's correct only.

COZ without numerical info none of Report/ Business make sense. As per Characteristics defined in cube, it's relating data and showing data as it has no fact/numeric info.

Did you check data at BEx by taking same objects?? and how abt data??

Thank You!!

Sent from iPhone