Skip to Content

Previous blog The Full Monty – Part 12 – Crystal Reports 2008 V1 SP3 Install

In this blog, I downloaded, installed & configured the BObj Integration Kit, which enables communication between my NSP SAP system, my BusinessObjects Edge 3.1, and my Crystal Reports 2008. I was tempted to split this into more than one part as is rather lengthy and detailed, but in the end, I left it as is.

FYI: I do not have any Office Suite, specifically Excel, installed at this point. It is not required.

Once again assisted by Ingo Hilgefort’s efforts, documented in his “Installation and Configuration” blogs.

Be mindful of the NSP compiling when you give it jobs to do for the first time. E.g. I Published a Crystal Report for the first time, and it took about 15 minutes. If in doubt, at least look at the Process Overview for activity in transaction SM50.

This blog has eight main stages, with further precise steps in each: 

  • Downloads
  • Obtain License Key
  • Java Connector Install
  • BObj Integration Kit Install
  • NSP Integration Kit Transports
  • NSP Integration Kit Configure
  • BObj Edge Integration Kit Configure
  • Testing

Downloads

Java Connector

I tried to use the latest JCo offering 3.0.5 at the time, but when it came to importing the SAP Roles during the BObj Edge configuration (see later), a known error occured – “An error occurred: com/sap/mw/jco/JCO$Function”.

See SAP Note: 1274700 – SAP Role Import error: com/sap/mw/jco/JCO$Function. 

So I had to resort to the JCo 2.1.9.

The Java Connector 2.1.9 simply consists of three files.

  • sapjco.jar
  • sapjcorfc.dll
  • librfc32.dll

Files are obtained from the SAP Market Place, http://service.sap.com/connectors -> SAP Java Connector ->Tools and Services(left hand side).

I scrolled down to the 32bit version “SAP JCo 2.1.9 as zip file”, clicked the link then saved the file. I continued to unzip the contents to a location on my machine.

Integration Kit

I was hoping the Integration Kit download would be easy, and at first, it seemed so, however, using the link on SDN, proved otherwise.

From the Main SDN home page, I navigated to the Downloads (tab) page. Towards the bottow, under “FREE DOWNLOAD CATALOG”, I clicked the link for the “BusinessObjects Integration Kit for SAP”. I then chose the “Click here to download the file directly” link. This is what I got

image

Because of the above error, I was forced to download via the SAP Market Place. Fortunately, I found an SP3 version of the Integration Kit, which I doubt would have been available via SDN. 

I went to, SAP Market Place->Downloads(tab)->Business Objects Downloads(tab). Then, under the “Installations and Upgrades” section on the page, I found a “… or simply click here” link, which took me to the SAP BusinessObjects Portfolio. Then SBOP INTGR. FOR SAP->BOBJ INTGR. FOR SAP XI 3.1->Installation->WINDOWS

I downloaded the object 51038935, titled “SBOP INTGR. FOR SAP XI 3.1 SP3 Win Server on IA32 32bit”, 237756kb in size.

SAP GUI

The SAP GUI delivered with my NSP, did not come with the BW 3.x Add-On, required for the BObj Integration Kit. Therefore, I used this opportunity to download and install the latest SAP GUI NW 7.0 Presentation – 7.20 Compilation.

The object 50098620_4 “NW 7.0 Presentation – 7.20 Compilation 1 Present . 1/2”

From here, SAP Market Place->Downloads(tab)->SAP Installations & Upgrades(tab). Then, under the “Installations and Upgrades” section on the left pane, “Installations and Upgrades – Entry by Application Group”->SAP Frontend Components->SAP GUI FOR WINDOWS->SAP GUI FOR WINDOWS 7.20 CORE->Installation

Obtain License Key

From the same location as the SP3 Integration Kit (See above)

I downloaded the other object, titled “Integration Kit License Keys”, #01200314692000000593, 4kb in size.

Java Connector Install

The Java Connector install is not like a usual automated installation. It is merely some file copies and a setting added. This must be performed now, before the “Setup.exe” of the BObj Installation Kit – done later.

