Voyager with SAPBW

[Former Member]

Dear All,

I am trying to access SAPBW from Voyager workspace in Infoview. I have created a voyager conn in CMC in XI 3.0.

The problem is when I connect to SAPBW from Voyager & drag the objects I am not able to see any data..Can anyone please tell me what is the issue here ?

[IngoH · Accepted solution]

Hi,

could you perhaps describe it in a little bit more details what you see ?

thanks

Ingo

[Former Member · Accepted solution]

Actually I am able to view the object in the Data tab metadata explorer(left hand side).

BUT i am not able to view the actual data in Crosstab component reference(right hand side)

Hope this is clear & please let me know about this..

[former_member192142 · Accepted solution]

Hi,

Have you remembered to drag in characteristics (dimensions) as well as key figures (measures) in the rows, columns and body of you workspace?. The result is not displayed in your workspace until you have.

Best regards,

Jacob

[IngoH · Accepted solution]

Hi mb,

so what is it that you see when you drag a characteristic to the rows and some keyfigures to the columns ?

thanks

ingo

[Former Member · Accepted solution]

When I drag the objects I see nothing(no data). I am still figuring out why the data is not displaying.....

[Former Member · Accepted solution]

I am having a similar problem. I am running Edge Professional and my steps are this:

From DocumentList in InfoView, I select New > Voyager Workspace

When the "Choose Connection" screen appears, I select a connection I have configured to SAP BW.

From the data tab I drag a dimension as a column (e.g. Country) and then another as a row (e.g. Material) and then select a measure (e.g. Invoice Amount).

After I've done this, both the row and column headings say "No member with data" instead of the actual data.

I'm just not sure if this is a) a problem with the BW data, b) a problem with the connection, or c) a problem with the way I'm building the query in voyager.

[IngoH · Accepted solution]

HI MB, Matt,

can both of you see the data when executing the BI query in BEx Analyzer ?

Do you have Crystal Reports available as well ?

thanks

Ingo

[Former Member · Accepted solution]

ingo,

I have the same issue with Voyager. SAP BI query is fine (executing in BEx)... I tried hooking to a cube instead of a query and same.. I can see meta data but when I drag and drop - nothing shows up.

thanks

bala

[IngoH · Accepted solution]

hi MR,

any updates here ?

ingo

[Former Member · Accepted solution]

Thanks for the reply.

I cannot see the data in BEx Analyzer, so I am working with our SAP BI people to make sure the data is setup properly in BW. I will post an update once I can establish this, and then hopefully the source of the problem will be narrowed down.

[Former Member · Accepted solution]

Hi,

A very simple way to validate whether the issue is on the BI vs. Voyager side is to go to transaction MDXTEST and look up your query then either use existing MDX statement if you have one or generate a sample statement which is an option offered by this tool to verify if any data is returned.

Additionally, you can browse through the members of a specific characteristic at level 01 or hierarchy to validate if your members are returned correctly through the MDX parser which is the same layer voyager is utilizing.

thanks

Mike

[Former Member · Accepted solution]

Hi Mike,

Thanks for the advice. I ran a statement in MDXTEST and got no results against that cube. I have already confirmed that in fact there is data in the cube, so I suppose this points to BI as the root of the problem.

I'm not an SAP BI expert by any means, so I am going to reach out to our BI team for some answers.

[Former Member · Accepted solution]

Hi,

Could you try to check in SM59 if RFC destination 'MDX PARSER' is working fine ?

Best Regards,

Olivier

[IngoH · Accepted solution]

Hi,

here a list of items in priority order that I would check:

- check the BI query with BEx Analayzer to see if you receive data

- try the same in transaction RSRT

If those return data try to run a simple MDX statement in transaction MDXTEST.

in case those do not return data should already receive more detailed error messages.

Ingo