interactive reporting

[Former Member]

Hi,

I have followed the config guide C41 CRM Interactive Reporting. I am using a seperate client as a reporting client. When I try to execute the report opportunity pipeline, the result list is empty - even though there are opportunities registered. I get no other error or warning messages. Do you have any suggestions for me? I feel like the opportunity which I have created in the crm client is not available in the reporting client, but I am not familiar with how this work...

thanks for help.

regards Camilla

[Former Member · Accepted solution]

Hello,

Firstly check chapter 6.6 in the config guide which describes what data is retrieved in the report.

Your system user has to be assigned to BP,

and the BP has to be in opportunities.

Regards,

Fukuhara Yohei

[Former Member · Accepted solution]

Hi Fukuhara,

thanks for answer. However, this criteria are allready fullfilled, but I still only get no result.

Other suggestions?

regards Camilla

[Former Member · Accepted solution]

hello Camilla,

What report do you want to use?

Activity, opportunity?

Regards,

Fukuhara yohei

[Former Member · Accepted solution]

Hi,

I have been testing the opportunity pipeline report.

Regards Camilla

[Former Member · Accepted solution]

Hi Camilla,

Firstly you have to check data exists or not using data source "/CRMBW/OLTP_OPPORTUNITY_ITEM".

Run t-cd:rsa3 and check opportunities.

If you can see opportunities, the problem is filter condition of the report.

Regards,

Fukuhara Yohei

[Former Member · Accepted solution]

Hi again Fukuhara,

Thanks for input. When I run the extractor checker in client 100 which is my crm client I get 5 result, but when I run the same test in my reporting client 600 I get 0 result. In my crm client I put the logical system to my reporting client as a target system and ran the extraction again, men there is still 0 result in my reporting client. I guess when using two clients that the data are collected from the reporting client?? Is there a job needed to set up? I have set ut the jobs defined in the config guide...

Thanks again for help.

regards Camilla

[Former Member · Accepted solution]

Hi,

How about executing query "/CRMBW/CRM_C04I//CRMBW/CRM_C04I_Q001" via t-cd:rsrt1 in CRM client?

Can you get opportunities?

Regards,

Fukuhara Yohei

[Former Member · Accepted solution]

Hi,

thanks again. This query gives 0 result. I also get a warning message:

Diagnosis

Values for InfoObject /CRMBW/LOGSYS have a maximum length of 10 characters. The user exit for variable /CRMBW/V_LOGSYS delivers value lt;ENTER LOGSYSquot;, that is longer than 10 characters.

System Response

Procedure

This message is a warning, indicating possible errors in user exits.

Procedure for System Administration

Notification Number BRAIN 619

However, I am not sure where I need to change something...

Regards Camilla

[Former Member · Accepted solution]

Hi,

Please check rfc destination's log on user from report client to CRM client.

Are you using "current user" for the destination?

Regards,

Fukuhara Yohei

[Former Member · Accepted solution]

Hi,

There are two rfc connection from reporting client to crm client. One was automatically created and uses the aleremote user which I created as part of the config guide. This rfc I can see in transaction rsor. In addition I have created a trusted rfc which have the flag current user. This rfc I use in the table SMOFPARSFA (for parameter CRM_CLIENT). All rfc's do not have more than 10 char. The ID of the logical system has also less than 10 char.

For me it looks like the warning message has something to do with the logical name. It seems like it does not manage to return the logical system...

Do you have more ideas?

Thanks again for help!

Regards Camilla

[Former Member · Accepted solution]

Hi,

I thought the warning message could be ignored and the cause seems to be rfc connection,

because you can extract opportunities via rsa3 but not query.

Now I have no idea about the issue.

If I were you, I would debug programs from rsrt1.

Regards,

Fukuhara yohei