I navigated to the location where I unzipped my Java Connector files.

I copied “sapjcorfc.dll” to the Windows System32 directory

“C:WindowsSystem32”

and the “sapjco.jar” file to the Tomcat Web Server’s “Lib” directory

“C:Program FilesBusiness ObjectsTomcat55commonlib”

The “librfc32.dll” would normally get copied to the Windows System32 directory, however, as I had a late version of the SAP GUI (7.1), I had a newer version of this file, already in the Windows System32 directory. I did not overwrite the newer version with an older one.

Note: If you are installing on Windows Server 2008, then the “librfc32.dll” must also reside in the “WindowsSysWOW64” directory.

The Tomcat “Java Classpath”, required the sapjco.jar file’s location to be added. I did this by navigating to “Windows Programs->Tomcat->Tomcat Configuration”. On the “Java” tab, and added the following line at the beginning of the “Java Classpath” field. INCLUDING THE SEMICOLON 

C:Program FilesBusiness ObjectsTomcat55commonlib;

image 

BObj Integration Kit Install

After unzipping the downloaded SP3 Integration Kit, I executed the “Setup.exe” file, to begin the installation.

I kept the default language

image

 

The window disappeared for about 2 minutes, eventually returning with the following screen

image

 

I accecpted the License Agreement

image

 

Then I opened up the downloaded “Integration Kit License” document, and used the second key from the top.

Headed …

“If you are installing SAP Integration Kit for Business Objects Enterprise XI 3.0, or version XI 3.1, or Business Objects Edge XI 3.0, this is your activation key:”

To add to the next installation screen

image

 

I then chose the “Custom” option

image 

 

and installed all components 

image

 

For the “CMS Name”, make sure you use the “Node” name given during the Edge Installation. In my case I left the Edge Installation Node name as it was, which assumed my PC’s name “PC”. So this is what must be used for the “CMS Name”. Excuse the “I” bar which I happened to catch when making the screen shot.

I then gave the the appropriate user Administrator’s password given during the Edge installation

image

 

I then entered the details for the SAP NSP RFC connection.

Program ID:

  • Type a descriptive string to identify the BW Publisher service. The Program ID can take any value, but must be 64 characters or fewer, and may not contain spaces. The Program ID is case-sensitive.

Gateway Host:

  • Type the name of your BW server. If you have a BW cluster, enter the name of the central instance of BW. I entered my Fully Qualified Domain Name

Gateway Service:

  • Type the port number that the Gateway Host is listening on. For example, type 33##, where ## represents the instance number of your SAP Gateway. My NSP instance number is 00, and so the value for this field is 3300.

Here they are

image

 

Next, I chose “Yes”, to deploying web applications

 image

 

I left the Tomcat defaults

image

 

Next, I confirmed that I had performed the installation for the SAP Java Connector. This must be done before get here

image

 

The installation commenced

image 

 

Soon after, I received the following message. This is not the first time I have seen this message happen.

image

 

I checked the file was present, then performed a “Retry” and all was well. So I don’t know what that was all about. 

Shortly after, the installation completed successfully

image 

 

A look at the CCM reveals a new entry “BW Publisher Service 12”

image

 

It was stopped, which is fine, as the NSP SAP system was also down. This Service will require manually starting, when we begin working with it. I dare say it can be configured to start up automatically. The SAP NSP system needs to be started before the “BW Publisher Service 12” can run.

BObj Integration Kit Transports

Just a heads up, the SP3 Transports will not go in without a problem. SAP have a known issue. Read on…

I started up the NSP with the MMC.

Whilst that was underway, I navigated to the downloaded BObj Installation Kit, directory “Transport/unicode_compatible”, (the NSP is a unicode system,) to reveal two further directories – “cofiles” & “data”. I coped the contents of each directory, into the corresponding directories of the NSP under “C:usrsap     rans”

image

 

image

 

Unfortunately, when I returned to see the progress of the NSP in the MMC, it had not started up successfully. I found the developer trace had identified that my VM 1.5GB RAM is not enough. To get over this immediate hurdle, I learnt that if I shut down the BObj Services first, then start up the NSP, then re-start the BObj Services, the NSP will be fine. This soon became a pain as I worked on.

 image

 image

 

