Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
former_member199597
Participant

Introduction

The task of my part of the project was to integrate Webi Reports from an existing BO 3.x installation in SAP CRM. It should be possible to submit parameters from CRM to the Webi Report. I was free to use which ever technology that would lead us to the expected result. For the integration I did SSO for BI 4.x but not

for 3.x since we want to upgrade soon.

I did not use was the Business Function "Integrated Reporting CRM_ANA_BOB" since I did not need the supplied reports from SAP. Also this works perfectly fine without the Business Function.

Please let me know if somthing is missing - however I cannot support you since I am quite busy :smile:

So I will update if somthing is wrong, missing or you might want me to add.


0.Landscape

- CRM 7.0 EHP2

- BO 3.1 SP3

1. Preparation

You will first need to have the information about the open document interface for BO 3.x (or BI4.x). Then you should create a working URL with parameters to test the URL in a browser of your choice.

What we need is (BO 3.x):

- The CUID of the Webi Report

- The Parameter you want to submit from CRM to BO

In order to get the CUID you want to go to InfoView select right click on the report and get the CUID (See screenshot).

To obtain the name of the parameter you want to fill from CRM, you open and edit the report. Then simply copy the name of the parameter you want to transfer. In my case its the number of the business partner <GP-Nr.:>. In order to use the parameter for the Opendocument Interface of Webi - simply add

<lsS> to the name of the parameter -> <lsSGP-Nr.:>

-> Make sure to remove the brackets <> :smile:

Now we can construct the URL:

http://<YOUR_BOE_SYS>:<PORT>/OpenDocument/opendoc/openDocument.jsp?

And add the following parameters:

sIDType=CUID (Type of ID you specify in iDocID)

&iDocID=ASCrT9OCQCJCtzkRiZ_NTs8 (CUID of the report)

&lsSGP-Nr.:=<BPARTNER_NO_OF_YOUR_CHOICE>

The result should look like this:

http://boetest.free.com:8080/OpenDocument/opendoc/openDocument.jsp?sIDType=CUID&iDocID=ASCrT9OCQCJCt...

Try the URL in your browser - you need to login to your BO System and the report should appear and refresh by itself.

2. Integration of Webi in CRM using Transaction Launcher by URL

After some research and the information supplied of a consultant, I chose the Transaction Launcher to do the job.

In order to use the transaction launcher we need some steps to configure. Hold tight :smile:

Step 1: Configuration of URL


Create a new URL in TA SPRO:

(SAP Customizing Implementation Guide -> Customer Relationship Management -> UI Framework -> Technical Role Definition -> Transaction Launcher -> Define URLs and Parameters)

The URL ID is important an will follow us during the configuration process.

So create a new entry with the following information:

The URL Field should be the first part of the URL untill the first parameter, as tested before in the browser:

Click on SAVE and you should have an entry like this:

http://boetest.free.com:8080/OpenDocument/opendoc/openDocument.jsp?

Step 2: Configuration of the Parameter for the URL

Now we have the URL configured but we still need to configure the parameters we want to submit from CRM to the Webi Report.

Lets do this:

Select your parameter and click on Define Parameters. Create the parameters that we specified before. Do this for all the 3 parameters we need.

The result should look like this:

Save your changes - make sure the URL and parameters are saved.

3. Integration of Webi in CRM using TXL by URL


If you have the possibility to test the transaction launcher, you can proceed to Chapter 4. Since I am no CRM consultant I can will simply show how I did test the transaction launcher. For this you need to do some CRM configuration.

OK lets do this.

We need to have logical link, a direct link group, a navigation profile and a business role that is assigned to us, in order to test this.

Step 1: Definition of the logical link

In SPRO we will create a new logical link. This is quite easy:

(SAP Customizing Implementation Guide -> Customer Relationship Management -> UI Framework -> Technical Role Definition -> Define Navigation Bar Profile )

Create a logical link with the following parameters:

The Parameter is the parameter you in Chapter 1. If you are unsure about the parameter class you need to ask your CRM consultant - if you use the wrong parameter class, you might not see your transaction launcher link. So in my case it was CL_CRM_UI_LTX_NAVBAR_PARAM.

Save your entry.

Step 2: Definition of the Direct Link Group

The direct link group is a visible box we can use to test the Transaction Launcher.

Create a direct link group, I used Z_BW fill in a description and your almost done.

Now we need to assign our logical link to the direct link group:

We created Z_BW_DEMBO and we add it the the link group. Fill in what ever position you like.

The Logical Link Z_BW_DEMO I created before, so no need to worry about this one.

Step 3: Assign the Direct Link Group to YOUR Navigation Bar Profile

Select your Navigation Bar you are using in your CRM.

Now add the Direct Link Group Z_BW we created before to the Navigation Bar Profile.

Save your changes :smile:

We are almost done - now we add our direct link group to the business role.

Step 4: Assign the Direct Link Group to YOUR Business Role

Make sure your user is assigned to the business role in order to see our Direct Link Group.

Go to SPRO:

(SAP Customizing Implementation Guide -> Customer Relationship Management -> UI Framework -> Business Roles -> Define Business Role )

Select the Business Role you want to add the Direct Link Group to:

Now click on "Adjust Direct Link Group" and make it visible:

Now select your Group ID and make the Direct Links visible in using "Adjust Direct Links":

4. Setting up the Transaction Launcher

In SPRO follow the path:


(SAP Customizing Implementation Guide -> Customer Relationship Management -> UI Framework -> Technical Role Definition -> Transaction Launcher -> Configure Transcation Launcher)

A wizard will help you now to configure the Transaction Launcher (TXL)

Fill in the name of the parameter we created in Chapter 2.

The Class will be generated by the Transaction Launcher - in my example I used the name of the parameter definition inserting a CL for class. You can use whichever name you like.


Now the wizard should show you the URL ID Z_BW_REPORT_DEMO we created in Step 1 - you cannot edit this. Just Continue..


Now we come to the most important part - the parameters :smile: finally...

The configuration is done by selecting the parameter in the drop down and filling in the value.

So since we have 3 parameters we want to submit, we configure all 3 of them:

sIDType : CUID

sDocID: ASCr…..  ( The CUID of the webi report)

lsSGP-Nr.:     : //datacontextCURRENTCUSTOMER/BP_NUMBER (Context we read the actual selected Business Partner in CRM).

So the last parameter is the one that will submit the Business Partner to the Webi. To test it we could also use the example we did in Chapter 1. Preparation.

In my example it was 0001096563.

Make sure all 3 parameters are filled - continues and save the TXL. Just select the again and see if the value is still filled.

Now open CRM WebUI - and you should see the Direct Link Box with the logical links we defined.

(sorry its in german - but you get the idea).

If you did use the //datacontext for retrieving the actual Business Partner - make sure you really selected it before you call the report.

If you did use the static BP Number e.g.0001096563 - you can just hit the link and it should work.

Make sure:

- you are assigned to the business role

- you have the correct parameter class

- the parameter you want to submit is correctly written.

- If you change somthing e.g. add a parameter -> make sure you will execute the transaction wizard again since the Class must be generated accordingly.

So I hope this helps - I hope this will work for you too :smile:

Cheers,

Andreas

24 Comments
Labels in this area