As i am aware, you can hit a BW Infocube directly from Reporter using the access licenses or directly from Designer.
Are there additional ways to report against an Infocube?
Can someone share same documentation or previous experience in working with Designer on the cube directly?
Hi
I have a question on SAP B/W. Currently, our company is using SAP B/W cubes for our backend. I wanted to create a universe in xi r2. I was able to install the SAP Integration kit (Adapter) which i assume would connect sap cubes to the universe. When i created the universe though, the classes and objects were generated in the universe but it seems they are all disabled. Also i seem to have no access rights whatsoever. I do not know if i am doing something wrong or there is really a limitation of using cubes for BO XI.
It means that we have probably found the problem smile. To truly take advantage of the SAP Integration Kit, there is BusObj code that must be loaded in your SAP environment. Moving things into an SAP environment is called a transport. Look at the readme / installation information that came with the SAP Integration Kit for details.
I am sure you know that in SAP the word transport means the moving of a customization or query object between the different instances in the landscape (DEV, QA and PROD), and it’s not related whatsoever to the data itself. That’s why the “transport” error BO displays is in my opinnion misleading. I now understand that some code needs to be loaded to the BW instance and then “transported”.
Regarding your comment.
“To truly take advantage of the SAP Integration Kit, there is BusObj code that must be loaded in your SAP environment.” . Does this (file? /code) include in the sap integration kit that was installed? How is this implemented ? Would this solve the unaccesible universe?
The bits to be transported are included on the installation media, and are listed specifically in the readme / installation guides. I wasn’t involved with the transports myself when we did some high-level testing, but I do remember my technical folks having a fit getting the correct privileges set up on the SAP side.
Some background. Yes, there are more generic ways of communicating with SAP. The term ODBO comes to mind, but I might be wrong. In any case, these “generic” methods are terribly inefficient. Unusable would be a more accurate term for all but the simplest applications.
Now enter Crystal. Even before Business Objects’ purchase of Crystal Decisions, some version of Crystal was embedded in SAP. Translation, a deeper knowledge of the SAP inner workings, and the ability to develop a more optimized way to communicate, using native SAP BAPIs, etc. That “inside” knowledge has evolved into the SAP Integration Kit, and also helps understand why code has to be loaded on the SAP side to take best advantage.
I’ve now reached the end of my expertise (ahem) on the SAP Integration Kit. Feel free to post follow up questions, but I’m pretty sure someone else will have to answer them .
In the installation guide for the SAP integration kit, it didn’t specify if I needed to do the transports to build universes using the BW Universe Builder. Most of the guide seems to talk about hitting the cubes directly or off infosets & queries. Has anyone had experience building universes from BW infocubes? Are the SAP transports really required to be able to build a universe off SAP BW?
There are two sets of transport files, which can be used with BusinessObjects Enterprise Integration Kit for SAP. One set is ANSI and the other set is Unicode enabled.
The set of transports you must use depends on the BASIS system your SAP system is running on. Additionally, each transport consists of a data file and a cofile, which are listed in brackets behind the transport names.
If your SAP system is running on a BASIS system earlier than 6.20, you must use the files listed below:
(These files are ANSI.)
Open SQL Connectivity transport (K900320.rd3 and R900320.rd3)
Info Set Connectivity transport ( K900304.rd3 and R900304.rd3)
Row-level Security Definition transport (K900305.rd3 and R900305.rd3)
Cluster Definition transport (K900306.rd3 and R900306.rd3)
Authentication Helpers transport (K900307.rd3 and R900307.rd3)
If your SAP system is running on a 6.20 BASIS system or later, you must use the files listed below:
(These files are Unicode enabled.)
Open SQL Connectivity transport (K900308.r21 and R900308.r21)
Info Set Connectivity transport (K900279.r21 and R900279.r21)
Row-level Security Definition transport (K900280.r21 and R900280.r21)
Cluster Definition transport (K900281.r21 and R900281.r21)
Authentication Helpers transport (K900282.r21 and R900282.r21)
The following files must be used on an SAP BW system:
(These files are Unicode enabled.)
Content Administration transport ( K900283.r21 and R900283.r21)
Personalization transport (K900284.r21 and R900284.r21)
this is snatched from one of the install txt files… We have the same problem and will hopefully find out if installing the transport files helps today…