After the BOBj Services had Stopped, it was sufficient for me to successfully start the NSP.

I then logged on to the NSP as DDIC in client 000, to begin the SAP Transport imports with transaction STMS, and navigated to the Transport Overview.

image

 

I then double clicked my NSP entry

image 

 

and began adding my Transports in numerical order to the Transport Queue

image 

 

Here is the list of transports with descriptions. Note, I am using the NSP as a Backend (OLTP), AND a BW Server(OLAP), so all Transports were imported

Important: Transports were added to queue in the numerical order below to avoid conflicts.

If your SAP system is running on a 6.20 BASIS system or later, you must use the files listed below:

  • Open SQL Connectivity transport (K900687.r21 and R900687.r21)
  • Info Set Connectivity transport (K900688.r21 and R900688.r21)
  • Row-level Security Definition transport (K900689.r21 and R900689.r21)
  • Cluster Definition transport (K900690.r21 and R900690.r21)
  • Authentication Helpers transport (K900691.r21 and R900691.r21)

The following files must be used on an SAP BW system:

  • Content Administration transport (K900692.r21 and R900692.r21)
  • Personalization transport (K900693.r21 and R900693.r21)
  • MDX Query Connectivity transport (K900694.r21 and R900694.r21)
  • ODS Connectivity transport (K900695.r21 and R900695.r21)

 

image

 

image

 

image

 

and here is the first Transport in the Queue ready for importing

 image

 

the seqeunce above was repeated for all the Transports, until they were all present in the queue, in the correct order.

After all Transports were loaded, I began the import. I pressed (Ctlr +F9) to import the complete queue.

 image

 

I entered my “Target Client” as “000” and, I executed in “Synchronous” mode, due the dependencies of the transports

 image

 

then I chose “Immediate” to begin

image 

 

the import was under way

image

 

shortly after, my import queue was empty

image

 

 a quick look at the import history

image

 

unfortunately revealed that one of the imported Transports failed.  I double clicked the red blob at the end, to drill down

image 

 

I then selected the log icon next to the first red line

image

 

I found the errors were due failed activations of some objects

image

 

I looked up the Transport – R21K900693, in The SAP Market Place to find this was a know error.

image

I simply tried to re-import the Transports again, but same thing happened.

I flaffed about with my NSP system, trying to load the original Integration Kit (SP1), but to no avail. I thought it had a problem with namespaces, so in SE03, I created a “/CRYSTAL/” namespace, still no fix. I re-read the note, and began looking for a Fix Pack.

I eventually went to, SAP Market Place->Downloads(tab)->Business Objects Downloads(tab) and found this “click here” link.

image 

 

It took me to the SAP BUSINESSOBJECTS PORTFOLIO page, where I navigated through to a Windows Server section

 

 image 

 

 

and eventually found a bunch of Fix Packs for the Integration Kit

I downloaded the 2.6 version

image

 

as well as the lastest 2.8 version (I did not use the 2.8 version, because there was some SAP note involved which only complicated matters)

After downloading, I ran the 2.6 version, self extracting file “BOBJINTGRSAP02_6-10007514.exe” file. It began extracting to my “Windows/temp” directory. After extraction, it wanted to begin an installation, I recognized the Language Popup Window. I clicked cancel to stop the installation, after all, I was only interested in the Transports, and navigated to my “Windows/temp” directory, from within I could recognize a “Transports” directory.

I eventually understood what the SAP note meant, when it says “Import a previous version of the transport files e.g. FickPack 2.6 then reimport the service pack 3 transport files.

So I navigated to the “unicode_compatible” directory from my “Windows/temp” directory, and further to both “cofiles” and “data” directories, to copy the four BW transports K900665.R1 through to K900668.R21, from each “cofiles” & “data” directory, into the corresponding directories under “C:usrsap     rans” of the NSP.

After they were copied, I began the Transport import tasks by adding them to the queue, in the correct numerical order. Then I performed the “Import All Requests (Ctrl+F9). For the Import, again, I made sure they would be imported synchronously, and under the “Options” tab, I chose the option to overwrite original versions. I am not really sure if this is necessary, nonetheless, that is what I did.

The Transports went in without a problem

 image

 

I then reloaded the SP3 Transports once again, from K900692 to K900695. Important, when you select the Transports, there is an option to “Import Again”. Make sure it is select.

image

 

After the four Transports were back in the queue again, I performed the “Import for all Transports” (CTRL+F9), again, in synchronous mode, and overwritting the original objects.

Finally, they went in without any problem

image

 

NSP Integration Kit Configure

Unlike Ingo’s blog, I began my Integration Kit Configuration with the SAP NSP System. It also differs with Ingo’s, as I am using the SP3 version, and some steps in the earlier version are no longer required. Finally, as I said earlier, I am going to utilize the delivered user BCUSER from my NSP system.

I began by logging on to the NSP system, with BCUSER, client 001.

NSP Crystal Role

My first step was to create an SAP Crystal Role for my user, so that when Reports are Published, they have somewhere to “hang” from. This should be clearer later.

I ran the Role Maintenance transaction – PFCG

Typed in my Role Name “ZCRYSTAL”, and pressed the create “Single Role” button

image

 

I gave it a meaningful description, and saved it.

I then selected the “Menu” tab, and added an arbitrary transaction, so I thought the “Administer Crystal Report Content” – “/CRYSTAL/RPTADMIN” would be appropriate.

image

Then I selected the “Authorizations” tab, and to generate the necessary authorizations. I selected the button that proposes a “Profile Name”

image 

 

Then I  selected the “Change Authorization Data” to generate the Role’s objects. I saved when prompted.

image 

 

I then generated the authorizations

image

 

After generating the authorizations, I returned back to my Role

image

 

Next I chose the “User” tab, to assign my BCUSER user

image 

 

I added my user, chose “User Comparison” button.

Another window popped up, prompting me to “Complete comparion” (button) which I did and saved when prompted.

I ended up with my “ZCRYSTAL” Role, assigned to my User, with a valid “Menu” and “Authorizations”

image

 

NSP BCUSER user

Next, I prepared the BCUSER user, and made some other changes whilst I was here

I ran “User Maintenance” – SE01, and edited user “BCUSER”. On the main screen I chose to change the “First name” & “Last name” to reflect this was the BCUSER and not DDIC as it suggested

image 

 

I gave it a default printer

image 

 

I added the Profile “SAP_NEW”

image 

 

and checked for Role “ZCRYSTAL” as created and configured earlier

image 

 

I logged out and back in, to put the changes into affect

image

 

NSP RFC Connection

I needed to create an RFC connection for the BW Publishing Service in the CCM.

image

 

I ran the “Configuration of RFC Connections” transaction – SM59, and pressed the create button

image

 

I gave the name “BW_PUBLISHING” as the “RFC Destination”, and a “Connection Type” of “T”. I pressed the enter key, and then gave it a description.

image

 

Further down, I chose the option “Registered Server Program”, for the “Activation Type”, and for the “Program ID” I gave it the same name, as entered during the Bobj Integration Kit “setup.exe” installation process – “BWPub”

image

 

Towards the bottom, I chose the “Default Gateway Value” for the timeout, and the two other parameters, “Gateway Host”, and “Gateway service” as entered during the Bobj Integration Kit “setup.exe” installation process.

image

 

I saved my RFC Connection, and in the MMC, I started the “BW Publisher Service 12”

image

 

it started ok 

image

 

I returned back to the NSP, in SM59 for my RFC connection, to test it

image

 

A successful connection as displayed below

image

 

NSP BObj Server Configuration

All three parts of Ingo’s blog BusinessObjects and SAP – Publishing of Crystal Reports expand on my information. BusinessObjects and SAP – Publishing of Crystal Reports Part 1 of 3, BusinessObjects and SAP – Publishing of Crystal Reports Part 2 of 3, BusinessObjects and SAP – Publishing of Crystal Reports Part 3 of 3

In my NSP, I needed to tell it more about the BusinessObjects Server

I ran the new “Administer Crystal Report Content” transaction – “/CRYSTAL/RPTADMIN”

image

 

I entered an alias, and the fully qualified domain name of my CMS server (excuse me catching the “I” bar in the screen shot)

image

 

then the RFC connection to the BW Server Service

image

 

Trying to “Verify the BOE definition” at this point, only returned a error

image

 

I will return to this, later

I entered some more http parameters, based on my Tomcat server

image

 

I chose to add all languages

image

 

Then I added the “ZCRYSTAL” Role created earlier

image 

 

and finally some other default information. The “Content base folder” information is consistent with the BusinessObjects Edge 3.1 SP3 file structure, so I left it as is

image

 

I then saved the information, to be returned to the main screen, with my “BObj” System defined.

image

 

Next I had to set some more parameters. Still in the “Content Administration Workbench”, I double clicked the “Set BW source parameters”

image

 

At the table screen, I selected the “Edit” mode

image

 

I passed through the information popup

image

 

and entered my BW’s Application Server’s fully qualified domain name, and System Number of my NSP.  

image

 

NSP ICF Setting

Next I had to make some changes to the NSP’s “BW” Service, in transaction SICF. I entered “BW” to fetch the Service.

image

 

I double clicked the “ce_url” item. Note the items are inactive (greyed out – I activated them at the end of this process)

image

 

 

I then selected the “Handler List” tab, and put the screen in “edit” mode

image

 

I selected the first item in the Handler List, and pressed the “Add” button, then inserted the Crystal specific handler class “/CRYSTAL/CL_BW_HTTP_HANDLER” into the first position

image

 

then saved. At the “Make repairs …” information popup

image

 

I created a new Request/Task, for the changes

image

 

after returning to the Service Screen, I right clicked on the “bw”node, to activate the service

image

 

and all below

image

 

again, returning to the “Service” screen, only this time, the nodes were all active, which can been seen, as they are no longer greyed out

image

 

BObj Edge Integration Kit Configure

For these steps, the NSP needed to be up and running. As I said earlier, the only way I could get both systems up were by stopping all the BObj Edge Services in the CCM first, then starting the NSP in the MMC. When the NSP was up and running, starting the “Apache Tomcat”, BW Publisher Service”, & “Server Intelligence Agent” Services from the CCM.

image 

 

I then logged on to the Central Management Console (CMC), as administrator

image

 

image

and navigated to the “Authentication” page

image

 

and double clicked the “SAP” item

image

 

Under the “Entitlement Systems” tab, I entered my NSP System details

image

 

and clicked “Update”, and the “Logical system name” was auto populated

image

 

then, under the “Options” tab, I checked the “Enable SAP Authentication” & “Automatically import users”. I also checked the “Default system” was my NSP logical system name.

image

 under the “Role Import” tab

image

 

I selected my “ZCRYSTAL” entry Role assigned to my BCUSER, and pressed the “Add” button, then “Update”

image

 

I then exited the “Authentication” screen

To check the above “Authentication” settings, I navigated to the “User and Groups”, “User List” to see my NSP BCUSER was present, it was

image

 

A final “Authentication” validation, was to log on to InfoView

image

 

 with my BCUSER, using “SAP” Authentication

image

 

image

 

 

I now had a folder structure for the NSP System. See under “Folders” and follow the hierarchy below

image

 

I needed to give this folder, permissions for my imported “BCUSER” user which is used to Publish items & create certain objects under the “NSPCLNT001” node.

I right clicked on it, and chose “User Security”

image

 

then, I was able to press the “Add Principals” button

image

 

at the “Add Principals” screen, I chose “Groups” to identify my new User/Role combination as a Group. I selected the “NSP~001@ZCRYSTAL” entry

image 

 

and added that over to the right hand side “Selected users/groups”

image

 

for me to press the “Add and Assign Security” button

At the “Assign Security” screen, I selected the “Advanced” tab, the the “Add/Remove Rights” link

image

 

In the “Add/Remove Rights” screen, I selected the “tick” option for all entries, then pressed the “OK” button

image

 

back at the “Assign Security” screen, I pressed the “OK” to apply the changes and exit

image

 

back at the “User Security” screen for my Folder NSPCLNT001, I could see my new Principal

image

 

That was the final step to configuring the BObj Integration Kit.

Finally, I can verify my BObj definition from within my NSP.

I logged in to my NSP, and ran transaction “/CRYSTAL/RPTADMIN”. I double clicked my “BObj” definition under “Enterprise System”->”Available system”. I navigated to the “RFC Destinations” tab, selected my “BW_PUBLISHING” item, and pressed the “Verify BOE definition” button.

After some serious compiling, I eventually was returned a success message

image

MEGA IMPORTANT !!

For whatever reason, the file “EnterpriseFramework.dll” may become de-registered, in Windows, and will fail the “Verify BOE definition” test. If it does fail, and you believe you have configured everything as it should be, run the following command from Windows -> Run… line. Including the “”.

regsvr32 “C:Program FilesBusiness ObjectsBusinessObjects Enterprise 12.0win32_x86EnterpriseFramework.dll”

More information can be found here http://ingohilgefort.blogspot.com/2009/07/sap-netweaver-bw-and-crystal-reports.html

You cannot harm the system if you run this more than once

SAP GUI Installation

I required a newer SAP GUI as the NSP delivered and currently installed one, did not supply me with the BW 3.X Add-Ons required for Crystal Reports. When I ran Crystal I should see an “SAP” menu, however, I did not.

image

 

So I continued to uninstall the SAP GUI, via Windows Control Panel->Programs and Features

image

 

The remaining of the uninstall was pretty eventless, so I have not bothered to add anything further.

I stopped my NSP from the MMC, and also stopped my BObj Services from the CCM.

I navigated to the directory “NW_7.0_Presentation 7.2 Comp1NW_7.0_PresentationPRES1GUIWINDOWSWIN32”, where I unzipped the download object, and executed the “SetupAll.exe” program to begin installation.

image

 

the installation wizard began, I clicked “Next”

image

 

 

I selected my components

 

  • SAP GUI for Windows 7.20 (Compilation 1)
  • BW 3.50 Add-on for SAP GUI 7.20
  • KW Add-On for SAP GUI 7.20
  • Business Explorer

 

image

 

I kept the path defaults for the FrontEnd

image

 

 

I kept the path defaults for the Business Explorer

image

 

 

the installation commenced, and completed. I then re-booted.

I looked at the new Program Group to see what I now have. I still do not have any Microsoft Office Suite Applications installed, so a couple of icons remain blank

image

 

I then ran the “SAP Logon”

image

 

to see my new SAP Logon Pad

 image

 

I also ran Crystal Reports to make sure I now had an “SAP” menu

image

 

Testing

To finally test my BObj Installation Kit configuration, I made sure my NSP, and all necessary BObj Services were up and running. Don’t forget I have to start the NSP, before the BObj Services

image

 

Preparation

To test the Publishing, I used an Info Set in the SAP delivered, “Flight” Scenario, that already exists in my NSP. However, there was a little preparation for the test. 

I logged on to the NSP, with my BCUSER user, and ran the program “SAPBC_DATA_GENERATOR” from transaction SE38. This populated some SAP tables for the “Flight” scenario

image

 

I chose the “Standard Data Record” set

image

 

I confirmed the caution

image

 

returning to the program screen with my data populated and ready

Next, I had to assign my user BCUSER to an SAP “User Group” so that we can see some SAP Info Set objects from within Crystal Reports. This is a little SAP authorization overhead that needs to be done, just for this example. It is required because when I run Crystal Reports and look for an Info Set, the user I am using must have privilages for the “User Group” that contains the Info Sets I want to choose. If I do not do this, I will not be able to see any Info Sets with my user BCUSER.

I ran the transaction for “User Groups” – SQ03

At the initial screen, I chose “User Group” “BC_KUNDE”. This is the one for the “Flights” Scenario

image

 

on the next “Assign Users” screen, I added my user “BCUSER”, and Saved, then Exited

image

That’s the BCUSER / Info Set stuff prepared

Crystal Reports

Next, I ran Crystal Reports

image

 

After, “OK” to the “Evaluation” prompt, from the initial Crystal Reports page, I selected the “Report wizard”

image

 

I then was presented with a window for my connections. As I had none at this stage, I dropped down the “Create New Connection” node

image

 

and navigated down to “SAP Info Sets”. After clicking on the “SAP Info sets” node, I was prompted with a “SAP System Logon” window. I selected the “NSP” node, and clicked “Next”. I had to select the “NSP” system before “Next”

image

 

I entered my NSP client “001”, “BCUSER” user and password details

image

 

then “Finish”

image

 

I expanded the selection 

my host (pc)->Info Sets (I)->Global (G)

and selected the Info Set “BCS1”. I then went to add it the “Selected Tables:” pane

image

 

because this Info Set has a number of parameters, I was prompted to enter them. The only mandatory parameter was the “Also Display Cancellations” under the “PA_CANC” section. I set that to “True”

image

 

then scrolled all the way down to the bottom of this screen, to click “OK”

image

 

now with my “BCS1” Info Set in the “Selected Tables:” pane, I pressed “Next”

image

 

I then began building my Report

I arbitrarily chose some “Fields” by selecting them from the left “Available Fields:” and adding them to the right “Fields to Display:”

image

 

in a similar fashion to above, I selected some fields for “Grouping”

image

 

and kept the proposed “Summarized Fields”

image

 

I kept the defaulted “Group Sorting”, as is

image

 

and kept the defaulted “No Chart” option

image

 

then chose the “Carrier Name” and “Flight Date” for “Record Selections”

image

 

I kept the defaulted “No Template”

image

 

and so I “Finished” and off the report went to access the database

image

 

a short while after, I was returned to Crystal Reports screen with my Report displayed in “Preview” mode

image

 

I was finally ready for “Publishing”

From the Crystal Reports menu, I chose SAP->Save Report…

image

 

I was prompted, again for some parameter values

image

 

I navigated to my mandatory parameter, I mentioned earlier, and chose “True”

image

 

I was then prompted to Generate the data, so I could actually save the report

image

 

I was prompted to log on to my NSP system

image

 

then I gave it the name “Flights”. I recognized my “ZCRYSTAL” Role description “my crystal menu”, it found. I was happy to “hang” my Report from under this Role.

image

 

then I chose to “Automatically publish to Enterprise” for this report

image

 

I was returned to the Crystal Reports main screen, with the cursor timer going

image

 

It must have been a good 10 – 15 minutes, probably compiling in the NSP, before it went “splat” and gave me a synchronizing error

image

 

As a workaround, I made my BObj Edge “NSP~001/BCUSER” user a member of the BObj Edge “Administrators”. This rather made the BObj Edge Folder “NSPCLNT001” Security steps performed earlier redundant, but I could not find anything wrong with the Security steps I performed, so I had to do this

I logged on to the BObj Edge, as “Administrator” and navigatied to the “Users and Groups”. I clicked the “User List”, and right clicked my “NSP~001/BCUSER”, then “Join Group”

image

 

I then selected the “Administrators” group, and added

image

 

After performing the same Report Saving tasks, I eventually successfully “Published”

image

 

NSP

I then had a look around the NSP System and noticed my “User Menu” for user “BCUSER” now had the “Flights” Report

image

 

In the Role Maintenance – transaction PFCG, for my Role “ZCRYSTAL”, I see the Report present under my Role Menu. Also, the “Authorizations” tab has gone red, for whatever reason. I left it as is for now.

image 

 

I navigated to the NSP Crystal “Content Administration Workbench”, transaction “/CRYSTAL/RPTADMIN”. I double clicked the “Selelect reports and roles to publish” filter, then selected my “BObj” “Enterprise System”, and “OK”

image 

 

to reveal my NSP system has knowledge of the my “Flights” report, being “Published”

image 

 

BObj Edge – InfoView

I logged on to the BObj InfoView, and selected the “Document List”

image

 

I navigated to “My Groups” and “my crystal menu”, to see my “Flights” Report

image 

 

I double clicked my “Flights” Report, to be presented with a selection criteria

image

 

where under the “PA_CANC” section, I changed the current value from “False” to “True”

image 

 

I then “Executed” the Report

image 

 

and was presented with my data

image

 

BObj Edge – Central Management Console

In the CMC BObj Edge under the “Folders”, I saw my hierarchy now contains my “ZCRYSTAL” Role, with the Report “Flights”. I right clcked on my “Flights” Report and chose “Schedule”

image

 

 

I selected the “Database Logon” from the left hand side, and entered my BCUSER user password

image

 

Then I chose the “Parameters” option, and updated the “PA_CANC” selection to “True”

image

 

Then I pressed the “Schedule” button

image

 

I could see my “Flights” Report started “Running”  

image

 

and finished, successfully

image

 

That’s the BObj Integration Kit, in and done!

I can now begin to learn and play around the Scheduling and Maintenance of Published Reports.

All this should lead me nicely into my next blog

The Full Monty – Part 14 – Dashboard Design (Xcelsius) & Live Office Install & Configure

To report this post you need to login first.

7 Comments

You must be Logged on to comment or reply to a post.

  1. Luc Vanrobays
    Hi Gingle,

    first of all, thanks a lot and congratulation for your dedication in the Full Monty serie. It gave us (gave me) the stamina to go all the way up to this BW-BOBJ instalation on a local machine (virtual or not). Any other initiative you may take will be perceived as highly interesting.

    Concerning the MDX driver, as we are running BW701SP02 or later we should use the transport R72K900007
    instead of R21K900694.

    Best Regards,

    Luc

    (0) 
      1. Luc Vanrobays
        Hi Gingle,
        Well I did follow your instructions about installing as well the patch for Integration Kit  BOBJINTGRSAP03P_2-10007514.exe

        But instead of running the application, I did unzipped into a temp file and in there
        C:\todelete\Transports\unicode_compatible\cofiles,I found K900007.R72 and in C:\todelete\Transports\unicode_compatible\data
        R900007.R72
        In the text file C:\todelete\Transports\transports_EN.txt there is an explanation about this.

        Actually, I was very happy to connect via Crystal, but was disapointed NOT to find the BW connection in Universe Builder…
        Probably missed a step, but no clue which could be.

        Cheers,

        Luc.

        (0) 
        1. glen spalding Post author
          hi luc, it is interesting to see what you have discovered. i am guessing you created the “todelete” directory ?
          could you please post the transports_EN.txt. thanks. glen
          (0) 
          1. Luc Vanrobays
            No problem, Glen.

            Here is the “read me” about transports as included with the Integration Kit Support Package. Nothing much interesting though, except the known million cell limitation here corrected.

            >>

            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 (K900120.r22 and R900120.r22)
            * Info Set Connectivity transport (K900121.r22 and R900121.r22)
            * Row-level Security Definition transport (K900122.r22 and R900122.r22)
            * Cluster Definition transport (K900123.r22 and R900123.r22)
            * Authentication Helpers transport (K900124.r22 and R900124.r22)

            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 (K900687.r21 and R900687.r21)
            * Info Set Connectivity transport (K900688.r21 and R900688.r21)
            * Row-level Security Definition transport (K900689.r21 and R900689.r21)
            * Cluster Definition transport (K900690.r21 and R900690.r21)
            * Authentication Helpers transport (K900691.r21 and R900691.r21)

            The following files must be used on an SAP BW system:

            (These files are Unicode enabled.)

            * Content Administration transport (K900692.r21 and R900692.r21)
            * Personalization transport (K900705.r21 and R900705.r21)
            * ODS Connectivity transport (K900695.r21 and R900695.r21)

            If your SAP BW system has not applied SAP Note 1232751, you must use the file listed below:
            * MDX Query Connectivity transport (K900694.r21 and R900694.r21)
            If your SAP BW system has applied SAP Note 1232751, you must use the file listed below:
            * MDX Query Connectivity transport (K900007.R72 and R900007.R72)

            (0) 

Leave a Reply